* [PATCH] ARM: dts: keystone: Fix control register range for clktsip
@ 2014-03-18 13:23 ` Ivan Khoronzhuk
0 siblings, 0 replies; 6+ messages in thread
From: Ivan Khoronzhuk @ 2014-03-18 13:23 UTC (permalink / raw)
To: santosh.shilimkar
Cc: robh+dt, pawel.moll, mark.rutland, ijc+devicetree, galak, linux,
devicetree, linux-arm-kernel, linux-kernel, grygorii.strashko,
Ivan Khoronzhuk
The control register range for clktsio interferes with clkaemifspi clock.
And it causes issues for NAND/AEMIF. So fix it.
Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
---
Only comment is corrected.
arch/arm/boot/dts/k2hk-clocks.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/k2hk-clocks.dtsi b/arch/arm/boot/dts/k2hk-clocks.dtsi
index a71aa29..8855b1f 100644
--- a/arch/arm/boot/dts/k2hk-clocks.dtsi
+++ b/arch/arm/boot/dts/k2hk-clocks.dtsi
@@ -59,7 +59,7 @@ clocks {
compatible = "ti,keystone,psc-clock";
clocks = <&chipclk16>;
clock-output-names = "tsip";
- reg = <0x0235000c 0xb00>, <0x02350000 0x400>;
+ reg = <0x02350000 0xb00>, <0x02350000 0x400>;
reg-names = "control", "domain";
domain-id = <0>;
};
--
1.8.3.2
^ permalink raw reply related [flat|nested] 6+ messages in thread* [PATCH] ARM: dts: keystone: Fix control register range for clktsip
@ 2014-03-18 13:23 ` Ivan Khoronzhuk
0 siblings, 0 replies; 6+ messages in thread
From: Ivan Khoronzhuk @ 2014-03-18 13:23 UTC (permalink / raw)
To: santosh.shilimkar
Cc: mark.rutland, devicetree, grygorii.strashko, linux, pawel.moll,
ijc+devicetree, linux-kernel, robh+dt, galak, Ivan Khoronzhuk,
linux-arm-kernel
The control register range for clktsio interferes with clkaemifspi clock.
And it causes issues for NAND/AEMIF. So fix it.
Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
---
Only comment is corrected.
arch/arm/boot/dts/k2hk-clocks.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/k2hk-clocks.dtsi b/arch/arm/boot/dts/k2hk-clocks.dtsi
index a71aa29..8855b1f 100644
--- a/arch/arm/boot/dts/k2hk-clocks.dtsi
+++ b/arch/arm/boot/dts/k2hk-clocks.dtsi
@@ -59,7 +59,7 @@ clocks {
compatible = "ti,keystone,psc-clock";
clocks = <&chipclk16>;
clock-output-names = "tsip";
- reg = <0x0235000c 0xb00>, <0x02350000 0x400>;
+ reg = <0x02350000 0xb00>, <0x02350000 0x400>;
reg-names = "control", "domain";
domain-id = <0>;
};
--
1.8.3.2
^ permalink raw reply related [flat|nested] 6+ messages in thread* [PATCH] ARM: dts: keystone: Fix control register range for clktsip
2014-03-18 13:23 ` Ivan Khoronzhuk
(?)
@ 2014-03-18 16:09 ` Santosh Shilimkar
-1 siblings, 0 replies; 6+ messages in thread
From: Santosh Shilimkar @ 2014-03-18 16:09 UTC (permalink / raw)
To: linux-arm-kernel
On Tuesday 18 March 2014 09:23 AM, Ivan Khoronzhuk wrote:
> The control register range for clktsio interferes with clkaemifspi clock.
> And it causes issues for NAND/AEMIF. So fix it.
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> ---
>
> Only comment is corrected.
>
Thanks .. Applying for 3.15-fixes
> arch/arm/boot/dts/k2hk-clocks.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/k2hk-clocks.dtsi b/arch/arm/boot/dts/k2hk-clocks.dtsi
> index a71aa29..8855b1f 100644
> --- a/arch/arm/boot/dts/k2hk-clocks.dtsi
> +++ b/arch/arm/boot/dts/k2hk-clocks.dtsi
> @@ -59,7 +59,7 @@ clocks {
> compatible = "ti,keystone,psc-clock";
> clocks = <&chipclk16>;
> clock-output-names = "tsip";
> - reg = <0x0235000c 0xb00>, <0x02350000 0x400>;
> + reg = <0x02350000 0xb00>, <0x02350000 0x400>;
> reg-names = "control", "domain";
> domain-id = <0>;
> };
>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH] ARM: dts: keystone: Fix control register range for clktsip
@ 2014-03-18 16:09 ` Santosh Shilimkar
0 siblings, 0 replies; 6+ messages in thread
From: Santosh Shilimkar @ 2014-03-18 16:09 UTC (permalink / raw)
To: Ivan Khoronzhuk
Cc: robh+dt, pawel.moll, mark.rutland, ijc+devicetree, galak, linux,
devicetree, linux-arm-kernel, linux-kernel, grygorii.strashko
On Tuesday 18 March 2014 09:23 AM, Ivan Khoronzhuk wrote:
> The control register range for clktsio interferes with clkaemifspi clock.
> And it causes issues for NAND/AEMIF. So fix it.
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> ---
>
> Only comment is corrected.
>
Thanks .. Applying for 3.15-fixes
> arch/arm/boot/dts/k2hk-clocks.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/k2hk-clocks.dtsi b/arch/arm/boot/dts/k2hk-clocks.dtsi
> index a71aa29..8855b1f 100644
> --- a/arch/arm/boot/dts/k2hk-clocks.dtsi
> +++ b/arch/arm/boot/dts/k2hk-clocks.dtsi
> @@ -59,7 +59,7 @@ clocks {
> compatible = "ti,keystone,psc-clock";
> clocks = <&chipclk16>;
> clock-output-names = "tsip";
> - reg = <0x0235000c 0xb00>, <0x02350000 0x400>;
> + reg = <0x02350000 0xb00>, <0x02350000 0x400>;
> reg-names = "control", "domain";
> domain-id = <0>;
> };
>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH] ARM: dts: keystone: Fix control register range for clktsip
@ 2014-03-18 16:09 ` Santosh Shilimkar
0 siblings, 0 replies; 6+ messages in thread
From: Santosh Shilimkar @ 2014-03-18 16:09 UTC (permalink / raw)
To: Ivan Khoronzhuk
Cc: robh+dt, pawel.moll, mark.rutland, ijc+devicetree, galak, linux,
devicetree, linux-arm-kernel, linux-kernel, grygorii.strashko
On Tuesday 18 March 2014 09:23 AM, Ivan Khoronzhuk wrote:
> The control register range for clktsio interferes with clkaemifspi clock.
> And it causes issues for NAND/AEMIF. So fix it.
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> ---
>
> Only comment is corrected.
>
Thanks .. Applying for 3.15-fixes
> arch/arm/boot/dts/k2hk-clocks.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/k2hk-clocks.dtsi b/arch/arm/boot/dts/k2hk-clocks.dtsi
> index a71aa29..8855b1f 100644
> --- a/arch/arm/boot/dts/k2hk-clocks.dtsi
> +++ b/arch/arm/boot/dts/k2hk-clocks.dtsi
> @@ -59,7 +59,7 @@ clocks {
> compatible = "ti,keystone,psc-clock";
> clocks = <&chipclk16>;
> clock-output-names = "tsip";
> - reg = <0x0235000c 0xb00>, <0x02350000 0x400>;
> + reg = <0x02350000 0xb00>, <0x02350000 0x400>;
> reg-names = "control", "domain";
> domain-id = <0>;
> };
>
^ permalink raw reply [flat|nested] 6+ messages in thread