From: 周琰杰 <zhouyanjie@wanyeetech.com>
To: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>,
sboyd@kernel.org, mturquette@baylibre.com,
tsbogend@alpha.franken.de
Cc: paulburton@kernel.org, paul@crapouillou.net,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Clock fixes for Ingenic SoCs
Date: Mon, 9 May 2022 17:12:11 +0800 [thread overview]
Message-ID: <f5ca7c72-6526-d733-93fd-933aa9b719bc@wanyeetech.com> (raw)
In-Reply-To: <20220428164454.17908-1-aidanmacdonald.0x0@gmail.com>
Hi,
On 2022/4/29 上午12:44, Aidan MacDonald wrote:
> 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.
>
> v2: Add comments to patch 02 to explain why we need CLK_IS_CRITICAL.
>
> 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 | 10 ++++++++++
> drivers/clk/ingenic/jz4740-cgu.c | 10 ++++++++++
> drivers/clk/ingenic/jz4760-cgu.c | 10 ++++++++++
> drivers/clk/ingenic/jz4770-cgu.c | 5 +++++
> drivers/clk/ingenic/jz4780-cgu.c | 15 +++++++++++++++
> drivers/clk/ingenic/x1000-cgu.c | 15 +++++++++++++++
> drivers/clk/ingenic/x1830-cgu.c | 11 +++++++++++
> 10 files changed, 80 insertions(+), 27 deletions(-)
Tested-by: 周琰杰 (Zhou Yanjie) <zhouyanjie@wanyeetech.com> # On X1000 and
X1830
prev parent reply other threads:[~2022-05-09 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 16:44 Aidan MacDonald
2022-04-28 16:44 ` [PATCH v2 1/3] clk: ingenic: Allow specifying common clock flags Aidan MacDonald
2022-05-18 20:57 ` Stephen Boyd
2022-04-28 16:44 ` [PATCH v2 2/3] clk: ingenic: Mark critical clocks in Ingenic SoCs Aidan MacDonald
2022-05-18 20:57 ` Stephen Boyd
2022-04-28 16:44 ` [PATCH v2 3/3] mips: ingenic: Do not manually reference the CPU clock Aidan MacDonald
2022-05-18 20:58 ` Stephen Boyd
2022-05-09 9:12 ` 周琰杰 [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=f5ca7c72-6526-d733-93fd-933aa9b719bc@wanyeetech.com \
--to=zhouyanjie@wanyeetech.com \
--cc=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=paulburton@kernel.org \
--cc=sboyd@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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®