From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] siimage: add sil_* I/O ops
Date: Sun, 27 Apr 2008 21:48:28 +0200 [thread overview]
Message-ID: <200804272148.29131.bzolnier@gmail.com> (raw)
In-Reply-To: <480A2926.6050404@ru.mvista.com>
On Saturday 19 April 2008, Sergei Shtylyov wrote:
[...]
> > @@ -124,6 +124,54 @@ static inline unsigned long siimage_seld
> > return base;
> > }
> >
> > +static u8 sil_ioread8(struct pci_dev *dev, unsigned long addr)
> > +{
> > + u8 tmp = 0;
> > +
> > + if (pci_get_drvdata(dev))
> > + tmp = readb((void __iomem *)addr);
> > + else
> > + pci_read_config_byte(dev, addr, &tmp);
> > +
> > + return tmp;
> > +}
> > +
> > +static u16 sil_ioread16(struct pci_dev *dev, unsigned long addr)
> > +{
> > + u16 tmp = 0;
> > +
> > + if (pci_get_drvdata(dev))
> > + tmp = readw((void __iomem *)addr);
> > + else
> > + pci_read_config_word(dev, addr, &tmp);
> > +
> > + return tmp;
> > +}
> > +
> > +static void sil_iowrite8(struct pci_dev *dev, u8 val, unsigned long addr)
> > +{
> > + if (pci_get_drvdata(dev))
> > + writeb(val, (void __iomem *)addr);
> > + else
> > + pci_write_config_byte(dev, addr, val);
> > +}
> > +
> > +static void sil_iowrite16(struct pci_dev *dev, u16 val, unsigned long addr)
> > +{
> > + if (pci_get_drvdata(dev))
> > + writew(val, (void __iomem *)addr);
> > + else
> > + pci_write_config_word(dev, addr, val);
> > +}
> > +
> > +static void sil_iowrite32(struct pci_dev *dev, u32 val, unsigned long addr)
> > +{
> > + if (pci_get_drvdata(dev))
> > + writel(val, (void __iomem *)addr);
> > + else
> > + pci_write_config_dword(dev, addr, val);
> > +}
> > +
>
> I think this could be further imporoved -- since we have to call
> pci_get_drvdata() in the accessors anyway, we could have used it to get the
> MMIO base right there, and thus be freed from the necessity to add it to the
> MMIO offset in the callers and also most probably from having it copied to
> hwif->hwif_data.
[...]
Or maybe we can remove sil_io* and always use PCI access (on the second
look none of sil_io* users seems to be performance critical)...
> > @@ -557,50 +513,80 @@ static unsigned int setup_mmio_siimage (
> [...]
> > + sil_iowrite8(dev, 0x72, base + 0xA1);
> > + sil_iowrite16(dev, 0x328A, base + 0xA2);
> > + sil_iowrite32(dev, 0x62DD62DD, base + 0xA4);
> > + sil_iowrite32(dev, 0x43924392, base + 0xA8);
> > + sil_iowrite32(dev, 0x40094009, base + 0xAC);
> > + sil_iowrite8(dev, 0x72, base ? (base + 0xE1) : 0xB1);
> > + sil_iowrite16(dev, 0x328A, base ? (base + 0xE2) : 0xB2);
> > + sil_iowrite32(dev, 0x62DD62DD, base ? (base + 0xE4) : 0xB4);
> > + sil_iowrite32(dev, 0x43924392, base ? (base + 0xE8) : 0xB8);
> > + sil_iowrite32(dev, 0x40094009, base ? (base + 0xEC) : 0xBC);
> > +
>
> Sigh, I was going to send a patch getting rid of these writes altogether
> last year -- there should be no point in setting PIO/DMA/UDMA timings here.
Heh, I know the feeling damn too well - I still have few low-prio patches
back from *2004* which need to be refreshed and pushed out...
> Maybe I'll submit it...
Just do it. ;)
Thanks,
Bart
next prev parent reply other threads:[~2008-04-27 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 18:51 [PATCH 2/3] siimage: add sil_* I/O ops Bartlomiej Zolnierkiewicz
2008-04-19 17:17 ` Sergei Shtylyov
2008-04-27 19:48 ` Bartlomiej Zolnierkiewicz [this message]
2008-04-29 4:45 ` Benjamin Herrenschmidt
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=200804272148.29131.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
/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;
as well as URLs for NNTP newsgroup(s).