* Wrong location of omap_writel?
@ 2012-05-28 9:00 David Lanzendörfer
2012-05-28 11:04 ` Tony Lindgren
0 siblings, 1 reply; 2+ messages in thread
From: David Lanzendörfer @ 2012-05-28 9:00 UTC (permalink / raw)
To: linux-arm-kernel
Hi
Under linux-next 20120528
I've just found "omap_writel" within "arch/arm/plat-omap/include/plat/usb.h"...
Shouldn't it be located within "arch/arm/plat-omap/include/plat/io.h"?
Just some logical question.
It looks somehow wrong to me...
best regards
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120528/266af70a/attachment.sig>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Wrong location of omap_writel?
2012-05-28 9:00 Wrong location of omap_writel? David Lanzendörfer
@ 2012-05-28 11:04 ` Tony Lindgren
0 siblings, 0 replies; 2+ messages in thread
From: Tony Lindgren @ 2012-05-28 11:04 UTC (permalink / raw)
To: linux-arm-kernel
* David Lanzend?rfer <david.lanzendoerfer@o2s.ch> [120528 02:07]:
> Hi
>
> Under linux-next 20120528
>
> I've just found "omap_writel" within "arch/arm/plat-omap/include/plat/usb.h"...
> Shouldn't it be located within "arch/arm/plat-omap/include/plat/io.h"?
>
> Just some logical question.
> It looks somehow wrong to me...
It's in usb.h as the legacy full speed usb code is the only remaining user
for omap_read/write for omap2+.
I've also posted a series that removes the legacy full speed usb code and
omap_read/write for omap2+ for v3.6 merge window.
Regards,
Tony
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-05-28 11:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-28 9:00 Wrong location of omap_writel? David Lanzendörfer
2012-05-28 11:04 ` Tony Lindgren
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox