From: sashiko-bot@kernel.org
To: "Lorenzo Bianconi" <lorenzo.bianconi@oss.qualcomm.com>
Cc: robh@kernel.org, linux-pci@vger.kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/5] dt-bindings: PCI: toshiba,tc9563: Document embedded GPIO controller
Date: Fri, 04 Sep 2026 17:21:13 +0000 [thread overview]
Message-ID: <20260904172114.2CF8F1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260904-pci-tc9563-aux-v3-1-5b1449d62ba2@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The 'gpio-controller' and '#gpio-cells' properties were added to the binding to document GPIO provider capabilities, but were not added to the 'required' list.
--
commit 167159eda5a6932cbffa6730117f8dd7e23b2970
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 adds gpio-controller and #gpio-cells properties to the device
tree binding, along with the reset-gpios property for the downstream port.
> diff --git a/Documentation/devicetree/bindings/pci/toshiba,tc9563.yaml b/Documentation/devicetree/bindings/pci/toshiba,tc9563.yaml
> index f084830c6d0cb..c4cd162cb084b 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
> +
[Severity: Medium]
Should gpio-controller and #gpio-cells be added to the required list?
Looking at the required list in
Documentation/devicetree/bindings/pci/toshiba,tc9563.yaml around line 108,
these newly added GPIO provider capabilities are missing:
required:
- resx-gpios
- vdd18-supply
- vdd09-supply
- vddc-supply
Without being added to the required list, device trees with incomplete
configurations (missing the newly added GPIO controller properties) will
silently pass schema validation when running dt_binding_check or dtbs_check.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260904-pci-tc9563-aux-v3-0-5b1449d62ba2@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-09-04 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 17:15 [PATCH v3 0/5] PCI/pwrctrl: tc9563: introduce support for embedded GPIO controller Lorenzo Bianconi
2026-09-04 17:15 ` [PATCH v3 1/5] dt-bindings: PCI: toshiba,tc9563: Document " Lorenzo Bianconi
2026-09-04 17:21 ` sashiko-bot [this message]
2026-09-04 18:32 ` Lorenzo Bianconi
2026-09-04 17:15 ` [PATCH v3 2/5] gpio: tc9563: Add support for the " Lorenzo Bianconi
2026-09-04 17:23 ` sashiko-bot
2026-09-04 17:15 ` [PATCH v3 3/5] PCI/pwrctrl: tc9563: Add GPIO auxiliary device support Lorenzo Bianconi
2026-09-04 17:34 ` sashiko-bot
2026-09-04 19:25 ` Lorenzo Bianconi
2026-09-04 17:15 ` [PATCH v3 4/5] PCI/pwrctrl: tc9563: Switch per-port reset to GPIO descriptor API Lorenzo Bianconi
2026-09-04 17:32 ` sashiko-bot
2026-09-04 17:15 ` [PATCH v3 5/5] arm64: dts: qcom: qcs6490-rb3gen2: Enable TC9563 embedded GPIO controller Lorenzo Bianconi
2026-09-04 17:23 ` 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=20260904172114.2CF8F1F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.bianconi@oss.qualcomm.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