From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Johan Jonker <jbx6244@gmail.com>,
heiko@sntech.de, zhangqing@rock-chips.com
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: clock: convert rockchip,rk3036-cru.txt to YAML
Date: Wed, 30 Mar 2022 19:28:20 +0200 [thread overview]
Message-ID: <faee52b3-6d43-dfe0-500d-2fae70fe2fd9@linaro.org> (raw)
In-Reply-To: <20220330114847.18633-1-jbx6244@gmail.com>
On 30/03/2022 13:48, Johan Jonker wrote:
> Convert rockchip,rk3036-cru.txt to YAML.
>
> Changes against original bindings:
> Add clocks and clock-names because the device has to have
> at least one input clock.
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
> .../bindings/clock/rockchip,rk3036-cru.txt | 56 ---------------
> .../bindings/clock/rockchip,rk3036-cru.yaml | 72 +++++++++++++++++++
> 2 files changed, 72 insertions(+), 56 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3036-cru.txt
> create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3036-cru.yaml
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-30 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 11:48 [PATCH v1 1/3] dt-bindings: clock: convert rockchip,rk3036-cru.txt to YAML Johan Jonker
2022-03-30 11:48 ` [PATCH v1 2/3] ARM: dts: rockchip: add clocks property to cru node rk3036 Johan Jonker
2022-03-30 11:48 ` [PATCH v1 3/3] ARM: dts: rockchip: rk3036: use generic node name for dma Johan Jonker
2022-03-30 17:29 ` Krzysztof Kozlowski
2022-03-30 17:28 ` Krzysztof Kozlowski [this message]
2022-05-17 19:11 ` [PATCH v1 1/3] dt-bindings: clock: convert rockchip,rk3036-cru.txt to YAML Heiko Stuebner
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=faee52b3-6d43-dfe0-500d-2fae70fe2fd9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=zhangqing@rock-chips.com \
/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).