From: Lorenzo Bianconi <lorenzo.bianconi@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-pci@vger.kernel.org, robh@kernel.org,
devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v5 1/5] dt-bindings: PCI: toshiba,tc9563: Document embedded GPIO controller
Date: Wed, 9 Sep 2026 17:38:20 +0200 [thread overview]
Message-ID: <aqF9bHTBBMmRhmn9@lore-desk> (raw)
In-Reply-To: <20260909150403.A5C511F00A3A@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2490 bytes --]
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Missing Required Properties for new GPIO provider capabilities
> --
>
> commit 384b355928f0212bcff0ab6c4447b15d28dc4109
> Author: Lorenzo Bianconi <lorenzo.bianconi@oss.qualcomm.com>
>
> dt-bindings: PCI: toshiba,tc9563: Document embedded GPIO controller
>
> This commit documents the embedded GPIO controller within the TC9563 PCIe
> switch. It exposes the controller by adding the gpio-controller and
> #gpio-cells properties to the switch node, and updates the example to
> demonstrate downstream ports utilizing these lines.
>
> > diff --git a/Documentation/devicetree/bindings/pci/toshiba,tc9563.yaml b/Documentation/devicetree/bindings/pci/toshiba,tc9563.yaml
> > index f084830c6d0cb..c4ebb99f50c37 100644
> > --- a/Documentation/devicetree/bindings/pci/toshiba,tc9563.yaml
> > +++ b/Documentation/devicetree/bindings/pci/toshiba,tc9563.yaml
> > @@ -31,6 +31,11 @@ properties:
> > description:
> > GPIO controlling the RESX# pin.
> >
> > + gpio-controller: true
> > +
> > + '#gpio-cells':
> > + const: 2
> > +
> > vdd18-supply: true
> >
> > vdd09-supply: true
>
> [Severity: Medium]
> Does this binding need to include the newly added GPIO provider capabilities
> in the required properties list?
In order to introduce any ABI change, we decided to not define 'gpio-controller'
and '#gpio-cells' properties as required.
Regards,
Lorenzo
>
> When hardware gains new provider capabilities, the subsystem guidelines
> stipulate that the corresponding standard properties (gpio-controller and
> #gpio-cells) must be added to the required properties list.
>
> Looking at the required properties block further down in this file:
>
> Documentation/devicetree/bindings/pci/toshiba,tc9563.yaml:
> required:
> - resx-gpios
> - vdd18-supply
> - vdd09-supply
> - vddc-supply
> - vddio1-supply
> - vddio2-supply
> - vddio18-supply
> - i2c-parent
>
> If gpio-controller and #gpio-cells are omitted from this list, device trees
> created with the pci1179,0623 compatible string but lacking these properties
> could silently pass dt_binding_check validation but fail at runtime when
> dependent subsystems attempt to use the GPIO functionality.
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260909-pci-tc9563-aux-v5-0-c9b33f56c8d3@oss.qualcomm.com?part=1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-09 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 14:55 [PATCH v5 0/5] PCI/pwrctrl: tc9563: Introduce support for embedded GPIO controller Lorenzo Bianconi
2026-09-09 14:55 ` [PATCH v5 1/5] dt-bindings: PCI: toshiba,tc9563: Document " Lorenzo Bianconi
2026-09-09 15:04 ` sashiko-bot
2026-09-09 15:38 ` Lorenzo Bianconi [this message]
2026-09-11 7:29 ` Krzysztof Kozlowski
2026-09-09 14:55 ` [PATCH v5 2/5] gpio: tc9563: Add support for the " Lorenzo Bianconi
2026-09-09 15:06 ` sashiko-bot
2026-09-09 14:55 ` [PATCH v5 3/5] PCI/pwrctrl: tc9563: Add GPIO auxiliary device support Lorenzo Bianconi
2026-09-09 15:15 ` sashiko-bot
2026-09-09 15:42 ` Lorenzo Bianconi
2026-09-09 14:55 ` [PATCH v5 4/5] PCI/pwrctrl: tc9563: Switch per-port reset to GPIO descriptor API Lorenzo Bianconi
2026-09-09 15:05 ` sashiko-bot
2026-09-09 14:55 ` [PATCH v5 5/5] arm64: dts: qcom: qcs6490-rb3gen2: Enable TC9563 embedded GPIO controller Lorenzo Bianconi
2026-09-09 15:05 ` 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=aqF9bHTBBMmRhmn9@lore-desk \
--to=lorenzo.bianconi@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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