From: Philipp Rossak <embed3d@gmail.com>
To: Chen-Yu Tsai <wens@csie.org>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] clk: sunxi-ng: a31: Fix CLK_OUT_* clock ops
Date: Sat, 17 Feb 2018 14:54:16 +0100 [thread overview]
Message-ID: <694c5137-0020-bb62-68c7-f9729c101462@gmail.com> (raw)
In-Reply-To: <20180217130504.8668-1-wens@csie.org>
On 17.02.2018 14:05, Chen-Yu Tsai wrote:
> When support for the A31/A31s CCU was first added, the clock ops for
> the CLK_OUT_* clocks was set to the wrong type. The clocks are MP-type,
> but the ops was set for div (M) clocks. This went unnoticed until now.
> This was because while they are different clocks, their data structures
> aligned in a way that ccu_div_ops would access the second ccu_div_internal
> and ccu_mux_internal structures, which were valid, if not incorrect.
>
> Furthermore, the use of these CLK_OUT_* was for feeding a precise 32.768
> kHz clock signal to the WiFi chip. This was achievable by using the parent
> with the same clock rate and no divider. So the incorrect divider setting
> did not affect this usage.
>
> Commit 946797aa3f08 ("clk: sunxi-ng: Support fixed post-dividers on MP
> style clocks") added a new field to the ccu_mp structure, which broke
> the aforementioned alignment. Now the system crashes as div_ops tries
> to look up a nonexistent table.
>
> Reported-by: Philipp Rossak <embed3d@gmail.com>
> Fixes: c6e6c96d8fa6 ("clk: sunxi-ng: Add A31/A31s clocks")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Tested-by: Philipp Rossak <embed3d@gmail.com>
> ---
>
> Philipp, can you give this a test and report if this fixes thing?
> I don't have any A31/A31s boards online to test this.
>
Thanks!
That fixes that bug!
Philipp
> ---
> drivers/clk/sunxi-ng/ccu-sun6i-a31.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/clk/sunxi-ng/ccu-sun6i-a31.c b/drivers/clk/sunxi-ng/ccu-sun6i-a31.c
> index 72b16ed1012b..3b97f60540ad 100644
> --- a/drivers/clk/sunxi-ng/ccu-sun6i-a31.c
> +++ b/drivers/clk/sunxi-ng/ccu-sun6i-a31.c
> @@ -762,7 +762,7 @@ static struct ccu_mp out_a_clk = {
> .features = CCU_FEATURE_FIXED_PREDIV,
> .hw.init = CLK_HW_INIT_PARENTS("out-a",
> clk_out_parents,
> - &ccu_div_ops,
> + &ccu_mp_ops,
> 0),
> },
> };
> @@ -783,7 +783,7 @@ static struct ccu_mp out_b_clk = {
> .features = CCU_FEATURE_FIXED_PREDIV,
> .hw.init = CLK_HW_INIT_PARENTS("out-b",
> clk_out_parents,
> - &ccu_div_ops,
> + &ccu_mp_ops,
> 0),
> },
> };
> @@ -804,7 +804,7 @@ static struct ccu_mp out_c_clk = {
> .features = CCU_FEATURE_FIXED_PREDIV,
> .hw.init = CLK_HW_INIT_PARENTS("out-c",
> clk_out_parents,
> - &ccu_div_ops,
> + &ccu_mp_ops,
> 0),
> },
> };
>
next prev parent reply other threads:[~2018-02-17 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 13:05 Chen-Yu Tsai
2018-02-17 13:54 ` Philipp Rossak [this message]
2018-02-20 3:17 ` Chen-Yu Tsai
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=694c5137-0020-bb62-68c7-f9729c101462@gmail.com \
--to=embed3d@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®