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 1/2] dt-bindings: pwm: dwc: add reset optional
Date: Mon, 9 Mar 2026 17:23:45 +0800 (GMT+08:00) [thread overview]
Message-ID: <2d4f2cf9.3fe0.19cd1e8df20.Coremail.dongxuyang@eswincomputing.com> (raw)
In-Reply-To: <20260307-charming-shrewd-mantis-54bf9f@quoll>
> >
> > Add the optional resets property.
>
> Why?
>
Hi Krzysztof,
The DesignWare PWM controller provides separate reset signals dedicated
to each clock domain, as specified in the hardware documentation.
Without asserting and deasserting these resets during probe, the PWM
output may remain in an undefined state after system reboot.
Add optional reset control handling to ensure the controller is
properly initialized.
We will update the commit message in the next version.
Best regards,
Xuyang Dong
> >
> > Signed-off-by: Xuyang Dong <dongxuyang@eswincomputing.com>
>
> Best regards,
> Krzysztof
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 [this message]
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
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=2d4f2cf9.3fe0.19cd1e8df20.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