All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea della Porta <andrea.porta@suse.com>
To: sashiko-reviews@lists.linux.dev
Cc: Andrea della Porta <andrea.porta@suse.com>,
	conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org,
	ukleinek@kernel.org, Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v7 1/3] dt-bindings: pwm: Add Raspberry Pi RP1 PWM controller
Date: Fri, 24 Jul 2026 16:16:43 +0200	[thread overview]
Message-ID: <amNzy0jqWAvh-cBk@apocalypse> (raw)
In-Reply-To: <20260720095027.B76CC1F000E9@smtp.kernel.org>

Hi,

On 09:50 Mon 20 Jul     , sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The binding description states the device acts as a syscon provider for shared registers, but the schema prohibits the use of the "syscon" compatible string.
> --
> 
> --- Patch [1]: [PATCH v7 1/3] dt-bindings: pwm: Add Raspberry Pi RP1 PWM controller ---
> commit 06ebdbe78362ab02ea5e88d503ad7c179855b48a
> Author: Naushir Patuck <naush@raspberrypi.com>
> 
> dt-bindings: pwm: Add Raspberry Pi RP1 PWM controller
> 
> This commit adds the devicetree binding documentation for the PWM controller
> found in the Raspberry Pi RP1 chipset.
> 
> > diff --git a/Documentation/devicetree/bindings/pwm/raspberrypi,rp1-pwm.yaml b/Documentation/devicetree/bindings/pwm/raspberrypi,rp1-pwm.yaml
> > new file mode 100644
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/pwm/raspberrypi,rp1-pwm.yaml
> > @@ -0,0 +1,66 @@
> 
> [ ... ]
> 
> > +description: |
> > +  The PWM peripheral is a flexible waveform generator with a
> > +  variety of operational modes. It has the following features:
> > +   - four independent output channels
> > +   - 32-bit counter widths
> > +   - Seven output generation modes
> > +   - Optional per-channel output inversion
> > +   - Optional duty-cycle data FIFO with DMA support
> > +   - Optional sigma-delta noise shaping engine
> > +  Serves as a fan speed provider to other nodes for a PWM-connected
> > +  fan using shared registers (syscon).
> > +
> > +properties:
> > +  compatible:
> > +    const: raspberrypi,rp1-pwm
> 
> [Severity: Medium]
> The description states this device acts as a syscon provider for shared
> registers, but the compatible property is restricted to a single string.
> 
> Will device tree validation fail if a user includes the "syscon" string 
> normally required for standard kernel syscon lookup APIs alongside the
> "raspberrypi,rp1-pwm" compatible string?

I deliberately chose not to include 'syscon' in the 'compatible' property
to retain the flexibility to constrain the regmap exported through syscon
in the future.
Including 'syscon' in the producer's compatible string causes the syscon
framework to register the entire 'reg' property range, whereas the driver
uses of_syscon_register_regmap(), which could restrict the regmap later on.

Additionally, the fact that a specific register is used as a tachometer
depends solely on the firmware; if this changes in the future, the syscon
requirement might go away. Therefore, we might not want 'syscon' in the
compatible string at all.

Thanks,
Andrea

> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/cover.1784539788.git.andrea.porta@suse.com?part=1

  reply	other threads:[~2026-07-24 14:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  9:44 [PATCH v7 0/3] Add RP1 PWM controller support Andrea della Porta
2026-07-20  9:44 ` [PATCH v7 1/3] dt-bindings: pwm: Add Raspberry Pi RP1 PWM controller Andrea della Porta
2026-07-20  9:50   ` sashiko-bot
2026-07-24 14:16     ` Andrea della Porta [this message]
2026-07-20  9:44 ` [PATCH v7 2/3] pwm: rp1: Add RP1 PWM controller driver Andrea della Porta
2026-07-20 10:02   ` sashiko-bot
2026-07-24 15:04     ` Andrea della Porta
2026-07-20  9:44 ` [PATCH v7 3/3] arm64: dts: broadcom: rpi-5: Add RP1 PWM node Andrea della Porta

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=amNzy0jqWAvh-cBk@apocalypse \
    --to=andrea.porta@suse.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.