From: Heiko Schocher <hs@denx.de>
To: linux-kernel@vger.kernel.org
Cc: Heiko Schocher <hs@denx.de>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: [PATCH v3 2/3] dt-bindings: pinctrl: sx150xq: allow gpio line naming
Date: Tue, 5 Nov 2024 07:42:05 +0100 [thread overview]
Message-ID: <20241105064206.43626-3-hs@denx.de> (raw)
In-Reply-To: <20241105064206.43626-1-hs@denx.de>
Adding gpio-line-names property works fine for this
device node, but dtb check drops warning:
'gpio-line-names' does not match any of the regexes: '-cfg$', 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/pinctrl/semtech,sx1501q.yaml#
Allow to add property gpio-line-names for this devices.
Signed-off-by: Heiko Schocher <hs@denx.de>
---
checkpatch shows
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
'gpio-line-names' does not match any of the regexes: '-cfg$', 'pinctrl-[0-9]+'
Ignored, as it is a make output, which helps to understand the
reason for adding this patch.
Changes in v3:
- worked in comments from Krzysztof
gpio-line-names should match the actual number of
gpios of the device.
Changes in v2:
patch dt-bindings: pinctrl: sx150xq: allow gpio line naming new in v2
.../bindings/pinctrl/semtech,sx1501q.yaml | 43 +++++++++++++++++++
1 file changed, 43 insertions(+)
diff --git a/Documentation/devicetree/bindings/pinctrl/semtech,sx1501q.yaml b/Documentation/devicetree/bindings/pinctrl/semtech,sx1501q.yaml
index 4214d7311f6b..39d7dad3313b 100644
--- a/Documentation/devicetree/bindings/pinctrl/semtech,sx1501q.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/semtech,sx1501q.yaml
@@ -26,6 +26,10 @@ properties:
reg:
maxItems: 1
+ gpio-line-names:
+ minItems: 5
+ maxItems: 17
+
interrupts:
maxItems: 1
@@ -87,6 +91,45 @@ required:
allOf:
- $ref: pinctrl.yaml#
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - semtech,sx1501q
+ - semtech,sx1504q
+ - semtech,sx1507q
+ then:
+ properties:
+ gpio-line-names:
+ minItems: 5
+ maxItems: 5
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - semtech,sx1502q
+ - semtech,sx1505q
+ - semtech,sx1508q
+ then:
+ properties:
+ gpio-line-names:
+ minItems: 9
+ maxItems: 9
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - semtech,sx1503q
+ - semtech,sx1506q
+ - semtech,sx1509q
+ then:
+ properties:
+ gpio-line-names:
+ minItems: 17
+ maxItems: 17
- if:
not:
properties:
--
2.20.1
next prev parent reply other threads:[~2024-11-05 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 6:42 [PATCH v3 0/3] arm64: dts: imx8mp: add support for the ABB SoM and carrier Heiko Schocher
2024-11-05 6:42 ` Heiko Schocher [this message]
2024-11-05 7:22 ` [PATCH v3 2/3] dt-bindings: pinctrl: sx150xq: allow gpio line naming Krzysztof Kozlowski
2024-11-08 9:09 ` Linus Walleij
2024-11-05 13:11 ` [PATCH v3 0/3] arm64: dts: imx8mp: add support for the ABB SoM and carrier Rob Herring (Arm)
2024-11-05 13:32 ` Heiko Schocher
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=20241105064206.43626-3-hs@denx.de \
--to=hs@denx.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).