From: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Clock fixes for Ingenic SoCs
Date: Wed, 9 Feb 2022 23:38:01 +0000 [thread overview]
Message-ID: <YgRQWfUmdXZU606t@localhost> (raw)
In-Reply-To: <EPN17R.TB21BVY3XDUH1@crapouillou.net>
On Wed, Feb 09, 2022 at 03:44:02PM +0000, Paul Cercueil wrote:
> Hi Aidan,
>
> Le mar., févr. 8 2022 at 01:00:45 +0000, Aidan MacDonald
> <aidanmacdonald.0x0@gmail.com> a écrit :
> > I ran across a problem trying to get Linux running on an Ingenic
> > X1000 SoC:
> > since the memory clock isn't referenced by any driver, it appears
> > unused and
> > gets disabled automatically. After that, the system hangs on any RAM
> > access.
> >
> > There is a hack in board-ingenic.c to forcibly enable the CPU clock,
> > but this
> > is insufficient for the X1000 since the memory clock has its own gate
> > and mux
> > that isn't tied to the CPU.
> >
> > This patch series fixes the bug by adding CLK_IS_CRITICAL flags to
> > important
> > clocks, which seems to be the approach used in many other SoC clock
> > drivers.
> >
> > It's my first time submitting patches to the kernel so let me know if
> > I
> > messed anything up.
>
> You did everything good.
>
> I think the CI20 suffered from the same problem, it would only boot as
> long as the "clk_ignore_unused" flag was added on the command line. I
> will need to try it there to see if it improved the situation.
>
> I tested the patchset on JZ4770 and it works fine. So:
>
> Reviewed-by: Paul Cercueil <paul@crapouillou.net>
>
> @Stephen: I don't see any changes pending on board-ingenic.c so it
> should be safe for you to also take [PATCH 3/3] in the clk tree.
>
> Cheers,
> -Paul
Thanks Paul. I've just sent two other small fixes which are basically
independent of this series, if you want to test them at the same time.
One is for the TCU driver and the other is for the pinctrl driver.
Regards,
Aidan
>
> > Aidan MacDonald (3):
> > clk: ingenic: Allow specifying common clock flags
> > clk: ingenic: Mark critical clocks in Ingenic SoCs
> > mips: ingenic: Do not manually reference the CPU clock
> >
> > arch/mips/generic/board-ingenic.c | 26 --------------------------
> > drivers/clk/ingenic/cgu.c | 2 +-
> > drivers/clk/ingenic/cgu.h | 3 +++
> > drivers/clk/ingenic/jz4725b-cgu.c | 2 ++
> > drivers/clk/ingenic/jz4740-cgu.c | 2 ++
> > drivers/clk/ingenic/jz4760-cgu.c | 2 ++
> > drivers/clk/ingenic/jz4770-cgu.c | 1 +
> > drivers/clk/ingenic/jz4780-cgu.c | 3 +++
> > drivers/clk/ingenic/x1000-cgu.c | 3 +++
> > drivers/clk/ingenic/x1830-cgu.c | 3 +++
> > 10 files changed, 20 insertions(+), 27 deletions(-)
> >
> > --
> > 2.34.1
> >
>
>
prev parent reply other threads:[~2022-02-09 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 1:00 [PATCH 0/3] Clock fixes for Ingenic SoCs Aidan MacDonald
2022-02-08 1:00 ` [PATCH 1/3] clk: ingenic: Allow specifying common clock flags Aidan MacDonald
2022-02-08 1:00 ` [PATCH 2/3] clk: ingenic: Mark critical clocks in Ingenic SoCs Aidan MacDonald
2022-02-08 1:00 ` [PATCH 3/3] mips: ingenic: Do not manually reference the CPU clock Aidan MacDonald
2022-02-09 15:44 ` [PATCH 0/3] Clock fixes for Ingenic SoCs Paul Cercueil
2022-02-09 23:38 ` Aidan MacDonald [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=YgRQWfUmdXZU606t@localhost \
--to=aidanmacdonald.0x0@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).