From: Jianqun Xu <jay.xu@rock-chips.com>
To: linus.walleij@linaro.org, heiko@sntech.de
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-gpio@vger.kernel.org, linux-rockchip@lists.infradead.org,
Jianqun Xu <jay.xu@rock-chips.com>
Subject: [PATCH 0/2] gpio clock-names
Date: Thu, 1 Sep 2022 09:29:39 +0800 [thread overview]
Message-ID: <20220901012944.2634398-1-jay.xu@rock-chips.com> (raw)
Add 'clock-names' for gpio dt nodes.
Jianqun Xu (2):
dt-bindings: gpio: rockchip: add clock-names
arm64: dts: rockchip: rk356x add 'clock-names' for gpio nodes
.../devicetree/bindings/gpio/rockchip,gpio-bank.yaml | 6 ++++++
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 5 +++++
2 files changed, 11 insertions(+)
--
2.25.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2022-09-01 1:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 1:29 Jianqun Xu [this message]
2022-09-01 1:29 ` [PATCH 1/2] dt-bindings: gpio: rockchip: add clock-names Jianqun Xu
2022-09-01 11:48 ` Rob Herring
2022-09-02 0:48 ` jay.xu
2022-09-01 1:29 ` [PATCH v1 1/3] gpio: rockchip: make gpio work without cru module Jianqun Xu
2022-09-02 18:38 ` Peter Geis
2022-09-02 21:09 ` Heiko Stübner
2022-09-01 1:29 ` [PATCH 2/2] arm64: dts: rockchip: rk356x add 'clock-names' for gpio nodes Jianqun Xu
2022-09-01 1:29 ` [PATCH 2/3] gpio: rockchip: get pinctrl node from 'gpio-ranges' property Jianqun Xu
2022-09-01 1:29 ` [PATCH 3/3] dt-bindings: gpio: rockchip,gpio add optional 'gpio-ranges' Jianqun Xu
2022-09-01 13:32 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2022-09-01 1:30 [PATCH 0/2] gpio clock-names Jianqun Xu
2022-09-02 6:04 Jianqun Xu
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=20220901012944.2634398-1-jay.xu@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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