From: Rob Herring <robh@kernel.org>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: sboyd@kernel.org, kever.yang@rock-chips.com,
linux-arm-kernel@lists.infradead.org, mturquette@baylibre.com,
linux-rockchip@lists.infradead.org, heiko@sntech.de,
robh+dt@kernel.org, cl@rock-chips.com,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
finley.xiao@rock-chips.com, tony.xie@rock-chips.com,
huangtao@rock-chips.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] dt-binding: clock: Document rockchip, rk3568-cru bindings
Date: Mon, 8 Mar 2021 10:27:28 -0700 [thread overview]
Message-ID: <20210308172728.GA2663354@robh.at.kernel.org> (raw)
In-Reply-To: <20210301064749.10392-2-zhangqing@rock-chips.com>
On Mon, 01 Mar 2021 14:47:46 +0800, Elaine Zhang wrote:
> Document the device tree bindings of the rockchip Rk3568 SoC
> clock driver in Documentation/devicetree/bindings/clock/rockchip,rk3568-cru.yaml.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> ---
> .../bindings/clock/rockchip,rk3568-cru.yaml | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3568-cru.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-03-08 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 6:47 [PATCH v3 0/4] clk: rockchip: add clock controller for rk3568 Elaine Zhang
2021-03-01 6:47 ` [PATCH v3 1/4] dt-binding: clock: Document rockchip,rk3568-cru bindings Elaine Zhang
2021-03-05 1:41 ` Kever Yang
2021-03-08 17:27 ` Rob Herring [this message]
2021-03-01 6:47 ` [PATCH v3 2/4] clk: rockchip: add dt-binding header for rk3568 Elaine Zhang
2021-03-05 2:14 ` Kever Yang
2021-03-08 17:28 ` Rob Herring
2021-03-01 6:47 ` [PATCH v3 3/4] clk: rockchip: support more core div setting Elaine Zhang
2021-03-05 2:14 ` Kever Yang
2021-03-01 6:47 ` [PATCH v3 4/4] clk: rockchip: add clock controller for rk3568 Elaine Zhang
2021-03-05 2:14 ` Kever Yang
2021-03-13 22:25 ` Stephen Boyd
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=20210308172728.GA2663354@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--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=tony.xie@rock-chips.com \
--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).