public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] rtl8169: use dm_pci_map_bar
Date: Thu, 13 Jun 2019 18:43:25 +0200	[thread overview]
Message-ID: <20190613164325.GD3258@ulmo> (raw)
In-Reply-To: <CAEUhbmUqqJeFL3hTDi+oGaHcz1eN0fnpgppCVbgMUYsuaHx1uQ@mail.gmail.com>

On Thu, Jun 13, 2019 at 03:16:10PM +0800, Bin Meng wrote:
> Hi Stefan,
> 
> On Thu, Jun 13, 2019 at 1:40 PM Stefan Roese <sr@denx.de> wrote:
> >
> > Added Bin, Joe and Thierry to Cc
> >
> > On 11.06.19 13:15, Patrick Wildt wrote:
> > > Hi,
> > >
> > > I have an rtl8169 on a macchiatobin and that card has a 64-bit
> > > memory address.  The current code only reads a single word, which
> > > means it can only support a 32-bit address.  By using dm_pci_map_bar
> > > we don't need to manually parse the register, we can just have it do
> > > its job.
> > >
> > > I'm not sure though if this works for all devices since the previous
> > > version had an explicit check for the device.
> > >
> > > Patrick
> > >
> > > Signed-off-by: Patrick Wildt <patrick@blueri.se>
> > >
> > > diff --git a/drivers/net/rtl8169.c b/drivers/net/rtl8169.c
> > > index 521e5909a2..f1d2ade253 100644
> > > --- a/drivers/net/rtl8169.c
> > > +++ b/drivers/net/rtl8169.c
> > > @@ -1182,22 +1182,11 @@ static int rtl8169_eth_probe(struct udevice *dev)
> > >       struct pci_child_platdata *pplat = dev_get_parent_platdata(dev);
> > >       struct rtl8169_private *priv = dev_get_priv(dev);
> > >       struct eth_pdata *plat = dev_get_platdata(dev);
> > > -     u32 iobase;
> > > -     int region;
> > >       int ret;
> > >
> > > -     debug("rtl8169: REALTEK RTL8169 @0x%x\n", iobase);
> > > -     switch (pplat->device) {
> > > -     case 0x8168:
> > > -             region = 2;
> > > -             break;
> > > -     default:
> > > -             region = 1;
> > > -             break;
> > > -     }
> > > -     dm_pci_read_config32(dev, PCI_BASE_ADDRESS_0 + region * 4, &iobase);
> > > -     iobase &= ~0xf;
> > > -     priv->iobase = (int)dm_pci_mem_to_phys(dev, iobase);
> > > +     priv->iobase = dm_pci_map_bar(dev, PCI_BASE_ADDRESS_2,
> > > +                                   PCI_REGION_MEM);
> > > +     printf("rtl8169: REALTEK RTL8169 @0x%x\n", priv->iobase);
> > >
> > >       ret = rtl_init(priv->iobase, dev->name, plat->enetaddr);
> > >       if (ret < 0) {
> >
> > Bin, Joe, Thierry,
> >
> > do you have any comments on this patch? Moving unconditionally to one
> > BAR instead of BAR1/2 depending on the chip version seems a bit
> > "brave".
> 
> Agreed that blinding setting one BAR for the iobase is not a good idea.

Agreed. I don't know whether it's actually required to differentiate
based on version, but I suppose the code is like that for a reason, so
better keep that.

Also, looking at dm_pci_map_bar() it doesn't look like that does
anything different than the existing code. It merely reads a single
32-bit register, so it doesn't properly deal with 64-bit BARs either.

I suppose that could be fixed in dm_pci_map_bar(), and then the fix
would automatically propagate to all users of that, which is good. But I
don't think it currently works correctly.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190613/81205155/attachment.sig>

  reply	other threads:[~2019-06-13 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 11:15 [U-Boot] rtl8169: use dm_pci_map_bar Patrick Wildt
2019-06-13  5:40 ` Stefan Roese
2019-06-13  7:16   ` Bin Meng
2019-06-13 16:43     ` Thierry Reding [this message]
2019-06-13 23:16       ` Patrick Wildt
2019-06-14  9:55         ` Thierry Reding

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=20190613164325.GD3258@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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