From: Heiko Stuebner <heiko@sntech.de>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-rockchip@lists.infradead.org, xf@rock-chips.com,
zhangqing@rock-chips.com
Subject: Re: [PATCH 1/4] clk: rockchip: fix cpuclk mux bit of big cpu-cluster
Date: Wed, 20 Jan 2016 23:25:57 +0100 [thread overview]
Message-ID: <2048998.GeQnePRN87@phil> (raw)
In-Reply-To: <56A004E3.5000309@codeaurora.org>
Am Mittwoch, 20. Januar 2016, 14:06:27 schrieb Stephen Boyd:
> On 01/20/2016 01:49 PM, Heiko Stuebner wrote:
> > Both clusters have their mux bit in bit 7 of their respective register.
> > For whatever reason the big cluster currently lists bit 15 which is
> > definitly wrong.
> >
> > Fixes: 3536c97a52db ("clk: rockchip: add rk3368 clock controller")
> > Reported-by: Zhang Qing <zhangqing@rock-chips.com>
> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > ---
> > I plan to include them into my clk-fixes branch, so posted for reference
> > and possible objections ;-)
>
> None of these patches are fixes to regressions introduced in the merge
> window for v4.5, so we wouldn't be considering them for clk-fixes. We
> can certainly queue them up in clk-next for v4.6 and let stable process
> funnel them to the right stable trees though.
ok, I'll move them over to that part then :-)
next prev parent reply other threads:[~2016-01-20 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 21:49 [PATCH 1/4] clk: rockchip: fix cpuclk mux bit of big cpu-cluster Heiko Stuebner
2016-01-20 21:49 ` [PATCH 2/4] clk: rockchip: fix rk3368 cpuclk core dividers Heiko Stuebner
2016-01-21 9:42 ` zhangqing
2016-01-20 21:49 ` [PATCH 3/4] clk: rockchip: rk3368: fix parents of video encoder/decoder Heiko Stuebner
2016-01-21 9:43 ` zhangqing
2016-01-20 21:49 ` [PATCH 4/4] clk: rockchip: rk3368: fix hdmi_cec gate-register Heiko Stuebner
2016-01-21 9:44 ` zhangqing
2016-01-20 22:06 ` [PATCH 1/4] clk: rockchip: fix cpuclk mux bit of big cpu-cluster Stephen Boyd
2016-01-20 22:25 ` Heiko Stuebner [this message]
2016-01-21 9:44 ` zhangqing
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=2048998.GeQnePRN87@phil \
--to=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=xf@rock-chips.com \
--cc=zhangqing@rock-chips.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).