From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Rob Herring <robh@kernel.org>, Linuxarm <linuxarm@huawei.com>,
mauro.chehab@huawei.com
Cc: Binghui Wang <wangbinghui@hisilicon.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Jingoo Han <jingoohan1@gmail.com>,
Xiaowei Song <songxiaowei@hisilicon.com>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
PCI <linux-pci@vger.kernel.org>,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v3 0/4] DT schema changes for HiKey970 PCIe hardware to work
Date: Thu, 5 Aug 2021 09:58:48 +0200 [thread overview]
Message-ID: <20210805095848.464cf85c@coco.lan> (raw)
In-Reply-To: <20210805094612.2bc2c78f@coco.lan>
Em Thu, 5 Aug 2021 09:46:12 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
> Em Wed, 4 Aug 2021 10:28:53 -0600
> Rob Herring <robh@kernel.org> escreveu:
>
> > On Wed, Aug 04, 2021 at 08:50:45AM +0200, Mauro Carvalho Chehab wrote:
> > > Em Tue, 3 Aug 2021 16:11:42 -0600
> > > Rob Herring <robh+dt@kernel.org> escreveu:
> > >
> > > > On Mon, Aug 2, 2021 at 10:39 PM Mauro Carvalho Chehab
> > > > <mchehab+huawei@kernel.org> wrote:
> > > > >
> > > > > Hi Rob,
> > > > >
> > > > > That's the third version of the DT bindings for Kirin 970 PCIE and its
> > > > > corresponding PHY.
> > > > >
> > > > > It is identical to v2, except by:
> > > > > - pcie@7,0 { // Lane 7: Ethernet
> > > > > + pcie@7,0 { // Lane 6: Ethernet
> > > >
> > > > Can you check whether you have DT node links in sysfs for the PCI
> > > > devices? If you don't, then something is wrong still in the topology
> > > > or the PCI core is failing to set the DT node pointer in struct
> > > > device. Though you don't rely on that currently, we want the topology
> > > > to match. It's possible this never worked on arm/arm64 as mainly
> > > > powerpc relied on this.
> > > >
> > > > I'd like some way to validate the DT matches the PCI topology. We
> > > > could have a tool that generates the DT structure based on the PCI
> > > > topology.
> > >
> > > The of_node node link is on those places:
> > >
> > > $ find /sys/devices/platform/soc/f4000000.pcie/ -name of_node
> > > /sys/devices/platform/soc/f4000000.pcie/of_node
> > > /sys/devices/platform/soc/f4000000.pcie/pci0000:00/0000:00:00.0/of_node
> > > /sys/devices/platform/soc/f4000000.pcie/pci0000:00/0000:00:00.0/pci_bus/0000:01/of_node
> > > /sys/devices/platform/soc/f4000000.pcie/pci0000:00/pci_bus/0000:00/of_node
> >
> > Looks like we're missing some...
> >
> > It's not immediately obvious to me what's wrong here. Only the root
> > bus is getting it's DT node set. The relevant code is pci_scan_device(),
> > pci_set_of_node() and pci_set_bus_of_node(). Give me a few days to try
> > to reproduce and debug it.
>
> I added a printk on both pci_set_*of_node() functions:
>
> [ 4.872991] (null): pci_set_bus_of_node: of_node: /soc/pcie@f4000000
> [ 4.913806] (null): pci_set_of_node: of_node: /soc/pcie@f4000000
> [ 4.978102] pci_bus 0000:01: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
> [ 4.990622] (null): pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
> [ 5.052383] pci_bus 0000:02: pci_set_bus_of_node: of_node: (null)
> [ 5.059263] (null): pci_set_of_node: of_node: (null)
> [ 5.085552] (null): pci_set_of_node: of_node: (null)
> [ 5.112073] (null): pci_set_of_node: of_node: (null)
> [ 5.138320] (null): pci_set_of_node: of_node: (null)
> [ 5.164673] (null): pci_set_of_node: of_node: (null)
> [ 5.233759] pci_bus 0000:03: pci_set_bus_of_node: of_node: (null)
> [ 5.240539] (null): pci_set_of_node: of_node: (null)
> [ 5.310545] pci_bus 0000:04: pci_set_bus_of_node: of_node: (null)
> [ 5.324719] pci_bus 0000:05: pci_set_bus_of_node: of_node: (null)
> [ 5.338914] pci_bus 0000:06: pci_set_bus_of_node: of_node: (null)
> [ 5.345516] (null): pci_set_of_node: of_node: (null)
> [ 5.415795] pci_bus 0000:07: pci_set_bus_of_node: of_node: (null)
The enclosed patch makes the above a clearer:
[ 4.800975] (null): pci_set_bus_of_node: of_node: /soc/pcie@f4000000
[ 4.855983] pci 0000:00:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000
[ 4.879169] pci_bus 0000:01: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
[ 4.900602] pci 0000:01:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
[ 4.953086] pci_bus 0000:02: pci_set_bus_of_node: of_node: (null)
[ 4.968821] pci 0000:02:01.0: pci_set_of_node: of_node: (null)
[ 5.003538] pci 0000:02:04.0: pci_set_of_node: of_node: (null)
[ 5.041348] pci 0000:02:05.0: pci_set_of_node: of_node: (null)
[ 5.092770] pci 0000:02:07.0: pci_set_of_node: of_node: (null)
[ 5.118298] pci 0000:02:09.0: pci_set_of_node: of_node: (null)
[ 5.178215] pci_bus 0000:03: pci_set_bus_of_node: of_node: (null)
[ 5.198433] pci 0000:03:00.0: pci_set_of_node: of_node: (null)
[ 5.233330] pci_bus 0000:04: pci_set_bus_of_node: of_node: (null)
[ 5.247071] pci_bus 0000:05: pci_set_bus_of_node: of_node: (null)
[ 5.260898] pci_bus 0000:06: pci_set_bus_of_node: of_node: (null)
[ 5.293764] pci 0000:06:00.0: pci_set_of_node: of_node: (null)
[ 5.332808] pci_bus 0000:07: pci_set_bus_of_node: of_node: (null)
>
> It sounds that the parent is missing when pci_set_bus_of_node() is
> called on some places. I'll try to identify why.
>
> Thanks,
> Mauro
Thanks,
Mauro
[PATCH] pci: setup PCI before setting the OF node
With this change, it is easier to add a debug printk at
pci_set_of_node() in order to address possible issues.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
index 79177ac37880..c5dfc1afb1d3 100644
--- a/drivers/pci/probe.c
+++ b/drivers/pci/probe.c
@@ -2374,15 +2374,14 @@ static struct pci_dev *pci_scan_device(struct pci_bus *bus, int devfn)
dev->vendor = l & 0xffff;
dev->device = (l >> 16) & 0xffff;
- pci_set_of_node(dev);
-
if (pci_setup_device(dev)) {
- pci_release_of_node(dev);
pci_bus_put(dev->bus);
kfree(dev);
return NULL;
}
+ pci_set_of_node(dev);
+
return dev;
}
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Rob Herring <robh@kernel.org>, Linuxarm <linuxarm@huawei.com>,
mauro.chehab@huawei.com
Cc: Binghui Wang <wangbinghui@hisilicon.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Jingoo Han <jingoohan1@gmail.com>,
Xiaowei Song <songxiaowei@hisilicon.com>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
PCI <linux-pci@vger.kernel.org>,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v3 0/4] DT schema changes for HiKey970 PCIe hardware to work
Date: Thu, 5 Aug 2021 09:58:48 +0200 [thread overview]
Message-ID: <20210805095848.464cf85c@coco.lan> (raw)
In-Reply-To: <20210805094612.2bc2c78f@coco.lan>
Em Thu, 5 Aug 2021 09:46:12 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
> Em Wed, 4 Aug 2021 10:28:53 -0600
> Rob Herring <robh@kernel.org> escreveu:
>
> > On Wed, Aug 04, 2021 at 08:50:45AM +0200, Mauro Carvalho Chehab wrote:
> > > Em Tue, 3 Aug 2021 16:11:42 -0600
> > > Rob Herring <robh+dt@kernel.org> escreveu:
> > >
> > > > On Mon, Aug 2, 2021 at 10:39 PM Mauro Carvalho Chehab
> > > > <mchehab+huawei@kernel.org> wrote:
> > > > >
> > > > > Hi Rob,
> > > > >
> > > > > That's the third version of the DT bindings for Kirin 970 PCIE and its
> > > > > corresponding PHY.
> > > > >
> > > > > It is identical to v2, except by:
> > > > > - pcie@7,0 { // Lane 7: Ethernet
> > > > > + pcie@7,0 { // Lane 6: Ethernet
> > > >
> > > > Can you check whether you have DT node links in sysfs for the PCI
> > > > devices? If you don't, then something is wrong still in the topology
> > > > or the PCI core is failing to set the DT node pointer in struct
> > > > device. Though you don't rely on that currently, we want the topology
> > > > to match. It's possible this never worked on arm/arm64 as mainly
> > > > powerpc relied on this.
> > > >
> > > > I'd like some way to validate the DT matches the PCI topology. We
> > > > could have a tool that generates the DT structure based on the PCI
> > > > topology.
> > >
> > > The of_node node link is on those places:
> > >
> > > $ find /sys/devices/platform/soc/f4000000.pcie/ -name of_node
> > > /sys/devices/platform/soc/f4000000.pcie/of_node
> > > /sys/devices/platform/soc/f4000000.pcie/pci0000:00/0000:00:00.0/of_node
> > > /sys/devices/platform/soc/f4000000.pcie/pci0000:00/0000:00:00.0/pci_bus/0000:01/of_node
> > > /sys/devices/platform/soc/f4000000.pcie/pci0000:00/pci_bus/0000:00/of_node
> >
> > Looks like we're missing some...
> >
> > It's not immediately obvious to me what's wrong here. Only the root
> > bus is getting it's DT node set. The relevant code is pci_scan_device(),
> > pci_set_of_node() and pci_set_bus_of_node(). Give me a few days to try
> > to reproduce and debug it.
>
> I added a printk on both pci_set_*of_node() functions:
>
> [ 4.872991] (null): pci_set_bus_of_node: of_node: /soc/pcie@f4000000
> [ 4.913806] (null): pci_set_of_node: of_node: /soc/pcie@f4000000
> [ 4.978102] pci_bus 0000:01: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
> [ 4.990622] (null): pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
> [ 5.052383] pci_bus 0000:02: pci_set_bus_of_node: of_node: (null)
> [ 5.059263] (null): pci_set_of_node: of_node: (null)
> [ 5.085552] (null): pci_set_of_node: of_node: (null)
> [ 5.112073] (null): pci_set_of_node: of_node: (null)
> [ 5.138320] (null): pci_set_of_node: of_node: (null)
> [ 5.164673] (null): pci_set_of_node: of_node: (null)
> [ 5.233759] pci_bus 0000:03: pci_set_bus_of_node: of_node: (null)
> [ 5.240539] (null): pci_set_of_node: of_node: (null)
> [ 5.310545] pci_bus 0000:04: pci_set_bus_of_node: of_node: (null)
> [ 5.324719] pci_bus 0000:05: pci_set_bus_of_node: of_node: (null)
> [ 5.338914] pci_bus 0000:06: pci_set_bus_of_node: of_node: (null)
> [ 5.345516] (null): pci_set_of_node: of_node: (null)
> [ 5.415795] pci_bus 0000:07: pci_set_bus_of_node: of_node: (null)
The enclosed patch makes the above a clearer:
[ 4.800975] (null): pci_set_bus_of_node: of_node: /soc/pcie@f4000000
[ 4.855983] pci 0000:00:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000
[ 4.879169] pci_bus 0000:01: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
[ 4.900602] pci 0000:01:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
[ 4.953086] pci_bus 0000:02: pci_set_bus_of_node: of_node: (null)
[ 4.968821] pci 0000:02:01.0: pci_set_of_node: of_node: (null)
[ 5.003538] pci 0000:02:04.0: pci_set_of_node: of_node: (null)
[ 5.041348] pci 0000:02:05.0: pci_set_of_node: of_node: (null)
[ 5.092770] pci 0000:02:07.0: pci_set_of_node: of_node: (null)
[ 5.118298] pci 0000:02:09.0: pci_set_of_node: of_node: (null)
[ 5.178215] pci_bus 0000:03: pci_set_bus_of_node: of_node: (null)
[ 5.198433] pci 0000:03:00.0: pci_set_of_node: of_node: (null)
[ 5.233330] pci_bus 0000:04: pci_set_bus_of_node: of_node: (null)
[ 5.247071] pci_bus 0000:05: pci_set_bus_of_node: of_node: (null)
[ 5.260898] pci_bus 0000:06: pci_set_bus_of_node: of_node: (null)
[ 5.293764] pci 0000:06:00.0: pci_set_of_node: of_node: (null)
[ 5.332808] pci_bus 0000:07: pci_set_bus_of_node: of_node: (null)
>
> It sounds that the parent is missing when pci_set_bus_of_node() is
> called on some places. I'll try to identify why.
>
> Thanks,
> Mauro
Thanks,
Mauro
[PATCH] pci: setup PCI before setting the OF node
With this change, it is easier to add a debug printk at
pci_set_of_node() in order to address possible issues.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
index 79177ac37880..c5dfc1afb1d3 100644
--- a/drivers/pci/probe.c
+++ b/drivers/pci/probe.c
@@ -2374,15 +2374,14 @@ static struct pci_dev *pci_scan_device(struct pci_bus *bus, int devfn)
dev->vendor = l & 0xffff;
dev->device = (l >> 16) & 0xffff;
- pci_set_of_node(dev);
-
if (pci_setup_device(dev)) {
- pci_release_of_node(dev);
pci_bus_put(dev->bus);
kfree(dev);
return NULL;
}
+ pci_set_of_node(dev);
+
return dev;
}
next prev parent reply other threads:[~2021-08-05 7:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 4:38 [PATCH v3 0/4] DT schema changes for HiKey970 PCIe hardware to work Mauro Carvalho Chehab
2021-08-03 4:38 ` Mauro Carvalho Chehab
2021-08-03 4:38 ` [PATCH v3 1/4] dt-bindings: PCI: kirin: Fix compatible string Mauro Carvalho Chehab
2021-08-03 22:22 ` Rob Herring
2021-08-03 4:38 ` [PATCH v3 2/4] dt-bindings: PCI: kirin: Convert kirin-pcie.txt to yaml Mauro Carvalho Chehab
2021-08-03 22:27 ` Rob Herring
2021-08-03 4:38 ` [PATCH v3 3/4] dt-bindings: PCI: kirin: Add support for Kirin970 Mauro Carvalho Chehab
2021-08-03 4:38 ` [PATCH v3 4/4] dt-bindings: phy: Add bindings for HiKey 970 PCIe PHY Mauro Carvalho Chehab
2021-08-03 4:38 ` Mauro Carvalho Chehab
2021-08-03 22:29 ` Rob Herring
2021-08-03 22:29 ` Rob Herring
2021-08-03 22:11 ` [PATCH v3 0/4] DT schema changes for HiKey970 PCIe hardware to work Rob Herring
2021-08-03 22:11 ` Rob Herring
2021-08-04 6:50 ` Mauro Carvalho Chehab
2021-08-04 6:50 ` Mauro Carvalho Chehab
2021-08-04 16:28 ` Rob Herring
2021-08-04 16:28 ` Rob Herring
2021-08-05 7:46 ` Mauro Carvalho Chehab
2021-08-05 7:46 ` Mauro Carvalho Chehab
2021-08-05 7:58 ` Mauro Carvalho Chehab [this message]
2021-08-05 7:58 ` Mauro Carvalho Chehab
2021-08-06 16:23 ` Rob Herring
2021-08-06 16:23 ` Rob Herring
2021-08-10 9:42 ` Mauro Carvalho Chehab
2021-08-10 9:42 ` Mauro Carvalho Chehab
2021-08-10 13:44 ` Rob Herring
2021-08-10 13:44 ` Rob Herring
2021-08-10 14:20 ` Mauro Carvalho Chehab
2021-08-10 14:20 ` Mauro Carvalho Chehab
2021-08-10 17:13 ` Rob Herring
2021-08-10 17:13 ` Rob Herring
2021-08-10 17:52 ` Rob Herring
2021-08-10 17:52 ` Rob Herring
2021-08-11 7:11 ` Mauro Carvalho Chehab
2021-08-11 7:11 ` Mauro Carvalho Chehab
2021-08-11 6:46 ` Mauro Carvalho Chehab
2021-08-11 6:46 ` Mauro Carvalho Chehab
2021-08-12 3:13 ` Rob Herring
2021-08-12 3:13 ` Rob Herring
2021-08-12 7:48 ` Mauro Carvalho Chehab
2021-08-12 7:48 ` Mauro Carvalho Chehab
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=20210805095848.464cf85c@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=mauro.chehab@huawei.com \
--cc=robh@kernel.org \
--cc=songxiaowei@hisilicon.com \
--cc=wangbinghui@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.