Re: [PATCH] ARM: moxart: move fixed rate clock child node to board level dts
On Thu, Jan 16, 2014 at 04:39:06PM +0100, Jonas Jensen wrote:
> When a skeleton "clocks { .. }" remain in .dtsi, the child node can
> be moved to .dts, "ref12" is then found by of_clk_get().
>
> Signed-off-by: Jonas Jensen
Applied to late/misc branch, will likely be included in 3.14-rc1
-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] ARM: moxart: move fixed rate clock child node to board level dts
On Thu, Jan 16, 2014 at 04:39:06PM +0100, Jonas Jensen wrote:
When a skeleton clocks { .. } remain in .dtsi, the child node can
be moved to .dts, ref12 is then found by of_clk_get().
Signed-off-by: Jonas Jensen jonas.jen...@gmail.com
Applied to late/misc branch, will likely be included in 3.14-rc1
-Olof
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] ARM: moxart: move fixed rate clock child node to board level dts
When a skeleton "clocks { .. }" remain in .dtsi, the child node can
be moved to .dts, "ref12" is then found by of_clk_get().
Signed-off-by: Jonas Jensen
---
Notes:
Applies to next-20140116
arch/arm/boot/dts/moxart-uc7112lx.dts | 8
arch/arm/boot/dts/moxart.dtsi | 6 --
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/moxart-uc7112lx.dts
b/arch/arm/boot/dts/moxart-uc7112lx.dts
index 90749d5..10d088d 100644
--- a/arch/arm/boot/dts/moxart-uc7112lx.dts
+++ b/arch/arm/boot/dts/moxart-uc7112lx.dts
@@ -17,6 +17,14 @@
reg = <0x0 0x200>;
};
+ clocks {
+ ref12: ref12M {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <1200>;
+ };
+ };
+
flash@8000,0 {
compatible = "numonyx,js28f128", "cfi-flash";
reg = <0x8000 0x100>;
diff --git a/arch/arm/boot/dts/moxart.dtsi b/arch/arm/boot/dts/moxart.dtsi
index da1d8ef..1fd27ed 100644
--- a/arch/arm/boot/dts/moxart.dtsi
+++ b/arch/arm/boot/dts/moxart.dtsi
@@ -26,12 +26,6 @@
clocks {
#address-cells = <1>;
#size-cells = <0>;
-
- ref12: ref12M {
- compatible = "fixed-clock";
- #clock-cells = <0>;
- clock-frequency = <1200>;
- };
};
soc {
--
1.8.2.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] ARM: moxart: move fixed rate clock child node to board level dts
When a skeleton clocks { .. } remain in .dtsi, the child node can
be moved to .dts, ref12 is then found by of_clk_get().
Signed-off-by: Jonas Jensen jonas.jen...@gmail.com
---
Notes:
Applies to next-20140116
arch/arm/boot/dts/moxart-uc7112lx.dts | 8
arch/arm/boot/dts/moxart.dtsi | 6 --
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/moxart-uc7112lx.dts
b/arch/arm/boot/dts/moxart-uc7112lx.dts
index 90749d5..10d088d 100644
--- a/arch/arm/boot/dts/moxart-uc7112lx.dts
+++ b/arch/arm/boot/dts/moxart-uc7112lx.dts
@@ -17,6 +17,14 @@
reg = 0x0 0x200;
};
+ clocks {
+ ref12: ref12M {
+ compatible = fixed-clock;
+ #clock-cells = 0;
+ clock-frequency = 1200;
+ };
+ };
+
flash@8000,0 {
compatible = numonyx,js28f128, cfi-flash;
reg = 0x8000 0x100;
diff --git a/arch/arm/boot/dts/moxart.dtsi b/arch/arm/boot/dts/moxart.dtsi
index da1d8ef..1fd27ed 100644
--- a/arch/arm/boot/dts/moxart.dtsi
+++ b/arch/arm/boot/dts/moxart.dtsi
@@ -26,12 +26,6 @@
clocks {
#address-cells = 1;
#size-cells = 0;
-
- ref12: ref12M {
- compatible = fixed-clock;
- #clock-cells = 0;
- clock-frequency = 1200;
- };
};
soc {
--
1.8.2.1
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
