[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3346d7cb9655eb111b4126d72a08499c6254fef.camel@suse.de>
Date: Tue, 16 Jun 2020 16:09:49 +0200
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: Simon Glass <sjg@...omium.org>
Cc: Matthias Brugger <mbrugger@...e.com>,
U-Boot Mailing List <u-boot@...ts.denx.de>,
Bin Meng <bmeng.cn@...il.com>, Marek Vasut <marex@...x.de>,
lk <linux-kernel@...r.kernel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Mark Kettenis <mark.kettenis@...all.nl>
Subject: Re: [PATCH v4 4/5] dm: pci: Assign controller device node to root
bridge
On Tue, 2020-06-16 at 07:43 -0600, Simon Glass wrote:
> Hi Nicolas,
>
> On Fri, 12 Jun 2020 at 10:47, Nicolas Saenz Julienne
> <nsaenzjulienne@...e.de> wrote:
> > There is no distinction in DT between the PCI controller device and the
> > root bridge, whereas such distinction exists from dm's perspective. Make
> > sure the root bridge ofnode is assigned to the controller's platform
> > device node.
> >
> > This permits setups like this to work correctly:
> >
> > pcie {
> > compatible = "...";
> > ...
> > dev {
> > reg = <0 0 0 0 0>;
> > ...
> > };
> > };
> >
> > Without this the dev node is assigned to the root bridge and the
> > actual device search starts one level lower than expected.
> >
> > Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
> > ---
> > drivers/pci/pci-uclass.c | 15 ++++++++++++++-
> > 1 file changed, 14 insertions(+), 1 deletion(-)
>
> Can you update the tests to handle this case please?
I'd be glad to, but I'm not familiar with the test FW in u-booy, coud give me
some pointers on where/how to test this?
Regards,
Nicolas
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists