summaryrefslogtreecommitdiff
path: root/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
diff options
context:
space:
mode:
authorChen-Yu Tsai <wens@csie.org>2021-01-22 00:23:20 +0800
committerHeiko Stuebner <heiko@sntech.de>2021-01-25 23:58:12 +0100
commit3503376d6cc385b6266f93c24ead9a33d8dfe8cb (patch)
treebf1a4062346133c93fb5d1a461118e9c0ee2eb03 /arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
parentd00e6e22e8b9f8d3b8308706f57ae82119289792 (diff)
arm64: dts: rockchip: Move ep-gpios property to nanopc-t4 from nanopi4
Only the NanoPC T4 hs the PCIe reset pin routed to the SoC. For the NanoPi M4 family, no such signal is routed to the expansion header on the base board. As the schematics for the expansion board were not released, it is unclear how this is handled, but the likely answer is that the signal is always pulled high. Move the ep-gpios property from the common nanopi4.dtsi file to the board level nanopc-t4.dts file. This makes the nanopi-m4 lack ep-gpios, matching the board design. A companion patch "PCI: rockchip: make ep_gpio optional" for the Linux driver is required, as the driver currently requires the property to be present. Fixes: e7a095908227 ("arm64: dts: rockchip: Add devicetree for NanoPC-T4") Reviewed-by: Robin Murphy <robin.murphy@arm.com> Signed-off-by: Chen-Yu Tsai <wens@csie.org> Link: https://lore.kernel.org/r/20210121162321.4538-4-wens@kernel.org Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Diffstat (limited to 'arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts')
-rw-r--r--arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts b/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
index e0d75617bb7e..452728b82e42 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
@@ -95,6 +95,7 @@
};
&pcie0 {
+ ep-gpios = <&gpio2 RK_PA4 GPIO_ACTIVE_HIGH>;
num-lanes = <4>;
vpcie3v3-supply = <&vcc3v3_sys>;
};