From: Kelvin Zhang <kelvin.zhang@amlogic.com>
To: George Stark <gnstark@salutedevices.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: "Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Kevin Hilman" <khilman@baylibre.com>,
linux-pwm@vger.kernel.org, "Jerome Brunet" <jbrunet@baylibre.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>
Subject: Re: [DMARC error][DKIM error] [PATCH 1/2] dt-bindings: pwm: amlogic: Document C3 PWM
Date: Tue, 10 Sep 2024 10:22:38 +0800 [thread overview]
Message-ID: <6326decd-cb9f-4095-9aca-4d40819d2eb4@amlogic.com> (raw)
In-Reply-To: <fcd005d2-dba4-4980-8d0d-f55632c7a6d9@salutedevices.com>
On 2024/9/9 20:49, George Stark wrote:
> [ EXTERNAL EMAIL ]
>
> Hello Kelvin, Krzysztof
>
> There's acked yet not merged patch [1] adding amlogic,meson-a1-pwm with
> s4 as back-compatible. Should amlogic,c3-pwm be added in the enum along
> with a1?
>
> [1]
> https://lore.kernel.org/linux-arm-kernel/dbb4be50-4793-40ab-
> b362-6c9a6dd87324@salutedevices.com/T/
>
Hello George,
I've noticed your patch.
Once it is merged, I will rebase my submission.
Thanks!
> On 9/6/24 15:46, Kelvin Zhang via B4 Relay wrote:
>> From: Kelvin Zhang <kelvin.zhang@amlogic.com>
>>
>> Document amlogic,c3-pwm compatible, which falls back to the meson-s4-pwm
>> group.
>>
>> Signed-off-by: Kelvin Zhang <kelvin.zhang@amlogic.com>
>> ---
>> Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml b/
>> Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml
>> index 1d71d4f8f328..356371164acd 100644
>> --- a/Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml
>> +++ b/Documentation/devicetree/bindings/pwm/pwm-amlogic.yaml
>> @@ -44,6 +44,10 @@ properties:
>> - amlogic,meson-axg-pwm-v2
>> - amlogic,meson-g12-pwm-v2
>> - const: amlogic,meson8-pwm-v2
>> + - items:
>> + - enum:
>> + - amlogic,c3-pwm
>> + - const: amlogic,meson-s4-pwm
>>
>> reg:
>> maxItems: 1
>>
>
> --
> Best regards
> George
next prev parent reply other threads:[~2024-09-10 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 12:46 [PATCH 0/2] Add support for Amlogic C3 PWM Kelvin Zhang via B4 Relay
2024-09-06 12:46 ` [PATCH 1/2] dt-bindings: pwm: amlogic: Document " Kelvin Zhang via B4 Relay
2024-09-06 12:50 ` Krzysztof Kozlowski
2024-09-09 10:43 ` Kelvin Zhang
2024-09-09 12:49 ` [DMARC error][DKIM error] " George Stark
2024-09-10 2:22 ` Kelvin Zhang [this message]
2024-09-06 12:46 ` [PATCH 2/2] arm64: dts: amlogic: Add Amlogic " Kelvin Zhang via B4 Relay
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=6326decd-cb9f-4095-9aca-4d40819d2eb4@amlogic.com \
--to=kelvin.zhang@amlogic.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gnstark@salutedevices.com \
--cc=hkallweit1@gmail.com \
--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=linux-pwm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.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