From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Benoit Cousson <bcousson@baylibre.com>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mike Turquette <mturquette@linaro.org>
Subject: Re: [PATCH] ARM: DTS: dra7xx-clocks: Correct mcasp2_ahclkx_mux bit-shift
Date: Fri, 18 Apr 2014 15:33:24 -0700 [thread overview]
Message-ID: <20140418223323.GJ21823@atomide.com> (raw)
In-Reply-To: <533C1A6E.4030100@ti.com>
* Tero Kristo <t-kristo@ti.com> [140402 07:14]:
> On 04/02/2014 04:46 PM, Peter Ujfalusi wrote:
> >The correct bit is 24 for AHCLKX.
> >
> >Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> Yes, thats a clear bug in the data.
>
> Acked-by: Tero Kristo <t-kristo@ti.com>
Applying into omap-for-v3.15/fixes thanks.
Tony
> > arch/arm/boot/dts/dra7xx-clocks.dtsi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/arch/arm/boot/dts/dra7xx-clocks.dtsi b/arch/arm/boot/dts/dra7xx-clocks.dtsi
> >index e96da9a898ad..cfb8fc753f50 100644
> >--- a/arch/arm/boot/dts/dra7xx-clocks.dtsi
> >+++ b/arch/arm/boot/dts/dra7xx-clocks.dtsi
> >@@ -1640,7 +1640,7 @@
> > #clock-cells = <0>;
> > compatible = "ti,mux-clock";
> > clocks = <&abe_24m_fclk>, <&abe_sys_clk_div>, <&func_24m_clk>, <&atlclkin3_ck>, <&atl_clkin2_ck>, <&atl_clkin1_ck>, <&atl_clkin0_ck>, <&sys_clkin2>, <&ref_clkin0_ck>, <&ref_clkin1_ck>, <&ref_clkin2_ck>, <&ref_clkin3_ck>, <&mlb_clk>, <&mlbp_clk>;
> >- ti,bit-shift = <28>;
> >+ ti,bit-shift = <24>;
> > reg = <0x1860>;
> > };
> >
> >
>
prev parent reply other threads:[~2014-04-18 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 13:46 [PATCH] ARM: DTS: dra7xx-clocks: Correct mcasp2_ahclkx_mux bit-shift Peter Ujfalusi
[not found] ` <1396446385-20258-1-git-send-email-peter.ujfalusi-l0cyMroinI0@public.gmane.org>
2014-04-02 14:10 ` Tero Kristo
2014-04-18 22:33 ` Tony Lindgren [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=20140418223323.GJ21823@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
/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).