From: Krzysztof Kozlowski <krzk@kernel.org>
To: Xuyang Dong <dongxuyang@eswincomputing.com>, ben.dooks@codethink.co.uk
Cc: ukleinek@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, p.zabel@pengutronix.de,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ningyu@eswincomputing.com,
linmin@eswincomputing.com, xuxiang@eswincomputing.com,
wangguosheng@eswincomputing.com, pinkesh.vaghela@einfochips.com
Subject: Re: [PATCH 1/2] dt-bindings: pwm: eswin: Add EIC7700 pwm controller
Date: Tue, 9 Dec 2025 22:40:55 +0100 [thread overview]
Message-ID: <502cc1eb-87a6-4574-903a-6181cd2258cc@kernel.org> (raw)
In-Reply-To: <47025bea.10ca.19b02a06c69.Coremail.dongxuyang@eswincomputing.com>
On 09/12/2025 11:20, Xuyang Dong wrote:
>>> +
>>> + pinctrl-0: true
>>> + pinctrl-1: true
>>> +
>>> + pinctrl-names:
>>> + minItems: 1
>>> + items:
>>> + - const: default
>>> + - const: sleep
>>> +
>>> + snps,pwm-full-range-enable:
>>
>> 1. Wrong vendor prefix, thats eswin, not snps.
>> 2. Why is this a hardware property? I really do not see that. You
>> described the desired Linux feature or behavior, not the actual
>> hardware. The bindings are about the latter, so instead you need to
>> rephrase the property and its description to match actual hardware
>> capabilities/features/configuration etc.
>>
> Hi Krzysztof and Ben,
>
> There is a patch [1] submmitted by Ben Dook a few years ago. The
> intention of this patch is to make DWC pwm controller can be used as
> platform driver. This is what we are currently working on.
> It seems that it would be more reasonable to continue improving this
> patch and make the DWC PWM driver universal, rather than creating a
> separate ESWIN PWM driver.
>
> The DWC pwm 2.13a version supports "Pulse Width Modulation with 0% and
> 100% Duty Cycle" by programming TIMER_0N100PWM_EN bit field. We also
> want to support this new hardware feature. So, adding a new property,
> like snps,timer-0n100pwm-en, in pwm/snps,dw-apb-timers-pwm2.yaml
> would be better?
>
> Krzysztof and Ben, do you think the above approach is reasonable and acceptable?
How any of this is related to the binding? We talk here about hardware
and binding, but you ask me about driver.... I don't care.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-09 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 9:04 [PATCH 0/2] Add driver support for ESWIN EIC7700 PWM controller dongxuyang
2025-12-05 9:04 ` [PATCH 1/2] dt-bindings: pwm: eswin: Add EIC7700 pwm controller dongxuyang
2025-12-08 6:45 ` Krzysztof Kozlowski
2025-12-09 10:20 ` Xuyang Dong
2025-12-09 21:40 ` Krzysztof Kozlowski [this message]
2025-12-05 9:05 ` [PATCH 2/2] pwm: eswin: Add EIC7700 pwm driver dongxuyang
2025-12-06 10:09 ` kernel test robot
2025-12-08 6:48 ` 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=502cc1eb-87a6-4574-903a-6181cd2258cc@kernel.org \
--to=krzk@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongxuyang@eswincomputing.com \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=ningyu@eswincomputing.com \
--cc=p.zabel@pengutronix.de \
--cc=pinkesh.vaghela@einfochips.com \
--cc=robh@kernel.org \
--cc=ukleinek@kernel.org \
--cc=wangguosheng@eswincomputing.com \
--cc=xuxiang@eswincomputing.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