Mirrors/u-boot
2
0
Fork 0
mirror of https://github.com/AsahiLinux/u-boot synced 2024-11-26 06:30:39 +00:00
Code Issues Projects Releases Packages Wiki Activity

sandbox: Update PCI nodes in dts files

Browse source 
The way the PCI nodes are written today causes a number of warnings if
we stop disabling some of the warnings we pass to DTC.  As these
warnings aren't disabled in current Linux Kernel builds, we should aim
to not disable them here either, so rewrite these slightly.  Update the
driver model doc as well.

Cc: Simon Glass <sjg@chromium.org>
Signed-off-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
Tom Rini 2020-02-11 12:41:23 -05:00 committed by Simon Glass
parent 8a770f9eb7
commit 42c64d1bc9
5 changed files with 18 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
arch/sandbox/dts/sandbox.dts
View file

@ -10,7 +10,7 @@
aliases {
i2c0 = &i2c_0;
pci0 = &pci;
pci0 = &pcic;
rtc0 = &rtc_0;
axi0 = &axi;
spi0 = &spi;
@ -52,9 +52,10 @@
pinctrl-0 = <&pinctrl_i2c0>;
};
pci: pci-controller {
pcic: pci@0 {
compatible = "sandbox,pci";
device_type = "pci";
bus-range = <0x00 0xff>;
#address-cells = <3>;
#size-cells = <2>;
ranges = <0x02000000 0 0x10000000 0x10000000 0 0x2000

2
arch/sandbox/dts/sandbox.dtsi
View file

@ -100,7 +100,7 @@
};
};
pci-controller {
pci@0 {
pci@1e,0 {
compatible = "sandbox,pmc";
reg = <0xf000 0 0 0 0>;

5
arch/sandbox/dts/sandbox64.dts
View file

@ -10,7 +10,7 @@
aliases {
i2c0 = &i2c_0;
pci0 = &pci;
pci0 = &pcic;
rtc0 = &rtc_0;
axi0 = &axi;
spi0 = &spi;
@ -47,9 +47,10 @@
pinctrl-0 = <&pinctrl_i2c0>;
};
pci: pci-controller {
pcic: pci@0 {
compatible = "sandbox,pci";
device_type = "pci";
bus-range = <0x00 0xff>;
#address-cells = <3>;
#size-cells = <2>;
ranges = <0x02000000 0 0x10000000 0 0x10000000 0 0x2000

9
arch/sandbox/dts/test.dts
View file

@ -463,9 +463,10 @@
compatible = "sandbox,pch";
};
pci0: pci-controller0 {
pci0: pci@0 {
compatible = "sandbox,pci";
device_type = "pci";
bus-range = <0x00 0xff>;
#address-cells = <3>;
#size-cells = <2>;
ranges = <0x02000000 0 0x10000000 0x10000000 0 0x2000000
@ -531,9 +532,10 @@
};
};
pci1: pci-controller1 {
pci1: pci@1 {
compatible = "sandbox,pci";
device_type = "pci";
bus-range = <0x00 0xff>;
#address-cells = <3>;
#size-cells = <2>;
ranges = <0x02000000 0 0x30000000 0x30000000 0 0x2000
@ -546,9 +548,10 @@
};
};
pci2: pci-controller2 {
pci2: pci@2 {
compatible = "sandbox,pci";
device_type = "pci";
bus-range = <0x00 0xff>;
#address-cells = <3>;
#size-cells = <2>;
ranges = <0x02000000 0 0x50000000 0x50000000 0 0x2000

10
doc/driver-model/pci-info.rst
View file

@ -12,10 +12,10 @@ Bus number 0 will need to be requested first, and the alias in the device
tree file will point to the correct device::
aliases {
pci0 = &pci;
pci0 = &pcic;
};
pci: pci-controller {
pcic: pci@0 {
compatible = "sandbox,pci";
...
};
@ -138,7 +138,7 @@ be scanned as a PCI device, causing confusion.
When this bus is scanned we will end up with something like this::
`- * pci-controller @ 05c660c8, 0
`- * pci@0 @ 05c660c8, 0
`- pci@1f,0 @ 05c661c8, 63488
`- emul@1f,0 @ 05c662c8
@ -152,7 +152,7 @@ host controller node for this functionality to work.
.. code-block:: none
pci1: pci-controller1 {
pci1: pci@1 {
compatible = "sandbox,pci";
...
sandbox,dev-info = <0x08 0x00 0x1234 0x5678
@ -166,6 +166,6 @@ fourth cells are PCI vendor ID and device ID respectively.
When this bus is scanned we will end up with something like this::
pci [ + ] pci_sandbo |-- pci-controller1
pci [ + ] pci_sandbo |-- pci1
pci_emul [ ] sandbox_sw | |-- sandbox_swap_case_emul
pci_emul [ ] sandbox_sw | `-- sandbox_swap_case_emul