From: Paul Cercueil <paul@crapouillou.net>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: ingenic/jz4740: Fix "pll half" divider not read/written properly
Date: Thu, 08 Aug 2019 15:18:07 +0200 [thread overview]
Message-ID: <1565270287.15950.0@crapouillou.net> (raw)
In-Reply-To: <20190808040822.430582186A@mail.kernel.org>
Le jeu. 8 août 2019 à 6:08, Stephen Boyd <sboyd@kernel.org> a écrit :
> Quoting Paul Cercueil (2019-08-07 16:28:10)
>>
>>
>> Le mer. 7 août 2019 à 23:33, Stephen Boyd <sboyd@kernel.org> a
>> écrit
>> :
>> > Quoting Paul Cercueil (2019-07-01 04:36:06)
>> >> The code was setting the bit 21 of the CPCCR register to use a
>> >> divider
>> >> of 2 for the "pll half" clock, and clearing the bit to use a
>> divider
>> >> of 1.
>> >>
>> >> This is the opposite of how this register field works: a
>> cleared bit
>> >> means that the /2 divider is used, and a set bit means that the
>> >> divider
>> >> is 1.
>> >>
>> >> Restore the correct behaviour using the newly introduced
>> .div_table
>> >> field.
>> >>
>> >> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> >> ---
>> >
>> > Applied to clk-next. Does this need a fixes tag?
>>
>> It depends on commit a9fa2893fcc6 ("clk: ingenic: Add support for
>> divider tables") which was sent without a fixes tag, so it'd be
>> a bit difficult. Probably not worth the trouble.
>>
>
> Does it need to go in as a fix for this -rc series then? Or is it not
> causing issues for you so it's ok to wait until next merge window?
It can wait for the next merge window, yes.
-Paul
prev parent reply other threads:[~2019-08-08 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 11:36 [PATCH] clk: ingenic/jz4740: Fix "pll half" divider not read/written properly Paul Cercueil
2019-08-07 21:33 ` Stephen Boyd
2019-08-07 23:28 ` Paul Cercueil
2019-08-08 4:08 ` Stephen Boyd
2019-08-08 13:18 ` Paul Cercueil [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=1565270287.15950.0@crapouillou.net \
--to=paul@crapouillou.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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