This is a note to let you know that I've just added the patch titled
ARM: dts: omap4/5: Use l3_ick for the gpmc node
to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
arm-dts-omap4-5-use-l3_ick-for-the-gpmc-node.patch
and it can be found in the queue-3.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 7b8b6af169a069454936053631d151a50af7b69a Mon Sep 17 00:00:00 2001
From: Florian Vaussard <florian.vaussard@xxxxxxx>
Date: Wed, 26 Feb 2014 11:38:09 +0100
Subject: ARM: dts: omap4/5: Use l3_ick for the gpmc node
From: Florian Vaussard <florian.vaussard@xxxxxxx>
commit 7b8b6af169a069454936053631d151a50af7b69a upstream.
The GPMC clock is derived from l3_ick. The simplest solution is
to reference directly l3_ick to provide the GPMC fck in order to
get correct timings. The real management of the clock is left to
hwmod.
Signed-off-by: Florian Vaussard <florian.vaussard@xxxxxxx>
Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
arch/arm/boot/dts/omap4.dtsi | 2 ++
arch/arm/boot/dts/omap5.dtsi | 2 ++
2 files changed, 4 insertions(+)
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -275,6 +275,8 @@
gpmc,num-waitpins = <4>;
ti,hwmods = "gpmc";
ti,no-idle-on-init;
+ clocks = <&l3_div_ck>;
+ clock-names = "fck";
};
uart1: serial@4806a000 {
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -302,6 +302,8 @@
gpmc,num-cs = <8>;
gpmc,num-waitpins = <4>;
ti,hwmods = "gpmc";
+ clocks = <&l3_iclk_div>;
+ clock-names = "fck";
};
i2c1: i2c@48070000 {
Patches currently in stable-queue which might be from florian.vaussard@xxxxxxx are
queue-3.14/arm-dts-omap4-5-use-l3_ick-for-the-gpmc-node.patch
queue-3.14/clk-ti-omap4-5-dra7-remove-gpmc_fck-from-dummy-clocks.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html