u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: "Marek Behún" <marek.behun@nic.cz>, "Simon Glass" <sjg@chromium.org>
Cc: 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: Fri, 10 Sep 2021 09:02:51 +0200	[thread overview]
Message-ID: <1f88ba42-49a9-1c54-db55-8b02963b6c99@denx.de> (raw)
In-Reply-To: <20210907160708.31547-1-marek.behun@nic.cz>

On 07.09.21 18:07, Marek Behún 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>

Reviewed-by: Stefan Roese <sr@denx.de>

Thanks,
Stefan

> ---
>   drivers/pci/pci-uclass.c | 9 +--------
>   1 file changed, 1 insertion(+), 8 deletions(-)
> 
> diff --git a/drivers/pci/pci-uclass.c b/drivers/pci/pci-uclass.c
> index ce2eb5da2c..4d0e938fe5 100644
> --- a/drivers/pci/pci-uclass.c
> +++ b/drivers/pci/pci-uclass.c
> @@ -856,10 +856,7 @@ int pci_bind_bus_devices(struct udevice *bus)
>   		/* Check only the first access, we don't expect problems */
>   		ret = pci_bus_read_config(bus, bdf, PCI_VENDOR_ID, &vendor,
>   					  PCI_SIZE_16);
> -		if (ret)
> -			goto error;
> -
> -		if (vendor == 0xffff || vendor == 0x0000)
> +		if (ret || vendor == 0xffff || vendor == 0x0000)
>   			continue;
>   
>   		pci_bus_read_config(bus, bdf, PCI_HEADER_TYPE,
> @@ -940,10 +937,6 @@ int pci_bind_bus_devices(struct udevice *bus)
>   	}
>   
>   	return 0;
> -error:
> -	printf("Cannot read bus configuration: %d\n", ret);
> -
> -	return ret;
>   }
>   
>   static void decode_regions(struct pci_controller *hose, ofnode parent_node,
> 


Viele Grüße,
Stefan

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr@denx.de

  parent reply	other threads:[~2021-09-10  7:03 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
2021-09-08 12:57     ` Bin Meng
2021-09-08 13:14       ` Pali Rohár
2021-09-10  7:02 ` Stefan Roese [this message]
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=1f88ba42-49a9-1c54-db55-8b02963b6c99@denx.de \
    --to=sr@denx.de \
    --cc=marek.behun@nic.cz \
    --cc=pali@kernel.org \
    --cc=sjg@chromium.org \
    --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).