From: Jian Hu <jian.hu@amlogic.com>
To: Ronald Claveau <linux-kernel-dev@aliel.fr>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH v2 4/4] arm64: dts: amlogic: t7: Add clk measure support
Date: Mon, 20 Apr 2026 11:25:49 +0800 [thread overview]
Message-ID: <64cde9f6-4f28-4ba7-8362-aac28887ff22@amlogic.com> (raw)
In-Reply-To: <ae61c52d-814c-40fa-b02a-833377d840a8@aliel.fr>
Hi Ronald,
Thanks for your review.
On 4/17/2026 5:48 PM, Ronald Claveau wrote:
> [ EXTERNAL EMAIL ]
>
> Hello Jian,
>
> On 4/15/26 10:33 AM, Jian Hu via B4 Relay wrote:
>> From: Jian Hu <jian.hu@amlogic.com>
>>
>> Add the clock measure device to the T7 SoC family.
>>
>> Signed-off-by: Jian Hu <jian.hu@amlogic.com>
>> ---
>> arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi b/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
>> index 7fe72c94ed62..cec2ea74850d 100644
>> --- a/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
>> +++ b/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
>> @@ -701,6 +701,11 @@ pwm_ao_cd: pwm@60000 {
>> status = "disabled";
>> };
>>
>> + clock-measurer@48000 {
>> + compatible = "amlogic,t7-clk-measure";
>> + reg = <0x0 0x48000 0x0 0x1c>;
>> + };
>> +
> Can you please order by reg, it should be between pwm_ao_gh and pwm_ab.
> Thank you.
According to the "Order of Nodes" chapter in
Documentation/devicetree/bindings/dts-coding-style.rst,
nodes of the same type should be grouped together, and this takes higher
priority.
So I have placed the clock-measure node after all PWM nodes to avoid
splitting the PWM group.
Best regards,
Jian
next prev parent reply other threads:[~2026-04-20 3:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 8:33 [PATCH v2 0/4] soc: amlogic: clk-measure: add A1 and T7 support Jian Hu via B4 Relay
2026-04-15 8:33 ` [PATCH v2 1/4] dt-bindings: soc: amlogic: clk-measure: Add A1 and T7 compatible Jian Hu via B4 Relay
2026-04-15 15:10 ` Conor Dooley
2026-04-15 8:33 ` [PATCH v2 2/4] soc: amlogic: clk-measure: Add A1 and T7 support Jian Hu via B4 Relay
2026-04-20 8:49 ` Neil Armstrong
2026-04-15 8:33 ` [PATCH v2 3/4] arm64: dts: meson: a1: Add clk measure support Jian Hu via B4 Relay
2026-04-15 8:33 ` [PATCH v2 4/4] arm64: dts: amlogic: t7: " Jian Hu via B4 Relay
2026-04-17 9:48 ` Ronald Claveau
2026-04-20 3:25 ` Jian Hu [this message]
2026-04-20 8:52 ` Neil Armstrong
2026-04-21 6:40 ` Jian Hu
2026-04-20 9:16 ` Ronald Claveau
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=64cde9f6-4f28-4ba7-8362-aac28887ff22@amlogic.com \
--to=jian.hu@amlogic.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel-dev@aliel.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@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