From: "Xuyang Dong" <dongxuyang@eswincomputing.com>
To: sashiko-reviews@lists.linux.dev
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, pinkesh.vaghela@einfochips.com
Subject: Re: Re: [PATCH v10 1/3] dt-bindings: pwm: dwc: Document optional resets property
Date: Thu, 9 Jul 2026 09:19:47 +0800 (GMT+08:00) [thread overview]
Message-ID: <3a5ad21c.82a4.19f44759fe7.Coremail.dongxuyang@eswincomputing.com> (raw)
In-Reply-To: <20260703094313.8EF191F000E9@smtp.kernel.org>
>
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Missing matching updates for related bindings in the same IP family.
> --
>
> commit 05dd50c982c598b86944765d91f297a8c37b303e
> Author: Xuyang Dong <dongxuyang@eswincomputing.com>
>
> dt-bindings: pwm: dwc: Document optional resets property
>
> This commit updates the DesignWare PWM binding to document two active-low
> reset inputs: presetn and timer_N_resetn. It adds the resets property with
> two items to describe the function of each reset line.
>
> > diff --git a/Documentation/devicetree/bindings/pwm/snps,dw-apb-timers-pwm2.yaml b/Documentation/devicetree/bindings/pwm/snps,dw-apb-timers-pwm2.yaml
> > --- 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,11 @@ properties:
> > - const: bus
> > - const: timer
> >
> > + resets:
> > + items:
> > + - description: Interface bus (presetn) reset
> > + - description: PWM timer logic (timer_N_resetn) reset
> > +
>
> [Severity: Medium]
> The subsystem guidelines note that when a binding has multiple YAML files for
> different device types in the same family, related files may need matching
> updates. Since the DesignWare APB timer IP is described by both this PWM
> binding and the timer binding, does the timer binding also need an update?
>
> Currently, the timer binding restricts the resets property to a single item:
>
> Documentation/devicetree/bindings/timer/snps,dw-apb-timer.yaml:properties:resets
> resets:
> maxItems: 1
>
> Defining both hardware resets for the snps,dw-apb-timer compatible will
> cause dt_binding_check to fail due to this inconsistency.
>
Hi Sashiko,
Thanks for the careful review.
This is not a binding inconsistency issue:
- We're describing different hardware usage scenarios (PWM vs clocksource)
- The PWM binding describes what the PWM driver actually needs
- The timer binding describes what the timer driver actually needs
- Both reflect their respective hardware requirements accurately
I don't think the number of items in the resets property of the timer binding
should be updated. Do you think this is acceptable?
Best regards,
Xuyang Dong
> > snps,pwm-number:
> > $ref: /schemas/types.yaml#/definitions/uint32
> > description: The number of PWM channels configured for this instance
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260703093308.482-1-dongxuyang@eswincomputing.com?part=1
next prev parent reply other threads:[~2026-07-09 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 9:33 [PATCH v10 0/3] Update designware pwm driver dongxuyang
2026-07-03 9:33 ` [PATCH v10 1/3] dt-bindings: pwm: dwc: Document optional resets property Xuyang Dong
[not found] ` <20260703094313.8EF191F000E9@smtp.kernel.org>
2026-07-09 1:19 ` Xuyang Dong [this message]
2026-07-03 9:34 ` [PATCH v10 2/3] dt-bindings: pwm: dwc: Add eswin compatible Xuyang Dong
2026-07-03 9:34 ` [PATCH v10 3/3] pwm: dwc: add of/platform support dongxuyang
[not found] ` <20260703094710.723361F000E9@smtp.kernel.org>
2026-07-09 1:21 ` Xuyang Dong
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=3a5ad21c.82a4.19f44759fe7.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=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=sashiko-reviews@lists.linux.dev \
--cc=ukleinek@kernel.org \
/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