public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Samuel Holland <samuel@sholland.org>,
	Chen-Yu Tsai <wens@csie.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	linux-sunxi@lists.linux.dev,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Stephen Boyd <sboyd@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] clk: sunxi-ng: Convert early providers to platform drivers
Date: Wed, 28 Jun 2023 12:07:56 +0100	[thread overview]
Message-ID: <yw1xa5wj3kvn.fsf@mansr.com> (raw)
In-Reply-To: <maqh4yir66agto4lyulvrqrim7qnixwd246jusvvhsjlhhrmmw@gjbubqc2cv4o> (Maxime Ripard's message of "Wed, 28 Jun 2023 09:44:18 +0200")

Maxime Ripard <mripard@kernel.org> writes:

> On Mon, Jun 26, 2023 at 01:21:33PM +0100, Måns Rullgård wrote:
>> Samuel Holland <samuel@sholland.org> writes:
>> 
>> > The PRCM CCU drivers depend on clocks provided by other CCU drivers. For
>> > example, the sun8i-r-ccu driver uses the "pll-periph" clock provided by
>> > the SoC's main CCU.
>> >
>> > However, sun8i-r-ccu is an early OF clock provider, and many of the
>> > main CCUs (e.g. sun50i-a64-ccu) use platform drivers. This means that
>> > the consumer clocks will be orphaned until the supplier driver is bound.
>> > This can be avoided by converting the remaining CCUs to use platform
>> > drivers. Then fw_devlink will ensure the drivers are bound in the
>> > optimal order.
>> >
>> > The sun5i CCU is the only one which actually needs to be an early clock
>> > provider, because it provides the clock for the system timer. That one
>> > is left alone.
>> >
>> > Signed-off-by: Samuel Holland <samuel@sholland.org>
>> > ---
>> >
>> > (no changes since v1)
>> >
>> >  drivers/clk/sunxi-ng/Kconfig             | 20 ++++----
>> >  drivers/clk/sunxi-ng/ccu-sun4i-a10.c     | 58 +++++++++++++--------
>> >  drivers/clk/sunxi-ng/ccu-sun50i-h6-r.c   | 56 ++++++++++++--------
>> >  drivers/clk/sunxi-ng/ccu-sun50i-h616.c   | 33 ++++++++----
>> >  drivers/clk/sunxi-ng/ccu-sun6i-a31.c     | 40 +++++++++++----
>> >  drivers/clk/sunxi-ng/ccu-sun8i-a23.c     | 35 +++++++++----
>> >  drivers/clk/sunxi-ng/ccu-sun8i-a33.c     | 40 +++++++++++----
>> >  drivers/clk/sunxi-ng/ccu-sun8i-h3.c      | 62 ++++++++++++++--------
>> >  drivers/clk/sunxi-ng/ccu-sun8i-r.c       | 65 ++++++++++++++----------
>> >  drivers/clk/sunxi-ng/ccu-sun8i-v3s.c     | 57 +++++++++++++--------
>> >  drivers/clk/sunxi-ng/ccu-suniv-f1c100s.c | 38 ++++++++++----
>> >  11 files changed, 332 insertions(+), 172 deletions(-)
>> 
>> This broke the hstimer clocksource on A20 since it requires a clock
>> provided by the sun4i ccu driver.
>
> The A10 is probably broken by this, but the A20 should be able to use
> the arch timers just like all the other Cortex-A7-based SoCs.
>
> Do you have a dmesg log that could help debug why it's not working?

The A20 works as such since, as you say, it has other clocksources.
However, the hstimer has become unusable.  If anyone was using, for
whatever reason, it won't be working for them now.

Before this change, the kernel log used include this line:

clocksource: hstimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370868154 ns

Now there is only a cryptic "Can't get timer clock" in its place.

As it is now, the hstimer driver is nothing but a waste of space.
I figure it ought to be fixed one way or another.

-- 
Måns Rullgård

  reply	other threads:[~2023-06-28 11:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19  3:33 [PATCH v3 0/4] clk: sunxi-ng: Module support Samuel Holland
2021-11-19  3:33 ` [PATCH v3 1/4] clk: sunxi-ng: Export symbols used by CCU drivers Samuel Holland
2021-11-19  3:33 ` [PATCH v3 2/4] clk: sunxi-ng: Allow drivers to be built as modules Samuel Holland
2021-11-19  3:33 ` [PATCH v3 3/4] clk: sunxi-ng: Convert early providers to platform drivers Samuel Holland
2023-06-26 12:21   ` Måns Rullgård
2023-06-28  7:44     ` Maxime Ripard
2023-06-28 11:07       ` Måns Rullgård [this message]
2023-06-28 11:41         ` Maxime Ripard
2023-06-28 18:33           ` Måns Rullgård
2023-06-30 14:17             ` Maxime Ripard
2023-06-30 17:03               ` Måns Rullgård
2021-11-19  3:33 ` [PATCH v3 4/4] clk: sunxi-ng: Allow the CCU core to be built as a module Samuel Holland
2021-11-22  9:06 ` [PATCH v3 0/4] clk: sunxi-ng: Module support Maxime Ripard

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=yw1xa5wj3kvn.fsf@mansr.com \
    --to=mans@mansr.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mripard@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=samuel@sholland.org \
    --cc=sboyd@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