From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jianqun Xu <jay.xu@rock-chips.com>,
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
Subject: Re: [PATCH 1/2] dt-bindings: gpio: rockchip: add clock-names
Date: Thu, 8 Sep 2022 12:58:00 +0200 [thread overview]
Message-ID: <be1c2903-c2af-74b3-b34c-5f8ee4935fad@linaro.org> (raw)
In-Reply-To: <20220901013101.2634480-2-jay.xu@rock-chips.com>
On 01/09/2022 03:31, Jianqun Xu wrote:
> Add 'clock-names' to the gpio dt node. so the driver could get clocks by
> a const char id, this patch names the clock-names as
> - 'bus': the apb clock for cpu to access the gpio controller
> - 'db': the debounce clock for cpu to set debounce clock rate
>
> Since the old dt nodes may have no clock-names, this patch not make them
> as part of 'required properties'.
>
> Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com>
I see this patch sent three times... version your patches.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-08 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 1:30 [PATCH 0/2] gpio clock-names Jianqun Xu
2022-09-01 1:31 ` [PATCH 1/2] dt-bindings: gpio: rockchip: add clock-names Jianqun Xu
2022-09-08 10:58 ` Krzysztof Kozlowski [this message]
2022-09-01 1:31 ` [PATCH 2/2] arm64: dts: rockchip: rk356x add 'clock-names' for gpio nodes Jianqun Xu
-- strict thread matches above, loose matches on Subject: below --
2022-09-02 6:04 [PATCH 0/2] gpio clock-names Jianqun Xu
2022-09-02 6:04 ` [PATCH 1/2] dt-bindings: gpio: rockchip: add clock-names Jianqun Xu
2022-09-02 21:05 ` Rob Herring
2022-09-07 12:24 ` Krzysztof Kozlowski
2022-09-07 14:32 ` Heiko Stübner
2022-09-01 1:29 [PATCH 0/2] gpio clock-names Jianqun Xu
2022-09-01 1:29 ` [PATCH 1/2] dt-bindings: gpio: rockchip: add clock-names Jianqun Xu
2022-09-01 11:48 ` Rob Herring
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=be1c2903-c2af-74b3-b34c-5f8ee4935fad@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=heiko@sntech.de \
--cc=jay.xu@rock-chips.com \
--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;
as well as URLs for NNTP newsgroup(s).