From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel@collabora.com,
Xing Zheng <zhengxing@rock-chips.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Elaine Zhang <zhangqing@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Michael Turquette <mturquette@baylibre.com>,
linux-rockchip@lists.infradead.org,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: clk: Convert rockchip,rk3399-cru to DT schema
Date: Mon, 19 Jul 2021 16:51:15 -0300 [thread overview]
Message-ID: <20210719195115.cgh7fh54kwloo4o7@notapiano> (raw)
In-Reply-To: <20210624190041.GA1812802@robh.at.kernel.org>
On Thu, Jun 24, 2021 at 01:00:41PM -0600, Rob Herring wrote:
> On Thu, 10 Jun 2021 14:56:13 -0300, Nícolas F. R. A. Prado wrote:
> > Convert the rockchip,rk3399-cru binding to DT schema format.
> > Tested with
> > ARCH=arm64 make dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.yaml
> > ARCH=arm64 make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.yaml
> >
> > Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> > ---
> >
> > One caveat is that this node expects certain external clocks, mainly 'xin24m'.
> >
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Thanks! Is this blocked on something else?
Thanks,
Nícolas
next prev parent reply other threads:[~2021-07-19 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 17:56 [PATCH] dt-bindings: clk: Convert rockchip,rk3399-cru to DT schema Nícolas F. R. A. Prado
2021-06-24 19:00 ` Rob Herring
2021-07-19 19:51 ` Nícolas F. R. A. Prado [this message]
2021-07-19 20:12 ` Rob Herring
2021-07-19 20:20 ` Heiko Stübner
2021-07-23 12:02 ` 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=20210719195115.cgh7fh54kwloo4o7@notapiano \
--to=nfraprado@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.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=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=zhangqing@rock-chips.com \
--cc=zhengxing@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).