[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250205-magnificent-spiffy-crab-54d631@krzk-bin>
Date: Wed, 5 Feb 2025 09:40:53 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Kaustabh Chakraborty <kauschluss@...root.org>
Cc: Sylwester Nawrocki <s.nawrocki@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>, Alim Akhtar <alim.akhtar@...sung.com>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor@...nel.org>, Tomasz Figa <tomasz.figa@...il.com>,
Sergey Lisov <sleirsgoevy@...il.com>, linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 2/5] dt-bindings: clock: document exynos7870 clock driver
CMU bindings
On Tue, Feb 04, 2025 at 02:07:30AM +0530, Kaustabh Chakraborty wrote:
> Provide dt-schema documentation for Exynos7870 SoC clock controller.
>
> Signed-off-by: Kaustabh Chakraborty <kauschluss@...root.org>
> ---
> .../bindings/clock/samsung,exynos7870-clock.yaml | 246 +++++++++++++++++++++
> 1 file changed, 246 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/clock/samsung,exynos7870-clock.yaml b/Documentation/devicetree/bindings/clock/samsung,exynos7870-clock.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..697e03ca191d685b71672d35257b022c663244ed
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/samsung,exynos7870-clock.yaml
> @@ -0,0 +1,246 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/clock/samsung,exynos7870-clock.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Samsung Exynos7870 SoC clock controller
> +
> +maintainers:
> + - Chanwoo Choi <cw00.choi@...sung.com>
> + - Krzysztof Kozlowski <krzk@...nel.org>
> + - Sylwester Nawrocki <s.nawrocki@...sung.com>
> + - Tomasz Figa <tomasz.figa@...il.com>
This should be someone responsible for this device rather.
> +
> +description: |
> + Exynos7870 clock controller is comprised of several CMU units, generating
> + clocks for different domains. Those CMU units are modeled as separate device
> + tree nodes, and might depend on each other. The root clock in that root tree
> + is an external clock: OSCCLK (26 MHz). This external clock must be defined
> + as a fixed-rate clock in dts.
> +
> + Each clock is assigned an identifier and client nodes can use this identifier
> + to specify the clock which they consume. All clocks available for usage
> + in clock consumer nodes are defined as preprocessor macros in
> + 'dt-bindings/clock/exynos7870.h' header.
> +
> +properties:
> + compatible:
> + enum:
> + - samsung,exynos7870-cmu-mif
> + - samsung,exynos7870-cmu-dispaud
> + - samsung,exynos7870-cmu-fsys
> + - samsung,exynos7870-cmu-g3d
> + - samsung,exynos7870-cmu-isp
> + - samsung,exynos7870-cmu-mfcmscl
> + - samsung,exynos7870-cmu-peri
> +
> + clocks:
> + minItems: 1
> + maxItems: 10
> +
> + clock-names:
> + minItems: 1
> + maxItems: 10
> +
> + "#clock-cells":
> + const: 1
> +
> + reg:
> + maxItems: 1
> +
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: samsung,exynos7870-cmu-mif
> +
> + then:
> + properties:
> + clocks:
> + items:
> + - description: External reference clock (26 MHz)
> +
> + clock-names:
> + items:
> + - const: oscclk
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: samsung,exynos7870-cmu-dispaud
> +
> + then:
> + properties:
> + clocks:
> + items:
> + - description: External reference clock (26 MHz)
> + - description: CMU_DISPAUD bus clock (from CMU_MIF)
> + - description: DECON external clock (from CMU_MIF)
> + - description: DECON vertical clock (from CMU_MIF)
> +
> + clock-names:
> + items:
> + - const: oscclk
> + - const: gout_mif_cmu_dispaud_busa
We switched some time ago to what is usually recommended, so purpose of
the clock, not the actual source clock name. See Exynos8895.
I do not see any of my other comments implemented and you sent it AFTER
I replied already.
Also, this is not v1, but v2. Implement the feedback, add proper
changelog and version the patches.
Best regards,
Krzysztof
Powered by blists - more mailing lists