From: sashiko-bot@kernel.org
To: dongxuyang@eswincomputing.com
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v13 1/5] dt-bindings: pwm: dwc: Document optional resets property
Date: Fri, 24 Jul 2026 08:53:45 +0000 [thread overview]
Message-ID: <20260724085345.E530D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260724084304.1531-1-dongxuyang@eswincomputing.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The timer binding for the same hardware family (`timer/snps,dw-apb-timer.yaml`) was not updated to reflect the newly documented reset lines.
--
--- Patch [1]: [PATCH v13 1/5] dt-bindings: pwm: dwc: Document optional resets property ---
commit 1c2d313919493838e6334a2a8bbd90732e217da2
Author: Xuyang Dong <dongxuyang@eswincomputing.com>
dt-bindings: pwm: dwc: Document optional resets property
This commit adds the resets and reset-names properties to the DesignWare PWM
IP binding. It documents the active-low presetn and timer_N_resetn inputs for
the bus and timer domains respectively.
> diff --git a/Documentation/devicetree/bindings/pwm/snps,dw-apb-timers-pwm2.yaml b/Documentation/devicetree/bindings/pwm/snps,dw-apb-timers-pwm2.yaml
> index 7523a89a17733..1f9d72f9f3590 100644
> --- a/Documentation/devicetree/bindings/pwm/snps,dw-apb-timers-pwm2.yaml
> +++ b/Documentation/devicetree/bindings/pwm/snps,dw-apb-timers-pwm2.yaml
> @@ -43,6 +43,16 @@ properties:
> - const: bus
> - const: timer
>
> + resets:
> + items:
> + - description: Interface bus (presetn) reset
> + - description: PWM timer logic (timer_N_resetn) reset
> +
> + reset-names:
> + items:
> + - const: bus
> + - const: timer
[Severity: Medium]
Should the standard timer binding for this exact same hardware module also
be updated to reflect these two newly documented reset lines?
The timer binding for the same hardware family currently only specifies
a single reset:
Documentation/devicetree/bindings/timer/snps,dw-apb-timer.yaml:
resets:
maxItems: 1
If a device tree author adds the second reset line to a timer node
representing this IP, will it incorrectly fail schema validation against
snps,dw-apb-timer.yaml since that file lacks reset-names and caps maxItems
at 1?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260724084153.1473-1-dongxuyang@eswincomputing.com?part=1
next prev parent reply other threads:[~2026-07-24 8:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 8:41 [PATCH v13 0/5] Update designware pwm driver dongxuyang
2026-07-24 8:43 ` [PATCH v13 1/5] dt-bindings: pwm: dwc: Document optional resets property dongxuyang
2026-07-24 8:53 ` sashiko-bot [this message]
2026-07-24 8:43 ` [PATCH v13 2/5] dt-bindings: pwm: dwc: Add eswin compatible dongxuyang
2026-07-24 8:56 ` sashiko-bot
2026-07-24 8:43 ` [PATCH v13 3/5] pwm: dwc: add of/platform support dongxuyang
2026-07-24 8:57 ` sashiko-bot
2026-07-24 8:44 ` [PATCH v13 4/5] dt-bindings: timer: dwc: Update resets property items dongxuyang
2026-07-24 8:55 ` sashiko-bot
2026-07-24 8:44 ` [PATCH v13 5/5] clocksource: dw_apb_timer: Use reset array API to handle all resets dongxuyang
2026-07-24 8:55 ` 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=20260724085345.E530D1F000E9@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