From: Vivian Wang <wangruikang@iscas.ac.cn>
To: Yixun Lan <dlan@gentoo.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: spacemit: uart: set dummy clock to silent dt warning
Date: Sat, 19 Jul 2025 15:48:13 +0800 [thread overview]
Message-ID: <22fd8b89-b937-48db-a5bf-4e468441b206@iscas.ac.cn> (raw)
In-Reply-To: <20250718-02-k1-uart-clock-v1-1-698e884aa717@gentoo.org>
On 7/18/25 23:13, Yixun Lan wrote:
> sec_uart1 is reserved in DT, and no clock is implemented in the CCF
> framework, thus 'make dtbs_check' will eject this warning message:
> serial@f0612000: 'clock-names' is a required property
>
> So, adding a dummy clock to the device tree to fulfill the clock
> requirement, then silent this dt check warning.
NAK. This is definitely worse than the warning.
Honestly, if you don't like this warning, I think we should just drop
the node. If not...
>
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
> ---
> arch/riscv/boot/dts/spacemit/k1.dtsi | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/arch/riscv/boot/dts/spacemit/k1.dtsi b/arch/riscv/boot/dts/spacemit/k1.dtsi
> index c0f8c5fca975d73b6ea6886da13fcf55289cb16c..e9b98f2a3b1cc38f569d7de336630df846cbfbe7 100644
> --- a/arch/riscv/boot/dts/spacemit/k1.dtsi
> +++ b/arch/riscv/boot/dts/spacemit/k1.dtsi
> @@ -309,6 +309,13 @@ cluster1_l2_cache: l2-cache1 {
> };
>
> clocks {
> + clk_dummy: clock-dummy {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <0>;
That can't be right for UART, which depends on knowing about the baud
clock rate. If we want a fixed clock to represent whatever the "secure"
clock controller has at least it should be set to the nominal frequency.
Vivian "dramforever" Wang
> + clock-output-names = "clk_dummy";
> + };
> +
> vctcxo_1m: clock-1m {
> compatible = "fixed-clock";
> clock-frequency = <1000000>;
> @@ -556,8 +563,9 @@ clint: timer@e4000000 {
> sec_uart1: serial@f0612000 {
> compatible = "spacemit,k1-uart", "intel,xscale-uart";
> reg = <0x0 0xf0612000 0x0 0x100>;
> + clocks = <&clk_dummy>, <&clk_dummy>;
> + clock-names = "core", "bus";
> interrupts = <43>;
> - clock-frequency = <14857000>;
> reg-shift = <2>;
> reg-io-width = <4>;
> status = "reserved"; /* for TEE usage */
>
> ---
> base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
> change-id: 20250718-02-k1-uart-clock-0beb9ef10fe0
>
> Best regards,
next prev parent reply other threads:[~2025-07-19 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 15:13 [PATCH] riscv: dts: spacemit: uart: set dummy clock to silent dt warning Yixun Lan
2025-07-19 7:48 ` Vivian Wang [this message]
2025-07-19 10:23 ` Yixun Lan
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=22fd8b89-b937-48db-a5bf-4e468441b206@iscas.ac.cn \
--to=wangruikang@iscas.ac.cn \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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