From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Linuxarm <linuxarm@huawei.com>,
mauro.chehab@huawei.com, 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: Wed, 11 Aug 2021 09:11:15 +0200 [thread overview]
Message-ID: <20210811091115.03b36daa@coco.lan> (raw)
In-Reply-To: <CAL_JsqKr9csV5fPZxD=kRRB5W6RCjHz0VsP6-nx0RQt8mgVJ5w@mail.gmail.com>
Em Tue, 10 Aug 2021 11:52:34 -0600
Rob Herring <robh@kernel.org> escreveu:
> > > > > pcie@0,0 { // Lane 0: PCIe switch: Bus 1, Device 0
> > > > > reg = <0x80 0 0 0 0>;
> > > >
> > > > s/0x80/0/
> > > >
> > > > > compatible = "pciclass,0604";
> > > > > device_type = "pci";
> > > > > #address-cells = <3>;
> > > > > #size-cells = <2>;
> > > > > ranges;
> > > > > bus-range = <0x01 0xff>;
> > > > > msi-parent = <&its_pcie>;
> > > > >
> > > > > pcie@0,0 { // Lane 0: upstream
> > > > > reg = <0x010000 0 0 0 0>;
> > > >
> > > > While technically correct having the bus# in the address, that doesn't
> > > > work for FDT since we don't know the bus assignment. So we should just
> > > > use 0.
> > >
> > > Using 0 causes DTB compilation to produce a warning, due to the
> > > bus-range.
>
> What's the warning? 'bus-range' should be optional.
With this DT schema (simplified to show only relevant bits):
pcie@f4000000 {
bus-range = <0x00 0xff>;
pcie@0,0 { // Lane 0: PCIe switch: Bus 1, Device 0
bus-range = <0x01 0xff>;
pcie@0,0 { // Lane 0: upstream
reg = <0x0000 0 0 0 0>;
pcie@1,0 { // Lane 4: M.2
reg = <0x0800 0 0 0 0>;
};
pcie@5,0 { // Lane 5: Mini PCIe
reg = <0x2800 0 0 0 0>;
};
pcie@7,0 { // Lane 6: Ethernet
reg = <0x3800 0 0 0 0>;
};
};
};
};
This is the compilation warning:
$ make dtbs
arch/arm64/boot/dts/hisilicon/hi3670.dtsi:735.5-29: Warning (pci_device_bus_num): /soc/pcie@f4000000/pcie@0,0/pcie@0,0:bus-range: PCI bus number 0 out of range, expected (1 - 1)
This is solved by changing:
pcie@0,0 { // Lane 0: upstream
reg = <0x0000 0 0 0 0>;
to:
pcie@0,0 { // Lane 0: upstream
reg = <0x010000 0 0 0 0>;
>
> > > Without the bus-range, there will be runtime warnings,
> > > as this will be assigned as bus 1.
> >
> > Okay, that might be something we need to fix.
>
> Actually, I don't see how there's a problem. First, the only place we
> read 'bus-range' is of_pci_parse_bus_range() and that's only called
> for the host bridge. Any other occurrence of 'bus-range' should be
> ignored. The only place we read 'reg' is of_pci_get_devfn() and we
> mask just the devfn bits.
>
> > [ 4.992572] pci_bus 0000:00: root bus resource [bus 00-01]
>
> I don't see any way this can happen other than pcie@f4000000 node
> containing 'bus-range = <0 1>;'. It comes from
> pci_host_bridge.windows.
Yeah, you're right. On the first versions, 'bus-range = <0 1>;' was used,
just like:
arch/arm64/boot/dts/hisilicon/hi3660.dtsi
(I have a fixup patch fixing the warning on Kirin 960 due to that)
Ok, I did another test here: if I drop both dma-range, it will output:
[ 3.778028] kirin-pcie f4000000.pcie: No bus range found for /soc/pcie@f4000000, using [bus 00-ff]
But no conflict warnings. So, I guess dropping bus-range and the explicit
bus 1 setting at "reg" is a clean approach.
As a reference, this is the dmesg log here (with OF debug turned on):
# dmesg|grep -i pci
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.0-rc1+ root=UUID=646147e1-d186-44cc-b0d2-60c42f8dcc6d ro drm.debug=0x6 earlycon=pl011,0xfff32000,115200 console=tty0 console=ttyAMA6,115200n8 root=/dev/sdd12 rootwait rw quiet efi=noruntime drm.debug=0x06 "dyndbg=file drivers/pci/of.c +p; drivers/gpu/* +p; file drivers/pci/of.c +p; drivers/spmi/* +p; file drivers/pci/of.c +p; drivers/mfd/* +p; file drivers/pci/of.c +p; drivers/regulator/* +p; file drivers/pci/of.c +p; drivers/usb/core/hub.c +p" no_console_suspend loglevel=9 kernel.panic=5
[ 0.000000] Unknown command line parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.0-rc1+ dyndbg=file drivers/pci/of.c +p; drivers/gpu/* +p; file drivers/pci/of.c +p; drivers/spmi/* +p; file drivers/pci/of.c +p; drivers/mfd/* +p; file drivers/pci/of.c +p; drivers/regulator/* +p; file drivers/pci/of.c +p; drivers/usb/core/hub.c +p
[ 0.725101] PCI: CLS 0 bytes, default 64
[ 1.520828] ehci-pci: EHCI PCI platform driver
[ 1.521022] ohci-pci: OHCI PCI platform driver
[ 2.204793] dyndbg=file drivers/pci/of.c +p; drivers/gpu/* +p; file drivers/pci/of.c +p; drivers/spmi/* +p; file drivers/pci/of.c +p; drivers/mfd/* +p; file drivers/pci/of.c +p; drivers/regulator/* +p; file drivers/pci/of.c +p; drivers/usb/core/hub.c +p
[ 3.767252] kirin-pcie f4000000.pcie: host bridge /soc/pcie@f4000000 ranges:
[ 3.778028] kirin-pcie f4000000.pcie: No bus range found for /soc/pcie@f4000000, using [bus 00-ff]
[ 3.792466] kirin-pcie f4000000.pcie: Parsing ranges property...
[ 3.801919] kirin-pcie f4000000.pcie: MEM 0x00f6000000..0x00f7ffffff -> 0x0000000000
[ 3.813680] kirin-pcie f4000000.pcie: invalid resource
[ 3.822189] kirin-pcie f4000000.pcie: iATU unroll: enabled
[ 3.831159] kirin-pcie f4000000.pcie: Detected iATU regions: 8 outbound, 8 inbound
[ 3.943155] kirin-pcie f4000000.pcie: Link up
[ 3.956821] (null): pci_set_bus_of_node: of_node: /soc/pcie@f4000000
[ 3.979143] kirin-pcie f4000000.pcie: PCI host bridge to bus 0000:00
[ 3.989441] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 3.998050] pci_bus 0000:00: root bus resource [mem 0xf6000000-0xf7ffffff] (bus address [0x00000000-0x01ffffff])
[ 4.011965] pci 0000:00:00.0: [19e5:3670] type 01 class 0x060400
[ 4.021177] pci 0000:00:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
[ 4.031041] pci 0000:00:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000
[ 4.041362] pci 0000:00:00.0: supports D1 D2
[ 4.049191] pci 0000:00:00.0: PME# supported from D0 D1 D2 D3hot
[ 4.059554] pci_bus 0000:01: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
[ 4.071133] pci 0000:01:00.0: [10b5:8606] type 01 class 0x060400
[ 4.080831] pci 0000:01:00.0: reg 0x10: [mem 0xf6000000-0xf601ffff]
[ 4.103511] pci 0000:01:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
[ 4.115403] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[ 4.139816] pci 0000:01:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.157297] pci_bus 0000:02: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.172380] pci 0000:02:01.0: [10b5:8606] type 01 class 0x060400
[ 4.182279] pci 0000:02:01.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.197047] pci 0000:02:01.0: PME# supported from D0 D3hot D3cold
[ 4.207583] pci 0000:02:04.0: [10b5:8606] type 01 class 0x060400
[ 4.217659] pci 0000:02:04.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.234551] pci 0000:02:04.0: PME# supported from D0 D3hot D3cold
[ 4.254284] pci 0000:02:05.0: [10b5:8606] type 01 class 0x060400
[ 4.267668] pci 0000:02:05.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.282530] pci 0000:02:05.0: PME# supported from D0 D3hot D3cold
[ 4.295077] pci 0000:02:07.0: [10b5:8606] type 01 class 0x060400
[ 4.306032] pci 0000:02:07.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.320927] pci 0000:02:07.0: PME# supported from D0 D3hot D3cold
[ 4.333414] pci 0000:02:09.0: [10b5:8606] type 01 class 0x060400
[ 4.340439] pci 0000:02:09.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.350084] pci 0000:02:09.0: PME# supported from D0 D3hot D3cold
[ 4.358150] pci 0000:02:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.366379] pci 0000:02:04.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.374515] pci 0000:02:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.382682] pci 0000:02:07.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.390834] pci 0000:02:09.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.399079] pci_bus 0000:03: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@1,0
[ 4.409309] pci 0000:03:00.0: [144d:a809] type 00 class 0x010802
[ 4.415564] pci 0000:03:00.0: reg 0x10: [mem 0xf6000000-0xf6003fff 64bit]
[ 4.422769] pci 0000:03:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@1,0
[ 4.433782] pci 0000:03:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[ 4.449954] pci_bus 0000:03: busn_res: [bus 03-ff] end is updated to 03
[ 4.456836] pci_bus 0000:04: pci_set_bus_of_node: of_node: (null)
[ 4.457918] pci_bus 0000:04: busn_res: [bus 04-ff] end is updated to 04
[ 4.478895] pci_bus 0000:05: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@5,0
[ 4.491772] pci_bus 0000:05: busn_res: [bus 05-ff] end is updated to 05
[ 4.503438] pci_bus 0000:06: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@7,0
[ 4.529140] pci 0000:06:00.0: [10ec:8168] type 00 class 0x020000
[ 4.535374] pci 0000:06:00.0: reg 0x10: [io 0x0000-0x00ff]
[ 4.541229] pci 0000:06:00.0: reg 0x18: [mem 0xf7000000-0xf7000fff 64bit]
[ 4.548194] pci 0000:06:00.0: reg 0x20: [mem 0xf7200000-0xf7203fff 64bit pref]
[ 4.561063] pci 0000:06:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@7,0
[ 4.582075] pci 0000:06:00.0: supports D1 D2
[ 4.586357] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 4.594727] pci_bus 0000:06: busn_res: [bus 06-ff] end is updated to 06
[ 4.601538] pci_bus 0000:07: pci_set_bus_of_node: of_node: (null)
[ 4.608473] pci_bus 0000:07: busn_res: [bus 07-ff] end is updated to 07
[ 4.615124] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 07
[ 4.621810] pci 0000:00:00.0: BAR 0: assigned [mem 0xf6000000-0xf6ffffff]
[ 4.628606] pci 0000:00:00.0: BAR 14: assigned [mem 0xf7000000-0xf72fffff]
[ 4.628610] pci 0000:00:00.0: BAR 15: assigned [mem 0xf7300000-0xf73fffff pref]
[ 4.642813] pci 0000:00:00.0: BAR 13: no space for [io size 0x1000]
[ 4.649174] pci 0000:00:00.0: BAR 13: failed to assign [io size 0x1000]
[ 4.661518] pci 0000:01:00.0: BAR 14: assigned [mem 0xf7000000-0xf71fffff]
[ 4.669074] pci 0000:01:00.0: BAR 15: assigned [mem 0xf7300000-0xf73fffff 64bit pref]
[ 4.677066] pci 0000:01:00.0: BAR 0: assigned [mem 0xf7200000-0xf721ffff]
[ 4.683891] pci 0000:01:00.0: BAR 13: no space for [io size 0x1000]
[ 4.690252] pci 0000:01:00.0: BAR 13: failed to assign [io size 0x1000]
[ 4.690266] pci 0000:02:01.0: BAR 14: assigned [mem 0xf7000000-0xf70fffff]
[ 4.690270] pci 0000:02:07.0: BAR 14: assigned [mem 0xf7100000-0xf71fffff]
[ 4.710728] pci 0000:02:07.0: BAR 15: assigned [mem 0xf7300000-0xf73fffff 64bit pref]
[ 4.727780] pci 0000:02:07.0: BAR 13: no space for [io size 0x1000]
[ 4.727783] pci 0000:02:07.0: BAR 13: failed to assign [io size 0x1000]
[ 4.727790] pci 0000:03:00.0: BAR 0: assigned [mem 0xf7000000-0xf7003fff 64bit]
[ 4.727904] pci 0000:02:01.0: PCI bridge to [bus 03]
[ 4.753165] pci 0000:02:01.0: bridge window [mem 0xf7000000-0xf70fffff]
[ 4.769738] pci 0000:02:04.0: PCI bridge to [bus 04]
[ 4.774843] pci 0000:02:05.0: PCI bridge to [bus 05]
[ 4.779959] pci 0000:06:00.0: BAR 4: assigned [mem 0xf7300000-0xf7303fff 64bit pref]
[ 4.787839] pci 0000:06:00.0: BAR 2: assigned [mem 0xf7100000-0xf7100fff 64bit]
[ 4.795273] pci 0000:06:00.0: BAR 0: no space for [io size 0x0100]
[ 4.801543] pci 0000:06:00.0: BAR 0: failed to assign [io size 0x0100]
[ 4.808159] pci 0000:02:07.0: PCI bridge to [bus 06]
[ 4.813166] pci 0000:02:07.0: bridge window [mem 0xf7100000-0xf71fffff]
[ 4.819981] pci 0000:02:07.0: bridge window [mem 0xf7300000-0xf73fffff 64bit pref]
[ 4.827782] pci 0000:02:09.0: PCI bridge to [bus 07]
[ 4.832871] pci 0000:01:00.0: PCI bridge to [bus 02-07]
[ 4.838138] pci 0000:01:00.0: bridge window [mem 0xf7000000-0xf71fffff]
[ 4.844952] pci 0000:01:00.0: bridge window [mem 0xf7300000-0xf73fffff 64bit pref]
[ 4.852751] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[ 4.857980] pci 0000:00:00.0: bridge window [mem 0xf7000000-0xf72fffff]
[ 4.864770] pci 0000:00:00.0: bridge window [mem 0xf7300000-0xf73fffff pref]
[ 4.881547] pcieport 0000:00:00.0: PME: Signaling with IRQ 58
[ 4.888905] pcieport 0000:00:00.0: AER: enabled with IRQ 58
[ 4.895013] pcieport 0000:01:00.0: enabling device (0000 -> 0002)
[ 4.903260] pcieport 0000:02:01.0: enabling device (0000 -> 0002)
[ 4.914761] pcieport 0000:02:07.0: enabling device (0000 -> 0002)
[ 4.928984] nvme nvme0: pci function 0000:03:00.0
Thanks,
Mauro
--
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>
Cc: Linuxarm <linuxarm@huawei.com>,
mauro.chehab@huawei.com, 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: Wed, 11 Aug 2021 09:11:15 +0200 [thread overview]
Message-ID: <20210811091115.03b36daa@coco.lan> (raw)
In-Reply-To: <CAL_JsqKr9csV5fPZxD=kRRB5W6RCjHz0VsP6-nx0RQt8mgVJ5w@mail.gmail.com>
Em Tue, 10 Aug 2021 11:52:34 -0600
Rob Herring <robh@kernel.org> escreveu:
> > > > > pcie@0,0 { // Lane 0: PCIe switch: Bus 1, Device 0
> > > > > reg = <0x80 0 0 0 0>;
> > > >
> > > > s/0x80/0/
> > > >
> > > > > compatible = "pciclass,0604";
> > > > > device_type = "pci";
> > > > > #address-cells = <3>;
> > > > > #size-cells = <2>;
> > > > > ranges;
> > > > > bus-range = <0x01 0xff>;
> > > > > msi-parent = <&its_pcie>;
> > > > >
> > > > > pcie@0,0 { // Lane 0: upstream
> > > > > reg = <0x010000 0 0 0 0>;
> > > >
> > > > While technically correct having the bus# in the address, that doesn't
> > > > work for FDT since we don't know the bus assignment. So we should just
> > > > use 0.
> > >
> > > Using 0 causes DTB compilation to produce a warning, due to the
> > > bus-range.
>
> What's the warning? 'bus-range' should be optional.
With this DT schema (simplified to show only relevant bits):
pcie@f4000000 {
bus-range = <0x00 0xff>;
pcie@0,0 { // Lane 0: PCIe switch: Bus 1, Device 0
bus-range = <0x01 0xff>;
pcie@0,0 { // Lane 0: upstream
reg = <0x0000 0 0 0 0>;
pcie@1,0 { // Lane 4: M.2
reg = <0x0800 0 0 0 0>;
};
pcie@5,0 { // Lane 5: Mini PCIe
reg = <0x2800 0 0 0 0>;
};
pcie@7,0 { // Lane 6: Ethernet
reg = <0x3800 0 0 0 0>;
};
};
};
};
This is the compilation warning:
$ make dtbs
arch/arm64/boot/dts/hisilicon/hi3670.dtsi:735.5-29: Warning (pci_device_bus_num): /soc/pcie@f4000000/pcie@0,0/pcie@0,0:bus-range: PCI bus number 0 out of range, expected (1 - 1)
This is solved by changing:
pcie@0,0 { // Lane 0: upstream
reg = <0x0000 0 0 0 0>;
to:
pcie@0,0 { // Lane 0: upstream
reg = <0x010000 0 0 0 0>;
>
> > > Without the bus-range, there will be runtime warnings,
> > > as this will be assigned as bus 1.
> >
> > Okay, that might be something we need to fix.
>
> Actually, I don't see how there's a problem. First, the only place we
> read 'bus-range' is of_pci_parse_bus_range() and that's only called
> for the host bridge. Any other occurrence of 'bus-range' should be
> ignored. The only place we read 'reg' is of_pci_get_devfn() and we
> mask just the devfn bits.
>
> > [ 4.992572] pci_bus 0000:00: root bus resource [bus 00-01]
>
> I don't see any way this can happen other than pcie@f4000000 node
> containing 'bus-range = <0 1>;'. It comes from
> pci_host_bridge.windows.
Yeah, you're right. On the first versions, 'bus-range = <0 1>;' was used,
just like:
arch/arm64/boot/dts/hisilicon/hi3660.dtsi
(I have a fixup patch fixing the warning on Kirin 960 due to that)
Ok, I did another test here: if I drop both dma-range, it will output:
[ 3.778028] kirin-pcie f4000000.pcie: No bus range found for /soc/pcie@f4000000, using [bus 00-ff]
But no conflict warnings. So, I guess dropping bus-range and the explicit
bus 1 setting at "reg" is a clean approach.
As a reference, this is the dmesg log here (with OF debug turned on):
# dmesg|grep -i pci
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.0-rc1+ root=UUID=646147e1-d186-44cc-b0d2-60c42f8dcc6d ro drm.debug=0x6 earlycon=pl011,0xfff32000,115200 console=tty0 console=ttyAMA6,115200n8 root=/dev/sdd12 rootwait rw quiet efi=noruntime drm.debug=0x06 "dyndbg=file drivers/pci/of.c +p; drivers/gpu/* +p; file drivers/pci/of.c +p; drivers/spmi/* +p; file drivers/pci/of.c +p; drivers/mfd/* +p; file drivers/pci/of.c +p; drivers/regulator/* +p; file drivers/pci/of.c +p; drivers/usb/core/hub.c +p" no_console_suspend loglevel=9 kernel.panic=5
[ 0.000000] Unknown command line parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.0-rc1+ dyndbg=file drivers/pci/of.c +p; drivers/gpu/* +p; file drivers/pci/of.c +p; drivers/spmi/* +p; file drivers/pci/of.c +p; drivers/mfd/* +p; file drivers/pci/of.c +p; drivers/regulator/* +p; file drivers/pci/of.c +p; drivers/usb/core/hub.c +p
[ 0.725101] PCI: CLS 0 bytes, default 64
[ 1.520828] ehci-pci: EHCI PCI platform driver
[ 1.521022] ohci-pci: OHCI PCI platform driver
[ 2.204793] dyndbg=file drivers/pci/of.c +p; drivers/gpu/* +p; file drivers/pci/of.c +p; drivers/spmi/* +p; file drivers/pci/of.c +p; drivers/mfd/* +p; file drivers/pci/of.c +p; drivers/regulator/* +p; file drivers/pci/of.c +p; drivers/usb/core/hub.c +p
[ 3.767252] kirin-pcie f4000000.pcie: host bridge /soc/pcie@f4000000 ranges:
[ 3.778028] kirin-pcie f4000000.pcie: No bus range found for /soc/pcie@f4000000, using [bus 00-ff]
[ 3.792466] kirin-pcie f4000000.pcie: Parsing ranges property...
[ 3.801919] kirin-pcie f4000000.pcie: MEM 0x00f6000000..0x00f7ffffff -> 0x0000000000
[ 3.813680] kirin-pcie f4000000.pcie: invalid resource
[ 3.822189] kirin-pcie f4000000.pcie: iATU unroll: enabled
[ 3.831159] kirin-pcie f4000000.pcie: Detected iATU regions: 8 outbound, 8 inbound
[ 3.943155] kirin-pcie f4000000.pcie: Link up
[ 3.956821] (null): pci_set_bus_of_node: of_node: /soc/pcie@f4000000
[ 3.979143] kirin-pcie f4000000.pcie: PCI host bridge to bus 0000:00
[ 3.989441] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 3.998050] pci_bus 0000:00: root bus resource [mem 0xf6000000-0xf7ffffff] (bus address [0x00000000-0x01ffffff])
[ 4.011965] pci 0000:00:00.0: [19e5:3670] type 01 class 0x060400
[ 4.021177] pci 0000:00:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
[ 4.031041] pci 0000:00:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000
[ 4.041362] pci 0000:00:00.0: supports D1 D2
[ 4.049191] pci 0000:00:00.0: PME# supported from D0 D1 D2 D3hot
[ 4.059554] pci_bus 0000:01: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
[ 4.071133] pci 0000:01:00.0: [10b5:8606] type 01 class 0x060400
[ 4.080831] pci 0000:01:00.0: reg 0x10: [mem 0xf6000000-0xf601ffff]
[ 4.103511] pci 0000:01:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0
[ 4.115403] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[ 4.139816] pci 0000:01:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.157297] pci_bus 0000:02: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.172380] pci 0000:02:01.0: [10b5:8606] type 01 class 0x060400
[ 4.182279] pci 0000:02:01.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.197047] pci 0000:02:01.0: PME# supported from D0 D3hot D3cold
[ 4.207583] pci 0000:02:04.0: [10b5:8606] type 01 class 0x060400
[ 4.217659] pci 0000:02:04.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.234551] pci 0000:02:04.0: PME# supported from D0 D3hot D3cold
[ 4.254284] pci 0000:02:05.0: [10b5:8606] type 01 class 0x060400
[ 4.267668] pci 0000:02:05.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.282530] pci 0000:02:05.0: PME# supported from D0 D3hot D3cold
[ 4.295077] pci 0000:02:07.0: [10b5:8606] type 01 class 0x060400
[ 4.306032] pci 0000:02:07.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.320927] pci 0000:02:07.0: PME# supported from D0 D3hot D3cold
[ 4.333414] pci 0000:02:09.0: [10b5:8606] type 01 class 0x060400
[ 4.340439] pci 0000:02:09.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0
[ 4.350084] pci 0000:02:09.0: PME# supported from D0 D3hot D3cold
[ 4.358150] pci 0000:02:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.366379] pci 0000:02:04.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.374515] pci 0000:02:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.382682] pci 0000:02:07.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.390834] pci 0000:02:09.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.399079] pci_bus 0000:03: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@1,0
[ 4.409309] pci 0000:03:00.0: [144d:a809] type 00 class 0x010802
[ 4.415564] pci 0000:03:00.0: reg 0x10: [mem 0xf6000000-0xf6003fff 64bit]
[ 4.422769] pci 0000:03:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@1,0
[ 4.433782] pci 0000:03:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[ 4.449954] pci_bus 0000:03: busn_res: [bus 03-ff] end is updated to 03
[ 4.456836] pci_bus 0000:04: pci_set_bus_of_node: of_node: (null)
[ 4.457918] pci_bus 0000:04: busn_res: [bus 04-ff] end is updated to 04
[ 4.478895] pci_bus 0000:05: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@5,0
[ 4.491772] pci_bus 0000:05: busn_res: [bus 05-ff] end is updated to 05
[ 4.503438] pci_bus 0000:06: pci_set_bus_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@7,0
[ 4.529140] pci 0000:06:00.0: [10ec:8168] type 00 class 0x020000
[ 4.535374] pci 0000:06:00.0: reg 0x10: [io 0x0000-0x00ff]
[ 4.541229] pci 0000:06:00.0: reg 0x18: [mem 0xf7000000-0xf7000fff 64bit]
[ 4.548194] pci 0000:06:00.0: reg 0x20: [mem 0xf7200000-0xf7203fff 64bit pref]
[ 4.561063] pci 0000:06:00.0: pci_set_of_node: of_node: /soc/pcie@f4000000/pcie@0,0/pcie@0,0/pcie@7,0
[ 4.582075] pci 0000:06:00.0: supports D1 D2
[ 4.586357] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 4.594727] pci_bus 0000:06: busn_res: [bus 06-ff] end is updated to 06
[ 4.601538] pci_bus 0000:07: pci_set_bus_of_node: of_node: (null)
[ 4.608473] pci_bus 0000:07: busn_res: [bus 07-ff] end is updated to 07
[ 4.615124] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 07
[ 4.621810] pci 0000:00:00.0: BAR 0: assigned [mem 0xf6000000-0xf6ffffff]
[ 4.628606] pci 0000:00:00.0: BAR 14: assigned [mem 0xf7000000-0xf72fffff]
[ 4.628610] pci 0000:00:00.0: BAR 15: assigned [mem 0xf7300000-0xf73fffff pref]
[ 4.642813] pci 0000:00:00.0: BAR 13: no space for [io size 0x1000]
[ 4.649174] pci 0000:00:00.0: BAR 13: failed to assign [io size 0x1000]
[ 4.661518] pci 0000:01:00.0: BAR 14: assigned [mem 0xf7000000-0xf71fffff]
[ 4.669074] pci 0000:01:00.0: BAR 15: assigned [mem 0xf7300000-0xf73fffff 64bit pref]
[ 4.677066] pci 0000:01:00.0: BAR 0: assigned [mem 0xf7200000-0xf721ffff]
[ 4.683891] pci 0000:01:00.0: BAR 13: no space for [io size 0x1000]
[ 4.690252] pci 0000:01:00.0: BAR 13: failed to assign [io size 0x1000]
[ 4.690266] pci 0000:02:01.0: BAR 14: assigned [mem 0xf7000000-0xf70fffff]
[ 4.690270] pci 0000:02:07.0: BAR 14: assigned [mem 0xf7100000-0xf71fffff]
[ 4.710728] pci 0000:02:07.0: BAR 15: assigned [mem 0xf7300000-0xf73fffff 64bit pref]
[ 4.727780] pci 0000:02:07.0: BAR 13: no space for [io size 0x1000]
[ 4.727783] pci 0000:02:07.0: BAR 13: failed to assign [io size 0x1000]
[ 4.727790] pci 0000:03:00.0: BAR 0: assigned [mem 0xf7000000-0xf7003fff 64bit]
[ 4.727904] pci 0000:02:01.0: PCI bridge to [bus 03]
[ 4.753165] pci 0000:02:01.0: bridge window [mem 0xf7000000-0xf70fffff]
[ 4.769738] pci 0000:02:04.0: PCI bridge to [bus 04]
[ 4.774843] pci 0000:02:05.0: PCI bridge to [bus 05]
[ 4.779959] pci 0000:06:00.0: BAR 4: assigned [mem 0xf7300000-0xf7303fff 64bit pref]
[ 4.787839] pci 0000:06:00.0: BAR 2: assigned [mem 0xf7100000-0xf7100fff 64bit]
[ 4.795273] pci 0000:06:00.0: BAR 0: no space for [io size 0x0100]
[ 4.801543] pci 0000:06:00.0: BAR 0: failed to assign [io size 0x0100]
[ 4.808159] pci 0000:02:07.0: PCI bridge to [bus 06]
[ 4.813166] pci 0000:02:07.0: bridge window [mem 0xf7100000-0xf71fffff]
[ 4.819981] pci 0000:02:07.0: bridge window [mem 0xf7300000-0xf73fffff 64bit pref]
[ 4.827782] pci 0000:02:09.0: PCI bridge to [bus 07]
[ 4.832871] pci 0000:01:00.0: PCI bridge to [bus 02-07]
[ 4.838138] pci 0000:01:00.0: bridge window [mem 0xf7000000-0xf71fffff]
[ 4.844952] pci 0000:01:00.0: bridge window [mem 0xf7300000-0xf73fffff 64bit pref]
[ 4.852751] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[ 4.857980] pci 0000:00:00.0: bridge window [mem 0xf7000000-0xf72fffff]
[ 4.864770] pci 0000:00:00.0: bridge window [mem 0xf7300000-0xf73fffff pref]
[ 4.881547] pcieport 0000:00:00.0: PME: Signaling with IRQ 58
[ 4.888905] pcieport 0000:00:00.0: AER: enabled with IRQ 58
[ 4.895013] pcieport 0000:01:00.0: enabling device (0000 -> 0002)
[ 4.903260] pcieport 0000:02:01.0: enabling device (0000 -> 0002)
[ 4.914761] pcieport 0000:02:07.0: enabling device (0000 -> 0002)
[ 4.928984] nvme nvme0: pci function 0000:03:00.0
Thanks,
Mauro
next prev parent reply other threads:[~2021-08-11 7:11 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
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 [this message]
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=20210811091115.03b36daa@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.