From: Rob Herring <robh@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-amlogic@lists.infradead.org, linux-pwm@vger.kernel.org,
JunYi Zhao <junyi.zhao@amlogic.com>
Subject: Re: [PATCH 1/6] dt-bindings: pwm: amlogic: fix s4 bindings
Date: Wed, 8 Nov 2023 11:04:48 -0600 [thread overview]
Message-ID: <20231108170448.GA2388329-robh@kernel.org> (raw)
In-Reply-To: <20231106103259.703417-2-jbrunet@baylibre.com>
On Mon, Nov 06, 2023 at 11:32:48AM +0100, Jerome Brunet wrote:
> s4 has been added to the compatible list while converting the Amlogic PWM
> binding documentation from txt to yaml.
>
> However, on the s4, the clock bindings have different meaning compared to
> previous SoCs.
>
> On previous SoCs the clock bindings used to describe which input the PWM
> channel multiplexer should pick among its possible parents.
>
> This is very much tied to the driver implementation, instead of describing
> the HW for what it is. When support for the Amlogic PWM was first added,
> how to deal with clocks through DT was not as clear as it nowadays.
> The Linux driver now ignores this DT setting, but still relies on the
> hard-coded list of clock sources.
>
> On the s4, the input multiplexer is gone. The clock bindings actually
> describe the clock as it exists, not a setting. The property has a
> different meaning, even if it is still 2 clocks and it would pass the check
> when support is actually added.
>
> Also the s4 cannot work if the clocks are not provided, so the property no
> longer optional.
>
> Finally, for once it makes sense to see the input as being numbered
> somehow. No need to bother with clock-names on the s4 type of PWM.
>
> Fixes: 43a1c4ff3977 ("dt-bindings: pwm: Convert Amlogic Meson PWM binding")
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
> .../devicetree/bindings/pwm/pwm-amlogic.yaml | 68 ++++++++++++++++---
> 1 file changed, 59 insertions(+), 9 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml b/Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml
> index 527864a4d855..754b70fc2db0 100644
> --- a/Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml
> +++ b/Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml
> @@ -9,9 +9,6 @@ title: Amlogic PWM
> maintainers:
> - Heiner Kallweit <hkallweit1@gmail.com>
>
> -allOf:
> - - $ref: pwm.yaml#
> -
> properties:
> compatible:
> oneOf:
> @@ -43,12 +40,8 @@ properties:
> maxItems: 2
>
> clock-names:
> - oneOf:
> - - items:
> - - enum: [clkin0, clkin1]
> - - items:
> - - const: clkin0
> - - const: clkin1
> + minItems: 1
> + maxItems: 2
>
> "#pwm-cells":
> const: 3
> @@ -57,6 +50,56 @@ required:
> - compatible
> - reg
>
> +allOf:
> + - $ref: pwm.yaml#
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - amlogic,meson8-pwm
> + - amlogic,meson8b-pwm
> + - amlogic,meson-gxbb-pwm
> + - amlogic,meson-gxbb-ao-pwm
> + - amlogic,meson-axg-ee-pwm
> + - amlogic,meson-axg-ao-pwm
> + - amlogic,meson-g12a-ee-pwm
> + - amlogic,meson-g12a-ao-pwm-ab
> + - amlogic,meson-g12a-ao-pwm-cd
> + - amlogic,meson-gx-pwm
> + - amlogic,meson-gx-ao-pwm
> + then:
> + # Historic bindings tied to the driver implementation
> + # The clocks provided here are meant to be matched with the input
> + # known (hard-coded) in the driver and used to select pwm clock
> + # source. Currently, the linux driver ignores this.
> + properties:
> + clock-names:
> + oneOf:
> + - items:
> + - enum: [clkin0, clkin1]
> + - items:
> + - const: clkin0
> + - const: clkin1
> +
> + # Newer IP block take a single input per channel, instead of 4 inputs
> + # for both channels
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - amlogic,meson-s4-pwm
> + then:
> + properties:
> + clocks:
> + items:
> + - description: input clock of PWM channel A
> + - description: input clock of PWM channel B
> + required:
> + - clocks
What are the 'clock-names' in this case? Because it's still allowed.
Rob
next prev parent reply other threads:[~2023-11-08 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:32 [PATCH 0/6] pwm: meson: dt-bindings fixup Jerome Brunet
2023-11-06 10:32 ` [PATCH 1/6] dt-bindings: pwm: amlogic: fix s4 bindings Jerome Brunet
2023-11-08 17:04 ` Rob Herring [this message]
2023-11-08 17:08 ` Jerome Brunet
2023-11-06 10:32 ` [PATCH 2/6] dt-bindings: pwm: amlogic: add new compatible for meson8 pwm type Jerome Brunet
2023-11-06 12:03 ` Jerome Brunet
2023-11-08 17:06 ` Rob Herring
2023-11-08 17:10 ` Jerome Brunet
2023-11-06 10:32 ` [PATCH 3/6] pwm: meson: prepare addition of new compatible types Jerome Brunet
2023-11-06 10:32 ` [PATCH 4/6] pwm: meson: add generic compatible for meson8 to sm1 Jerome Brunet
2023-11-06 10:32 ` [PATCH 5/6] arm: dts: amlogic: migrate pwms to new meson8 v2 binding Jerome Brunet
2023-11-06 10:32 ` [PATCH 6/6] arm64: " Jerome Brunet
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=20231108170448.GA2388329-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=junyi.zhao@amlogic.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=thierry.reding@gmail.com \
/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