From: Karl Hiramoto <karl@hiramoto.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-arm-kernel@lists.infradead.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: IXP4xx repetitive 16-bit/32-bit I/O macros/inlines.
Date: Sun, 08 Nov 2009 21:24:39 +0100 [thread overview]
Message-ID: <4AF72907.1060705@hiramoto.org> (raw)
In-Reply-To: <m3iqdkc0n6.fsf@intrepid.localdomain>
Krzysztof Halasa wrote:
> Anybody using 32-bit PATA/SATA transfers on IXP4xx? :-)
>
Yes, on HPT371 IDE chip on the PCI bus to interface to compact flash
to store logs. For what it's worth I've only ever been able to make PIO
work, I've never had any luck with the IDE DMA modes. It hasn't been a
high enough priority to investigate further.
> Long story, mostly with PCI in mind:
> - readb/readw/readl, writeb/writew/writel macros are value-preserving
> - __raw_* are order-preserving (i.e., strings are preserved)
> but the repetitive versions (outs[wl], ins[wl], ioread*_rep,
> iowrite*_rep) are supposed to preserve order as well (while lacking the
> __raw_ prefix).
>
> Comments?
>
> Is it worth it to change the names to __raw_*, or maybe to some other
> variant like native_*, to avoid confusion? It's really confusing.
> There aren't many users in the tree (I'd also change readl() and friends
> to something like read_le32, but it would be massive, comments welcome).
>
> Or perhaps we should have *_le32, *_be32, _order32? It should be
> something the compiler can optimize out if used wi
*_le32, *_be32, _order32 sounds like a good idea.
> th le32_to_cpu etc.
>
>
> --- a/arch/arm/mach-ixp4xx/include/mach/io.h
> +++ b/arch/arm/mach-ixp4xx/include/mach/io.h
> @@ -311,7 +311,7 @@ static inline void
> __ixp4xx_outsl(u32 io_addr, const u32 *vaddr, u32 count)
> {
> while (count--)
> - outl(*vaddr++, io_addr);
> + outl(cpu_to_le32(*vaddr++), io_addr);
> }
>
> static inline u8
> @@ -366,7 +366,7 @@ static inline void
> __ixp4xx_insl(u32 io_addr, u32 *vaddr, u32 count)
> {
> while (count--)
> - *vaddr++ = inl(io_addr);
> + *vaddr++ = le32_to_cpu(inl(io_addr));
> }
>
> #define PIO_OFFSET 0x10000UL
>
next prev parent reply other threads:[~2009-11-08 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 18:49 IXP4xx repetitive 16-bit/32-bit I/O macros/inlines Krzysztof Halasa
2009-11-08 20:24 ` Karl Hiramoto [this message]
2009-11-08 21:07 ` Krzysztof Halasa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF72907.1060705@hiramoto.org \
--to=karl@hiramoto.org \
--cc=khc@pm.waw.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox