From: "Heiko Stübner" <heiko@sntech.de>
To: Sonny Rao <sonnyrao@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, 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: Mon, 24 Nov 2014 01:07:38 +0100 [thread overview]
Message-ID: <2905614.GvjeQFvyvc@diego> (raw)
In-Reply-To: <1416381319-31117-1-git-send-email-sonnyrao@chromium.org>
Hi Sonny,
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>
> ---
> drivers/clk/rockchip/clk-rk3288.c | 3 ++-
> include/dt-bindings/clock/rk3288-cru.h | 1 +
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
[...]
> diff --git a/include/dt-bindings/clock/rk3288-cru.h
> b/include/dt-bindings/clock/rk3288-cru.h index 100a08c..4acc730 100644
> --- a/include/dt-bindings/clock/rk3288-cru.h
> +++ b/include/dt-bindings/clock/rk3288-cru.h
> @@ -71,6 +71,7 @@
> #define SCLK_HDMI_CEC 110
> #define SCLK_HEVC_CABAC 111
> #define SCLK_HEVC_CORE 112
> +#define SCLK_I2S0_OUT 113
>
> #define DCLK_VOP0 190
> #define DCLK_VOP1 191
just to get branches right, do you plan on sending a patch using this new
clock-id in a devicetree file in time for 3.19 (i.e. during the next week).
If you plan on doing this, we'll need a 2-patch series like Alexandru did for
the mmc phases [because we would need a shared branch between clk and dts
branches]. If not the patch can stay as it is.
Thanks
Heiko
next prev parent reply other threads:[~2014-11-24 0:24 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 [this message]
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
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=2905614.GvjeQFvyvc@diego \
--to=heiko@sntech.de \
--cc=dianders@chromium.org \
--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 \
--cc=sonnyrao@chromium.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).