From: "Xuyang Dong" <dongxuyang@eswincomputing.com>
To: "Krzysztof Kozlowski" <krzk@kernel.org>
Cc: ukleinek@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, ben-linux@fluff.org,
ben.dooks@codethink.co.uk, 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: Re: [PATCH v2 0/2] Update designware pwm driver
Date: Mon, 9 Mar 2026 17:24:02 +0800 (GMT+08:00) [thread overview]
Message-ID: <7e73ec54.3fe1.19cd1e922bc.Coremail.dongxuyang@eswincomputing.com> (raw)
In-Reply-To: <a88fa91a-20e8-4391-824b-8e16c910430d@kernel.org>
Hi Krzysztof,
> >>
> >> There is already a patch [1] for the DesignWare PWM driver,
> >
> > So provide review there instead of allowing Ben to post incomplete
> > hardware description which you want to correct here...
> >
> > I don't understand why posting this change.
>
> I see now Ben did not post the bindings change, so this message here
> just confused me.
We noticed Ben’s DesignWare PWM driver series on lore [1]. The patches for
the DT bindings, pwm-dwc.c and pwm-dwc-core.c have already been merged into
the kernel, for example, patches 1/6, 2/6, and 3/6.
However, the pwm-dwc-of.c patch has not yet been accepted, for example,
patches 4/6, 5/6, and 6/6.
We discussed the status of this PWM series with Ben on lore. Given the lack
of recent updates following Ben’s message in [2], we’d like to step in and
help move this forward.
This series is based on v9 and includes the following updates:
1. Migrated to the latest PWM subsystem structure and APIs.
2. Added support for 0% and 100% duty cycle modes.
3. Implemented basic power management (runtime PM) support.
The previous series (v1) has been deprecated. Would it be more
appropriate to send this as v2 rather than v10?
[1] https://lore.kernel.org/lkml/20230907161242.67190-1-ben.dooks@codethink.co.uk/
[2] https://lore.kernel.org/lkml/0bdd6ab6-bfdd-400e-99b6-cfb186dfcc3e@codethink.co.uk/
The binding file 'snps,dw-apb-timers-pwm2.yaml' has already been merged,
but the current driver lacks reset support.
Therefore, patch 1 adds an optional reset property to address this.
We will update the commit message in the next version.
> >
> >
> >
> >> which is posted by Ben and still under review.
> >> Based on this patch, this series is a continuation of [1]
> >> to add support for IP versions 2.11a and later, which
> >> includes support for "Pulse Width Modulation with 0%
> >> and 100% Duty Cycle".
>
> But does this mean the patchset cannot be even tested?
Support for 0% and 100% duty cycle mode (available in DesignWare PWM IP
version 2.11a and later) has been tested on the EIC7700 SoC, which
integrates IP version 2.13a.
For Ben's implementation, which does not support this mode, testing can
still be done by setting dwc->features to 0 after reading the version
register, effectively disabling 0% and 100% duty cycle support.
Regards,
Xuyang Dong
next prev parent reply other threads:[~2026-03-09 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 9:30 [PATCH v2 0/2] Update designware pwm driver dongxuyang
2026-03-06 9:30 ` [PATCH v2 1/2] dt-bindings: pwm: dwc: add reset optional dongxuyang
2026-03-07 13:22 ` Krzysztof Kozlowski
2026-03-09 9:23 ` Xuyang Dong
2026-03-17 9:42 ` Uwe Kleine-König
2026-03-06 9:31 ` [PATCH v2 2/2] pwm: dwc: add of/platform support dongxuyang
2026-03-07 13:24 ` [PATCH v2 0/2] Update designware pwm driver Krzysztof Kozlowski
2026-03-07 13:26 ` Krzysztof Kozlowski
2026-03-09 9:24 ` Xuyang Dong [this message]
2026-03-17 13:50 ` Ben Dooks
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=7e73ec54.3fe1.19cd1e922bc.Coremail.dongxuyang@eswincomputing.com \
--to=dongxuyang@eswincomputing.com \
--cc=ben-linux@fluff.org \
--cc=ben.dooks@codethink.co.uk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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