From: Karsten Keil <kkeil@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, isdn4linux@listserv.isdn4linux.de,
"Andreas.Eversberg" <Andreas.Eversberg@versatel.de>
Subject: Re: [PATCH 3/4] Fix remaining big endian issue of hfcmulti
Date: Tue, 5 Aug 2008 19:25:49 +0200 [thread overview]
Message-ID: <20080805172549.GA6052@pingi.kke.suse.de> (raw)
In-Reply-To: <1217941466.24157.190.camel@pasglop>
On Tue, Aug 05, 2008 at 11:04:26PM +1000, Benjamin Herrenschmidt wrote:
>
> > Thanks for this hint, I didn't know that the repetive versions are
> > for byte streams and not for eg. transfer of multiple u32.
> > So it makes things lot easier the code should look like:
> >
> > int l = len >> 2;
> >
> > if (l) {
> > ioread32_rep(hc->pci_membase + A_FIFO_DATA0, data, l);
> > data += l << 2;
> > }
> > if (len & 2) {
> > ioread16_rep(hc->pci_membase + A_FIFO_DATA0, data, 1);
> > data += 2;
> > }
> > if (len & 1)
> > writeb(*data, hc->pci_membase + A_FIFO_DATA0);
>
> Don't mix the io* variants with the PCI variants. Use iowrite8 for the
> last one and make sure you do a proper pci_iomap.
Yes, OK it need some cleanups in other places as well.
>
> One cool thing with the new iomap stuff is that it also works for both
> PIO and MMIO, so you no longer need to differenciate writeX from outX
> as long as you use the right mapping stuff initially.
>
Yes this stuff looks really cool, but unfortunately in our case it is not
so easy to remove the different IO functions for MMIO and PIO, since for
MMIO the chip use a flat register model, for PIO it use indirect addressing
via only 2 ports, one for the register offset and one for the data IO.
Maybe we can use the trick from lib/iomap.c to detect which
kind of IO is needed, but unfortunately PIO_OFFSET, PIO_MASK and
PIO_RESERVED are not exported so it would need to copy the defines, which
isn't a really clean solution.
--
Karsten Keil
SuSE Labs
ISDN and VOIP development
SUSE LINUX Products GmbH, Maxfeldstr.5 90409 Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)
next prev parent reply other threads:[~2008-08-05 17:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 14:35 [PATCH 3/4] Fix remaining big endian issue of hfcmulti Karsten Keil
2008-08-04 12:03 ` David Woodhouse
2008-08-04 14:29 ` Karsten Keil
2008-08-05 4:29 ` Benjamin Herrenschmidt
2008-08-05 11:31 ` Karsten Keil
2008-08-05 13:04 ` Benjamin Herrenschmidt
2008-08-05 17:25 ` Karsten Keil [this message]
2008-08-05 18:42 ` Linus Torvalds
2008-08-05 21:02 ` Karsten Keil
2008-08-05 21:23 ` Sean MacLennan
2008-08-05 21:37 ` Linus Torvalds
2008-08-05 21:59 ` Sean MacLennan
2008-08-05 23:04 ` Benjamin Herrenschmidt
2008-08-05 23:38 ` Sean MacLennan
2008-08-06 0:18 ` Karsten Keil
2008-08-06 0:33 ` Benjamin Herrenschmidt
2008-08-05 21:46 ` Benjamin Herrenschmidt
2008-08-05 21:45 ` Benjamin Herrenschmidt
2008-08-05 21:43 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 11:01 AW: " Andreas.Eversberg
2008-08-07 13:46 ` Karsten Keil
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=20080805172549.GA6052@pingi.kke.suse.de \
--to=kkeil@suse.de \
--cc=Andreas.Eversberg@versatel.de \
--cc=benh@kernel.crashing.org \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.