From: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Stephen Boyd <sboyd@kernel.org>,
mturquette@baylibre.com, linux-mips@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: ingenic-tcu: Properly enable registers before accessing timers
Date: Fri, 10 Jun 2022 17:24:38 +0100 [thread overview]
Message-ID: <SRc6K3M4AqicGZJ2iAONg1d6NAikTPNJ@localhost> (raw)
In-Reply-To: <TDQ9DR.SDDTZMEA0H7F3@crapouillou.net>
Paul Cercueil <paul@crapouillou.net> writes:
> Le ven., juin 10 2022 at 16:43:27 +0100, Aidan MacDonald
> <aidanmacdonald.0x0@gmail.com> a écrit :
>> Stephen Boyd <sboyd@kernel.org> writes:
>>
>>> Quoting Aidan MacDonald (2022-06-03 06:47:05)
>>>> Access to registers is guarded by ingenic_tcu_{enable,disable}_regs()
>>>> so the stop bit can be cleared before accessing a timer channel, but
>>>> those functions did not clear the stop bit on SoCs with a global TCU
>>>> clock gate.
>>>> Testing on the X1000 has revealed that the stop bits must be cleared
>>>> _and_ the global TCU clock must be ungated to access timer registers.
>>>> Programming manuals for the X1000, JZ4740, and JZ4725B specify this
>>>> behavior. If the stop bit isn't cleared, then writes to registers do
>>>> not take effect, which can leave clocks with no defined parent when
>>>> registered and leave clock tree state out of sync with the hardware,
>>>> triggering bugs in downstream drivers relying on TCU clocks.
>>>> Fixing this is easy: have ingenic_tcu_{enable,disable}_regs() always
>>>> clear the stop bit, regardless of the presence of a global TCU gate.
>>>> Signed-off-by: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
>>>> ---
>>> Any Fixes: tag?
>> Probably 4f89e4b8f121 ("clk: ingenic: Add driver for the TCU clocks")
>> but I don't have docs or hardware to confirm the bug affects the jz4770,
>> which is the only other SoC affected by the change.
>> I think what caused my problem was my bootloader stopping all the timer
>> channels. The stop bits are supposed to be zeroed at reset, so I'd guess
>> the jz4770 relied on that and only worked by accident.
>
> I'll test it on JZ4770 this weekend.
>
>> I'll send a v2 along shortly. Is it worth CC'ing stable as well?
>
> If the bug is in jz-5.18 or earlier, yes.
>
> Cheers,
> -Paul
Thanks. Guess I'll wait for your test results, though I don't expect any
problems.
next prev parent reply other threads:[~2022-06-10 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 13:47 [PATCH] clk: ingenic-tcu: Properly enable registers before accessing timers Aidan MacDonald
2022-06-09 22:41 ` Stephen Boyd
2022-06-10 15:43 ` Aidan MacDonald
2022-06-10 15:44 ` Paul Cercueil
2022-06-10 16:24 ` Aidan MacDonald [this message]
2022-06-13 9:02 ` Paul Cercueil
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=SRc6K3M4AqicGZJ2iAONg1d6NAikTPNJ@localhost \
--to=aidanmacdonald.0x0@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=paul@crapouillou.net \
--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