Memory type used for ioremap

Shilimkar, Santosh santosh.shilimkar at ti.com
Wed Aug 11 09:03:42 EDT 2010


> -----Original Message-----
> From: Pedanekar, Hemant
> Sent: Wednesday, August 11, 2010 6:25 PM
> To: Shilimkar, Santosh; Russell King - ARM Linux
> Cc: linux-arm-kernel at lists.infradead.org
> Subject: RE: Memory type used for ioremap
> 
> Shilimkar, Santosh wrote on Wednesday, August 04, 2010 5:35 PM:
> 
> >> -----Original Message-----
> >> From: Pedanekar, Hemant
> >> Sent: Wednesday, August 04, 2010 5:31 PM
> >> To: Shilimkar, Santosh; Russell King - ARM Linux
> >> Cc: linux-arm-kernel at lists.infradead.org
> >> Subject: RE: Memory type used for ioremap
> >>
> >> Shilimkar, Santosh wrote:
> >>>> Pedanekar, Hemant wrote:
> >>>>> Russell King - ARM Linux wrote:
> >>>>>> On Fri, Jul 09, 2010 at 07:32:46PM +0530, Pedanekar,
> >>> Hemant wrote:
> >>>>>>> Catalin,
> >>>>>>
> >
> >> Santosh,
> >>
> >> Can you please point me to the patch series you mentioned? I will give
> it a
> >> try.
> > http://www.spinics.net/lists/arm-kernel/msg93218.html
> >
> 
> Thanks for the link. I applied the patches and used writel/readl but no
> luck.
> The MT_DEVICE mappings still result into writes not getting through.
> 
> >>
> >> Regarding read-back, the writes themselves are not successful as the
> >> peripheral has specific requirement for non-posted writes. So reading
> back
> >> after write Always returns old value.
> >>
> > Are you sure about this behaviour?
> 
> Yes. The writes are not going through with MT_DEVICE mappings as the
> target
> peripheral has requirement for non-posted writes.
> 
> Looks like only strongly ordered mapping is resulting into non-posted
> writes
> which works. Is there any specific reason the strongly order mapping patch
> is
> not accepted/applied?

Attaching one which is I use for debugging. This is only for OMAP3/4
Hope this is useful to you.

I suggest only the device which has non-posted requirement
you convert it to SO

Regards,
Santosh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-OMAP3-4-Enable-IO-posting.patch
Type: application/octet-stream
Size: 7074 bytes
Desc: 0001-OMAP3-4-Enable-IO-posting.patch
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100811/6b57000a/attachment-0001.obj>


More information about the linux-arm-kernel mailing list