From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mubin Sayyed <mubin.sayyed@amd.com>,
robh+dt@kernel.org, treding@nvidia.com,
u.kleine-koenig@pengutronix.de, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, git@amd.com, michal.simek@amd.com,
siva.durga.prasad.paladugu@amd.com, mubin10@gmail.com
Subject: Re: [LINUX PATCH 2/3] dt-bindings: timer: Update device tree bindings for cadence TTC PWM
Date: Thu, 12 Jan 2023 11:10:52 +0100 [thread overview]
Message-ID: <06144828-d1c4-7423-81e3-9c35df996da7@kernel.org> (raw)
In-Reply-To: <20230112071526.3035949-3-mubin.sayyed@amd.com>
On 12/01/2023 08:15, Mubin Sayyed wrote:
> Cadence TTC can act as PWM device, it is supported through
Subject: drop second/last, redundant "device tree bindings". The
"dt-bindings" prefix is already stating that these are bindings.
Anyway subject is poor - every commit is an "update", so basically you
said there nothing...
> separate PWM framework based driver. Decision to configure
> specific TTC device as PWM or clocksource/clockevent would
> be done based on presence of "#pwm-cells" property.
>
> Also, interrupt property is not required for TTC PWM driver.
> Updated bindings to support TTC PWM configuration.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
>
> Signed-off-by: Mubin Sayyed <mubin.sayyed@amd.com>
> ---
> .../devicetree/bindings/timer/cdns,ttc.yaml | 25 ++++++++++++++++++-
> 1 file changed, 24 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/timer/cdns,ttc.yaml b/Documentation/devicetree/bindings/timer/cdns,ttc.yaml
> index 7d821fd480f6..2855e92e02e3 100644
> --- a/Documentation/devicetree/bindings/timer/cdns,ttc.yaml
> +++ b/Documentation/devicetree/bindings/timer/cdns,ttc.yaml
> @@ -32,12 +32,26 @@ properties:
> description: |
> Bit width of the timer, necessary if not 16.
>
> + "#pwm-cells":
> + description: |
> + Required to configure TTC as PWM device, supported cells are 0 to 3.
> + minimum: 0
> + maximum: 3
Better make it const. What's the benefit of flexible cells? You also
should describe the arguments.
> +
> required:
> - compatible
> - reg
> - - interrupts
> - clocks
>
> +allOf:
> + - if:
> + not:
> + required:
> + - "#pwm-cells"
> + then:
> + required:
> + - interrupts
> +
> additionalProperties: false
>
> examples:
> @@ -50,3 +64,12 @@ examples:
> clocks = <&cpu_clk 3>;
> timer-width = <32>;
> };
> +
> + - |
> + ttc1: ttc1@f8002000 {
Node names should be generic.
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> + compatible = "cdns,ttc";
> + reg = <0xF8002000 0x1000>;
lowercase hex
> + clocks = <&cpu_clk 3>;
> + timer-width = <32>;
> + #pwm-cells = <3>;
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-12 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 7:15 [LINUX PATCH 0/3] Add initial support for TTC PWM driver Mubin Sayyed
2023-01-12 7:15 ` [LINUX PATCH 1/3] clocksource: timer-cadence-ttc: Do not probe TTC device configured as PWM Mubin Sayyed
2023-01-12 21:30 ` Uwe Kleine-König
2023-01-12 7:15 ` [LINUX PATCH 2/3] dt-bindings: timer: Update device tree bindings for cadence TTC PWM Mubin Sayyed
2023-01-12 10:10 ` Krzysztof Kozlowski [this message]
2023-01-12 7:15 ` [LINUX PATCH 3/3] pwm: pwm-cadence: Add support for " Mubin Sayyed
2023-01-12 17:57 ` kernel test robot
2023-01-12 21:25 ` Uwe Kleine-König
2023-01-17 9:58 ` Sayyed, Mubin
2023-01-17 11:27 ` Uwe Kleine-König
2023-01-17 12:55 ` Sayyed, Mubin
2023-01-17 14:05 ` Uwe Kleine-König
2023-01-13 8:13 ` Krzysztof Kozlowski
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=06144828-d1c4-7423-81e3-9c35df996da7@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=mubin.sayyed@amd.com \
--cc=mubin10@gmail.com \
--cc=robh+dt@kernel.org \
--cc=siva.durga.prasad.paladugu@amd.com \
--cc=treding@nvidia.com \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).