From: sashiko-bot@kernel.org
To: dongxuyang@eswincomputing.com
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v14 3/5] pwm: dwc: add of/platform support
Date: Thu, 30 Jul 2026 11:39:29 +0000 [thread overview]
Message-ID: <20260730113930.8FC151F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260730111553.1886-1-dongxuyang@eswincomputing.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dwc_pwm_runtime_resume() writes the EN bit and timer configuration simultaneously, violating the hardware specification.
--
--- Patch [3]: [PATCH v14 3/5] pwm: dwc: add of/platform support ---
commit b441231de2fcc89e4187b672bde1919622ac7347
Author: Xuyang Dong <dongxuyang@eswincomputing.com>
pwm: dwc: add of/platform support
This commit adds platform and OF device tree support for the DesignWare PWM
controller, enabling its use in non-PCI systems. It also implements polarity
control using dual load registers and adds runtime PM callbacks to save and
restore hardware state.
> diff --git a/drivers/pwm/pwm-dwc-of.c b/drivers/pwm/pwm-dwc-of.c
> new file mode 100644
> index 0000000000000..e96e5569eb81e
> --- /dev/null
> +++ b/drivers/pwm/pwm-dwc-of.c
[ ... ]
> +static int dwc_pwm_runtime_resume(struct device *dev)
> +{
[ ... ]
> + for (idx = 0; idx < chip->npwm; idx++) {
> + dwc_pwm_writel(dwc, dwc->ctx[idx].cnt, DWC_TIM_LD_CNT(idx));
> + dwc_pwm_writel(dwc, dwc->ctx[idx].cnt2, DWC_TIM_LD_CNT2(idx));
> + dwc_pwm_writel(dwc, dwc->ctx[idx].ctrl, DWC_TIM_CTRL(idx));
[Severity: Medium]
Does writing the saved control register directly in dwc_pwm_runtime_resume()
violate the hardware initialization sequence?
The driver notes in __dwc_pwm_configure_timer() that the specification
requires disabling the timer, programming it, and then enabling it.
Since ctx[idx].ctrl may have the DWC_TIM_CTRL_EN bit set from when the device
was active, does this single write attempt to configure and enable the timer
simultaneously? Could this cause unpredictable behavior upon resume?
> + }
> +
> + return 0;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260730111425.1680-1-dongxuyang@eswincomputing.com?part=3
next prev parent reply other threads:[~2026-07-30 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 11:14 [PATCH v14 0/5] Update designware pwm driver dongxuyang
2026-07-30 11:15 ` [PATCH v14 1/5] dt-bindings: pwm: dwc: Document optional resets property dongxuyang
2026-07-30 11:15 ` [PATCH v14 2/5] dt-bindings: pwm: dwc: Add eswin compatible dongxuyang
2026-07-30 11:29 ` sashiko-bot
2026-07-30 11:15 ` [PATCH v14 3/5] pwm: dwc: add of/platform support dongxuyang
2026-07-30 11:39 ` sashiko-bot [this message]
2026-07-30 11:16 ` [PATCH v14 4/5] dt-bindings: timer: dwc: Update resets property items dongxuyang
2026-07-30 11:16 ` [PATCH v14 5/5] clocksource: dw_apb_timer: Use reset array API to handle all resets dongxuyang
2026-07-30 11:52 ` sashiko-bot
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=20260730113930.8FC151F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongxuyang@eswincomputing.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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