From: Peter Geis <pgwipeout@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Peter Geis <pgwipeout@gmail.com>
Subject: [PATCH 1/9] dt-bindings: gpio: rockchip,gpio-bank: increase max clocks
Date: Wed, 28 Jul 2021 09:55:26 -0400 [thread overview]
Message-ID: <20210728135534.703028-2-pgwipeout@gmail.com> (raw)
In-Reply-To: <20210728135534.703028-1-pgwipeout@gmail.com>
The rk356x adds a debounce clock to the gpio devices.
Increase the maximum clocks to account for it.
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
---
Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml b/Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml
index d993e002cebe..489a5263a7a1 100644
--- a/Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml
+++ b/Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml
@@ -22,7 +22,7 @@ properties:
maxItems: 1
clocks:
- maxItems: 1
+ maxItems: 2
gpio-controller: true
--
2.25.1
next prev parent reply other threads:[~2021-07-28 13:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 13:55 [PATCH 0/9] fixes and enablement for rk356x Peter Geis
2021-07-28 13:55 ` Peter Geis [this message]
2021-07-28 14:10 ` [PATCH 1/9] dt-bindings: gpio: rockchip,gpio-bank: increase max clocks Heiko Stübner
2021-07-28 15:24 ` Peter Geis
2021-07-28 15:51 ` Rob Herring
2021-07-28 13:55 ` [PATCH 2/9] arm64: dts: rockchip: fix rk3568 mbi-alias Peter Geis
2021-07-28 13:55 ` [PATCH 3/9] arm64: dts: rockchip: add rk356x gpio debounce clocks Peter Geis
2021-07-28 13:55 ` [PATCH 4/9] arm64: dts: rockchip: add rk356x gmac1 node Peter Geis
2021-07-28 14:21 ` Heiko Stübner
2021-07-28 14:32 ` Peter Geis
2021-07-28 13:55 ` [PATCH 5/9] arm64: dts: rockchip: add rk3568 tsadc nodes Peter Geis
2021-07-28 14:46 ` Heiko Stübner
2021-07-28 15:14 ` Peter Geis
2021-07-28 15:31 ` Heiko Stübner
2021-07-28 15:33 ` Johan Jonker
2022-01-17 8:43 ` Piotr Oniszczuk
2022-01-17 13:49 ` Peter Geis
2022-01-17 14:13 ` Piotr Oniszczuk
2022-01-17 14:38 ` Peter Geis
2022-01-17 14:53 ` Piotr Oniszczuk
2021-07-28 13:55 ` [PATCH 6/9] arm64: dts: rockchip: add missing rk3568 cru phandles Peter Geis
2021-07-28 14:06 ` Heiko Stübner
2021-07-28 14:18 ` Peter Geis
2021-07-28 14:41 ` Heiko Stübner
2021-07-28 15:16 ` Peter Geis
2021-07-28 16:49 ` Peter Geis
2021-07-28 17:28 ` Heiko Stübner
2021-07-28 13:55 ` [PATCH 7/9] arm64: dts: rockchip: adjust rk3568 pll clocks Peter Geis
2021-07-28 14:08 ` Heiko Stübner
2021-07-28 14:24 ` Peter Geis
2021-07-28 13:55 ` [PATCH 8/9] arm64: dts: rockchip: enable gmac node on quartz64-a Peter Geis
2021-07-28 13:55 ` [PATCH 9/9] arm64: dts: rockchip: add thermal support to Quartz64 Model A Peter Geis
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=20210728135534.703028-2-pgwipeout@gmail.com \
--to=pgwipeout@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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).