From: Krzysztof Kozlowski <krzk@kernel.org>
To: Charan Pedumuru <charan.pedumuru@gmail.com>
Cc: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Pal Singh" <ajitpal.singh@st.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: pwm: st,pwm: convert to DT schema
Date: Tue, 23 Jun 2026 16:25:05 +0200 [thread overview]
Message-ID: <761cb58f-17cd-4a0b-98eb-a38b3b619941@kernel.org> (raw)
In-Reply-To: <464e09d2-5a8f-42ea-998a-42cf1376a6e7@gmail.com>
On 23/06/2026 16:16, Charan Pedumuru wrote:
>
>
> On 23-06-2026 12:47, Krzysztof Kozlowski wrote:
>> On Thu, Jun 18, 2026 at 12:42:07PM +0000, Charan Pedumuru wrote:
>>> +description:
>>> + The STiH41x PWM controller supports both PWM output and input capture
>>> + functionality. It provides multiple PWM output channels for generating
>>> + variable duty-cycle waveforms, and multiple input capture channels for
>>> + measuring external signal periods and pulse widths. PWM output channels
>>> + and input capture channels are configured independently via
>>> + st,pwm-num-chan and st,capture-num-chan respectively.
>>> +
>>> +allOf:
>>> + - $ref: pwm.yaml#
>>
>> Where is this compatible used?
>
> I will remove this allof and redefine the YAML again
>
Sorry, I think I messed something so comment was incorrectly placed.
The comment should be under:
"+ const: st,pwm"
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-23 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 12:42 [PATCH v2] dt-bindings: pwm: st,pwm: convert to DT schema Charan Pedumuru
2026-06-18 12:55 ` sashiko-bot
2026-06-23 7:17 ` Krzysztof Kozlowski
2026-06-23 14:16 ` Charan Pedumuru
2026-06-23 14:25 ` Krzysztof Kozlowski [this message]
2026-06-23 14:31 ` Charan Pedumuru
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=761cb58f-17cd-4a0b-98eb-a38b3b619941@kernel.org \
--to=krzk@kernel.org \
--cc=ajitpal.singh@st.com \
--cc=charan.pedumuru@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ukleinek@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