ARM: tegra: Add back gpio-ranges properties

The properties have been commented out to prevent a regression a while
ago. The first regression should be resolved by commit 44af7927316e
("spi: Map SPI OF client IRQ at probe time").

The second regression is probably addressed by commit 494fd7b7ad10
("PM / core: fix deferred probe breaking suspend resume order") and/or
maybe others. Readd the gpio-ranges properties to see whether
regressions still get reported.

This reverts commit 4f1d841475e1 ("ARM: tegra: Comment out gpio-ranges
properties").

Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
Tested-by: Dmitry Osipenko <digetx@gmail.com>
[treding@nvidia.com: drop redundant gpio-ranges from Ouya DTS file]
Signed-off-by: Thierry Reding <treding@nvidia.com>
This commit is contained in:
Stefan Agner 2018-07-26 17:40:25 +02:00 committed by Thierry Reding
parent 919be27fd0
commit 9ca9a608a7
5 changed files with 0 additions and 12 deletions

View File

@ -261,9 +261,7 @@
gpio-controller;
#interrupt-cells = <2>;
interrupt-controller;
/*
gpio-ranges = <&pinmux 0 0 246>;
*/
};
vde@6001a000 {

View File

@ -308,9 +308,7 @@
gpio-controller;
#interrupt-cells = <2>;
interrupt-controller;
/*
gpio-ranges = <&pinmux 0 0 251>;
*/
};
apbdma: dma@60020000 {

View File

@ -328,9 +328,7 @@
gpio-controller;
#interrupt-cells = <2>;
interrupt-controller;
/*
gpio-ranges = <&pinmux 0 0 224>;
*/
};
vde@6001a000 {

View File

@ -68,10 +68,6 @@
};
};
gpio: gpio@6000d000 {
gpio-ranges = <&pinmux 0 0 248>;
};
pinmux@70000868 {
pinctrl-names = "default";
pinctrl-0 = <&state_default>;

View File

@ -507,9 +507,7 @@
gpio-controller;
#interrupt-cells = <2>;
interrupt-controller;
/*
gpio-ranges = <&pinmux 0 0 248>;
*/
};
vde@6001a000 {