From: Sonny Rao <sonnyrao@chromium.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-rockchip@lists.infradead.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Douglas Anderson <dianders@chromium.org>,
Mike Turquette <mturquette@linaro.org>,
Mark yao <mark.yao@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH] clk: rockchip: rk3288 export i2s0_clkout for use in DT
Date: Wed, 26 Nov 2014 19:47:10 -0800 [thread overview]
Message-ID: <CAPz6YkXOS08hv7x+DM3roTuZYMbh9n4=kpTrH8NGYUffczQwLA@mail.gmail.com> (raw)
In-Reply-To: <3863623.tcGxuFQcZa@diego>
On Wed, Nov 26, 2014 at 3:32 PM, Heiko Stübner <heiko@sntech.de> wrote:
> Am Dienstag, 18. November 2014, 23:15:19 schrieb Sonny Rao:
>> This exposes the clock that comes out of the i2s block which generally
>> goes to the audio codec.
>>
>> Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
>
> applied to my clk branch after removing the CLK_SET_RATE_PARENT
Hi, sorry for the delay, and thanks for fixing it. I think when I
applied the patch to next-20141118 that had a CLK_SET_RATE_PARENT in
it from this patch:
commit fc69ed70c16a31d6a77ec47a30a9fe941f763f1e
Author: Jianqun <jay.xu@rock-chips.com>
Date: Tue Sep 30 11:12:04 2014 +0800
clk: rockchip: rk3288: i2s_frac adds flag to set parent's rate
I agree that is is not necessary and maybe not desirable. Thanks again!
> Heiko
next prev parent reply other threads:[~2014-11-27 3:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 7:15 [PATCH] clk: rockchip: rk3288 export i2s0_clkout for use in DT Sonny Rao
2014-11-24 0:07 ` Heiko Stübner
2014-11-24 2:08 ` Sonny Rao
2014-11-26 18:09 ` Heiko Stübner
2014-11-26 23:05 ` Doug Anderson
2014-11-26 23:15 ` Heiko Stübner
2014-11-26 23:32 ` Heiko Stübner
2014-11-27 3:47 ` Sonny Rao [this message]
2014-11-27 8:52 ` Heiko Stübner
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='CAPz6YkXOS08hv7x+DM3roTuZYMbh9n4=kpTrH8NGYUffczQwLA@mail.gmail.com' \
--to=sonnyrao@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.com \
--cc=mturquette@linaro.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).