From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chuan Liu <chuan.liu@amlogic.com>
Cc: 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>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/13] dt-bindings: soc: amlogic: Add clk-measure related properties
Date: Wed, 20 Aug 2025 10:08:50 +0200 [thread overview]
Message-ID: <20250820-robust-didactic-panda-d374be@kuoka> (raw)
In-Reply-To: <20250815-add-more-socs-to-support-clk_measure-v1-1-59f04ba67457@amlogic.com>
On Fri, Aug 15, 2025 at 04:37:27PM +0800, Chuan Liu wrote:
> Add three properties to clk-measure: 'clkmsr-indices', 'clkmsr-names',
> and 'clkmsr-reg-v2' for describing measurable channels and register
> offsets in DT.
>
> Signed-off-by: Chuan Liu <chuan.liu@amlogic.com>
> ---
> .../soc/amlogic/amlogic,meson-gx-clk-measure.yaml | 54 +++++++++++++++++++++-
> 1 file changed, 53 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/soc/amlogic/amlogic,meson-gx-clk-measure.yaml b/Documentation/devicetree/bindings/soc/amlogic/amlogic,meson-gx-clk-measure.yaml
> index 39d4637c2d08..1c9d37eef5f0 100644
> --- a/Documentation/devicetree/bindings/soc/amlogic/amlogic,meson-gx-clk-measure.yaml
> +++ b/Documentation/devicetree/bindings/soc/amlogic/amlogic,meson-gx-clk-measure.yaml
> @@ -6,7 +6,7 @@ $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> title: Amlogic Internal Clock Measurer
>
> -description:
> +description: |
Why?
> The Amlogic SoCs contains an IP to measure the internal clocks.
> The precision is multiple of MHz, useful to debug the clock states.
>
> @@ -28,15 +28,67 @@ properties:
> reg:
> maxItems: 1
>
> + clkmsr-indices:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description: |
Why | ?
> + Supported channel IDs for clk-measure.
> + minItems: 1
> + maxItems: 256
Nothing - neither this nor commit msg - explains why you need it and
what this is.
> +
> + clkmsr-names:
> + $ref: /schemas/types.yaml#/definitions/string-array
> + description: |
> + The channel ID names supported by clk-measure correspond one-to-one with
> + the IDs specified in 'clkmsr-indices'.
> +
> + Therefore, the defined 'clkmsr-indices' and 'clkmsr-names' must have
> + matching counts and maintain strict correspondence.
> + minItems: 1
> + maxItems: 256
> +
> + clkmsr-reg-v2:
> + type: boolean
> + description: |
> + Specify whether the register address offset for clk-measure corresponds
> + to version V2.
No, compatible defines this.
> +
> required:
> - compatible
> - reg
> + - clkmsr-indices
> + - clkmsr-names
That's ABI break. Again, nothing explains it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-20 8:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 8:37 [PATCH 00/13] soc: amlogic: clk-measure: Add more SoCs to support clk-measure Chuan Liu via B4 Relay
2025-08-15 8:37 ` [PATCH 01/13] dt-bindings: soc: amlogic: Add clk-measure related properties Chuan Liu via B4 Relay
2025-08-20 8:08 ` Krzysztof Kozlowski [this message]
2025-08-15 8:37 ` [PATCH 02/13] soc: amlogic: clk-measure: Remove the msr_data from clk-measure Chuan Liu via B4 Relay
2025-08-20 8:10 ` Krzysztof Kozlowski
2025-08-15 8:37 ` [PATCH 03/13] ARM: dts: amlogic: add clk-measure IDs and names for meson SoC family Chuan Liu via B4 Relay
2025-08-15 8:37 ` [PATCH 04/13] arm64: dts: amlogic: add clk-measure IDs and names for Amlogic SoCs Chuan Liu via B4 Relay
2025-08-15 8:37 ` [PATCH 05/13] dt-bindings: soc: amlogic: Unify the compatible property for clk-measure Chuan Liu via B4 Relay
2025-08-20 8:09 ` Krzysztof Kozlowski
2025-08-15 8:37 ` [PATCH 06/13] soc: amlogic: clk-measure: Unify the compatible property Chuan Liu via B4 Relay
2025-08-20 8:11 ` Krzysztof Kozlowski
2025-08-15 8:37 ` [PATCH 07/13] ARM: dts: amlogic: Unify the compatible property for clk-measure Chuan Liu via B4 Relay
2025-08-15 8:37 ` [PATCH 08/13] arm64: " Chuan Liu via B4 Relay
2025-08-20 8:11 ` Krzysztof Kozlowski
2025-08-15 8:37 ` [PATCH 09/13] arm64: dts: amlogic: A4: Add clk-measure controller node Chuan Liu via B4 Relay
2025-08-15 8:37 ` [PATCH 10/13] arm64: dts: amlogic: A5: " Chuan Liu via B4 Relay
2025-08-15 8:37 ` [PATCH 11/13] arm64: dts: amlogic: S7: " Chuan Liu via B4 Relay
2025-08-15 8:37 ` [PATCH 12/13] arm64: dts: amlogic: S7D: " Chuan Liu via B4 Relay
2025-08-15 8:37 ` [PATCH 13/13] arm64: dts: amlogic: S6: " Chuan Liu via B4 Relay
2025-08-18 8:01 ` [PATCH 00/13] soc: amlogic: clk-measure: Add more SoCs to support clk-measure Neil Armstrong
2025-08-19 3:32 ` Chuan Liu
2025-08-20 8:12 ` Krzysztof Kozlowski
2025-08-20 10:05 ` Chuan Liu
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=20250820-robust-didactic-panda-d374be@kuoka \
--to=krzk@kernel.org \
--cc=chuan.liu@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@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