From: Rosen Penev <rosenp@gmail.com>
To: devicetree@vger.kernel.org
Cc: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org (open list:GPIO SUBSYSTEM),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v2] dt-bindings: gpio: pca95xx: add onnn,pca9655 compatible
Date: Sun, 4 Oct 2026 12:10:42 -0700 [thread overview]
Message-ID: <20261004191042.143713-1-rosenp@gmail.com> (raw)
The pca9655 is the On Semi variant of the pca9555 16-bit I2C GPIO
expander. "onnn,pca9655" is already used standalone by in-tree DTS
(armada-388-clearfog, armada-388-helios4) and has a dedicated entry in
the pca953x driver's OF match table, but was never documented, causing
dtbs_check failures.
Document it alongside the other standalone entries such as
onnn,pca9654, without an nxp,pca9555 fallback, so that the existing
DTS remain valid.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202610021617.AlVUa9No-lkp@intel.com/
Assisted-by: LLM
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
v2: rewrite description. Use tags from kernel test bot.
Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml b/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
index 4631388a7d91..563f61e6e543 100644
--- a/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
+++ b/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
@@ -67,6 +67,7 @@ properties:
- nxp,pcal9555a
- onnn,cat9554
- onnn,pca9654
+ - onnn,pca9655
- ti,pca6107
- ti,pca9536
- ti,tca6408
--
2.56.0
next reply other threads:[~2026-10-04 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 19:10 Rosen Penev [this message]
2026-10-04 19:17 ` [PATCH v2] dt-bindings: gpio: pca95xx: add onnn,pca9655 compatible sashiko-bot
2026-10-04 19:21 ` Rosen Penev
2026-10-09 7:26 ` Krzysztof Kozlowski
2026-10-09 20:47 ` Igor Velkov
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=20261004191042.143713-1-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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.