Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yu-Chun Lin" <eleanor.lin@realtek.com>
Cc: conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v7 10/10] arm64: dts: realtek: Add clock support for RTD1625
Date: Fri, 08 May 2026 23:55:29 +0000	[thread overview]
Message-ID: <20260508235530.5C052C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260508111641.3192177-11-eleanor.lin@realtek.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] Device tree nodes with a unit-address should be ordered by their physical unit-address, but `clock-controller@7088` is incorrectly placed after `serial@7800`.
- [Low] The fixed-clock node is named `osc`, which uses a deprecated naming format according to the `fixed-clock` bindings.
--

commit a60494898a192c94263b0fcf9833b624f1fce48f
Author: Yu-Chun Lin <eleanor.lin@realtek.com>

arm64: dts: realtek: Add clock support for RTD1625

This commit adds the clock controller nodes and an osc27m fixed clock for
the Realtek RTD1625 SoC to the kent.dtsi device tree.

> diff --git a/arch/arm64/boot/dts/realtek/kent.dtsi b/arch/arm64/boot/dts/realtek/kent.dtsi
> index ae006ce244205..4722337a143d8 100644
> --- a/arch/arm64/boot/dts/realtek/kent.dtsi
> +++ b/arch/arm64/boot/dts/realtek/kent.dtsi
> @@ -26,6 +26,15 @@ timer {
>  			     <GIC_PPI  9 IRQ_TYPE_LEVEL_HIGH>;
>  	};
>  
> +	clocks {
> +		osc27m: osc {

This isn't a bug, but does the node name osc follow the fixed-clock bindings?
The fixed-clock schema deprecates generic names like osc and prefers names
matching the clock-([0-9]+|[a-z0-9-]+) pattern, such as clock-27000000.

> +			compatible = "fixed-clock";
> +			clock-frequency = <27000000>;
> +			clock-output-names = "osc27m";
> +			#clock-cells = <0>;
> +		};
> +	};
> +

[ ... ]

>  			uart0: serial@7800 {
>  				compatible = "snps,dw-apb-uart";
>  				reg = <0x7800 0x100>;
> @@ -150,6 +167,22 @@ uart0: serial@7800 {
>  				reg-shift = <2>;
>  				status = "disabled";
>  			};
> +
> +			ic: clock-controller@7088 {

This isn't a bug, but should clock-controller@7088 be placed before
serial@7800? Device tree nodes with unit-addresses are typically sorted in
ascending order by their physical address.

> +				compatible = "realtek,rtd1625-iso-clk";
> +				reg = <0x7088 0x8>;
> +				clocks = <&osc27m>;
> +				#clock-cells = <1>;
> +				#reset-cells = <1>;
> +			};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260508111641.3192177-1-eleanor.lin@realtek.com?part=10

      reply	other threads:[~2026-05-08 23:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 11:16 [PATCH v7 00/10] clk: realtek: Add RTD1625 clock support Yu-Chun Lin
2026-05-08 11:16 ` [PATCH v7 01/10] dt-bindings: clock: Add Realtek RTD1625 Clock & Reset Controller Yu-Chun Lin
2026-05-08 11:16 ` [PATCH v7 02/10] reset: Add Realtek basic reset support Yu-Chun Lin
2026-05-08 11:16 ` [PATCH v7 03/10] clk: realtek: Introduce a common probe() Yu-Chun Lin
2026-05-08 21:24   ` sashiko-bot
2026-05-08 11:16 ` [PATCH v7 04/10] clk: realtek: Add support for phase locked loops (PLLs) Yu-Chun Lin
2026-05-08 21:41   ` sashiko-bot
2026-05-08 11:16 ` [PATCH v7 05/10] clk: realtek: Add support for gate clock Yu-Chun Lin
2026-05-08 11:16 ` [PATCH v7 06/10] clk: realtek: Add support for mux clock Yu-Chun Lin
2026-05-08 22:21   ` sashiko-bot
2026-05-08 11:16 ` [PATCH v7 07/10] clk: realtek: Add support for MMC-tuned PLL clocks Yu-Chun Lin
2026-05-08 22:42   ` sashiko-bot
2026-05-08 11:16 ` [PATCH v7 08/10] clk: realtek: Add RTD1625-CRT clock controller driver Yu-Chun Lin
2026-05-08 23:17   ` sashiko-bot
2026-05-08 11:16 ` [PATCH v7 09/10] clk: realtek: Add RTD1625-ISO " Yu-Chun Lin
2026-05-08 23:50   ` sashiko-bot
2026-05-08 11:16 ` [PATCH v7 10/10] arm64: dts: realtek: Add clock support for RTD1625 Yu-Chun Lin
2026-05-08 23:55   ` sashiko-bot [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=20260508235530.5C052C2BCB0@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eleanor.lin@realtek.com \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko@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