u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: "Simon Glass" <sjg@chromium.org>, "Stefan Roese" <sr@denx.de>,
	"U-Boot Mailing List" <u-boot@lists.denx.de>,
	"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH u-boot] dm: pci: Fix handling of errors when scanning device
Date: Wed, 8 Sep 2021 14:02:56 +0200	[thread overview]
Message-ID: <20210908140256.393aeb9a@dellmb> (raw)
In-Reply-To: <CAEUhbmVfJ5vtWHVr3-KrHiifB3VU=1RnGncgsiUAGCT1=qcJOA@mail.gmail.com>

On Wed, 8 Sep 2021 09:06:28 +0800
Bin Meng <bmeng.cn@gmail.com> wrote:

> On Wed, Sep 8, 2021 at 12:07 AM Marek Behún <marek.behun@nic.cz>
> wrote:
> >
> > From: Pali Rohár <pali@kernel.org>
> >
> > Some PCIe controller's read_config() method support indicating error
> > directly via return value, but some cannot distinguish all-ones (or
> > all-zeros) read response from an error.
> >
> > The current code in pci_bind_bus_devices() interprets all-ones /
> > all-zeros in PCI_VENDOR_ID register as "nothing connected", and
> > continues the cycle, but an error returned via return value breaks
> > the cycle.
> >
> > This is wrong for the PCIe controllers which return this error via
> > return value.
> >
> > Handle all errors when reading PCI_VENDOR_ID the same way.
> >
> > This fixes enumeration of PCI devices for example when there is a
> > PCI bridge connected behind another PCI bridge and not all ports are
> > connected to a device, and the controller (for example Aardvark)
> > translates the UR error (Unsupported Request) as -EOPNOTSUPP.
> >
> > Signed-off-by: Pali Rohár <pali@kernel.org>
> > Signed-off-by: Marek Behún <marek.behun@nic.cz>
> > ---
> >  drivers/pci/pci-uclass.c | 9 +--------
> >  1 file changed, 1 insertion(+), 8 deletions(-)
> >  
> 
> Is it possible to update these PCI controller drivers to fill in
> vendor id to all zeros when there is an errror?

It is, but we think it is wrong. If the PCI controller supports
reporting errors, they should be propagated.

What we might want to change in those controller drivers, though, is
error numbers, so that they are the same for each controller. For
example Unsupported Request should be always translated to EOPNOTSUPP.

Marek

  reply	other threads:[~2021-09-08 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 16:07 [PATCH u-boot] dm: pci: Fix handling of errors when scanning device Marek Behún
2021-09-08  1:06 ` Bin Meng
2021-09-08 12:02   ` Marek Behún [this message]
2021-09-08 12:57     ` Bin Meng
2021-09-08 13:14       ` Pali Rohár
2021-09-10  7:02 ` Stefan Roese
2021-09-26 18:40 ` Simon Glass

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=20210908140256.393aeb9a@dellmb \
    --to=kabel@kernel.org \
    --cc=bmeng.cn@gmail.com \
    --cc=pali@kernel.org \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --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;
as well as URLs for NNTP newsgroup(s).