From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: "Pavel Machek" <pavel@ucw.cz>,
"Jan Kundrát" <jan.kundrat@cesnet.cz>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: [PATCH] schemas: gpio: Add trigger-source-cells
Date: Sat, 16 Sep 2023 18:52:30 +0200 [thread overview]
Message-ID: <20230916-gpio-triggers-v1-1-6e5052bead9a@linaro.org> (raw)
This adds trigger-source-cells to the GPIO schema,
and makes it depend on the GPIO controller also being
an interrupt controller.
This makes the most sense when reusing the
trigger-sources also for GPIO, driver bindings can
opt in by specifying the number of cells.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
dtschema/schemas/gpio/gpio.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/dtschema/schemas/gpio/gpio.yaml b/dtschema/schemas/gpio/gpio.yaml
index 87c381b2942b..0c3950d8789e 100644
--- a/dtschema/schemas/gpio/gpio.yaml
+++ b/dtschema/schemas/gpio/gpio.yaml
@@ -13,6 +13,7 @@ select: true
properties:
"#gpio-cells": true
+ "#trigger-source-cells": true
gpio-controller:
$ref: /schemas/types.yaml#/definitions/flag
gpio-line-names:
@@ -36,6 +37,7 @@ properties:
dependencies:
gpio-controller: ['#gpio-cells']
'#gpio-cells': [ gpio-controller ]
+ '#trigger-source-cells': [ interrupt-controller ]
gpio-line-names: ['#gpio-cells']
ngpios: ['#gpio-cells']
gpio-reserved-ranges: ['#gpio-cells']
---
base-commit: 033d0b1430e0670ddeb58f60fbff0ecefccaa925
change-id: 20230916-gpio-triggers-25ef26ddd711
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
reply other threads:[~2023-09-16 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230916-gpio-triggers-v1-1-6e5052bead9a@linaro.org \
--to=linus.walleij@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jan.kundrat@cesnet.cz \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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).