From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, grygorii.strashko@ti.com
Subject: Re: [PATCH] ARM: dts: keystone: Fix control register range for clktsip
Date: Tue, 18 Mar 2014 12:09:35 -0400 [thread overview]
Message-ID: <53286FBF.6050708@ti.com> (raw)
In-Reply-To: <1395148991-22538-1-git-send-email-ivan.khoronzhuk@ti.com>
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>;
> };
>
prev parent reply other threads:[~2014-03-18 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 13:23 [PATCH] ARM: dts: keystone: Fix control register range for clktsip Ivan Khoronzhuk
2014-03-18 16:09 ` Santosh Shilimkar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53286FBF.6050708@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).