summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJohan Hovold <johan@kernel.org>2016-08-15 09:10:45 -0700
committerTony Lindgren <tony@atomide.com>2016-08-15 09:10:45 -0700
commit5e0568dfbfb8c13cdb69c9fd06d600593ad4b430 (patch)
tree7c8a8df655a311b31d50c3e9d190bfeb07116484
parent42647f947210cb9fd8a7737c0fd2a60002a81188 (diff)
downloadtalos-op-linux-5e0568dfbfb8c13cdb69c9fd06d600593ad4b430.tar.gz
talos-op-linux-5e0568dfbfb8c13cdb69c9fd06d600593ad4b430.zip
ARM: dts: overo: fix gpmc nand cs0 range
The gpmc ranges property for NAND at CS0 has been broken since it was first added. This currently prevents the nand gpmc child node from being probed: omap-gpmc 6e000000.gpmc: /ocp/gpmc@6e000000/nand@0,0 has malformed 'reg' property and consequently the NAND device from being registered. Fixes: 98ce6007efb4 ("ARM: dts: overo: Support PoP NAND") Cc: stable <stable@vger.kernel.org> # 4.3 Signed-off-by: Johan Hovold <johan@kernel.org> Signed-off-by: Tony Lindgren <tony@atomide.com>
-rw-r--r--arch/arm/boot/dts/omap3-overo-base.dtsi2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/boot/dts/omap3-overo-base.dtsi b/arch/arm/boot/dts/omap3-overo-base.dtsi
index de256fa8da48..b15c435439fb 100644
--- a/arch/arm/boot/dts/omap3-overo-base.dtsi
+++ b/arch/arm/boot/dts/omap3-overo-base.dtsi
@@ -223,7 +223,7 @@
};
&gpmc {
- ranges = <0 0 0x00000000 0x20000000>;
+ ranges = <0 0 0x30000000 0x1000000>; /* CS0 */
nand@0,0 {
compatible = "ti,omap2-nand";
OpenPOWER on IntegriCloud