From: Rob Herring <robh@kernel.org>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: knaerzche@gmail.com, strit@manjaro.org, mbrugger@suse.com,
zyw@rock-chips.com, zhangqing@rock-chips.com,
arnaud.ferraris@collabora.com, devicetree@vger.kernel.org,
Chris Morgan <macromorgan@hotmail.com>,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
lee.jones@linaro.org, heiko@sntech.de
Subject: Re: [PATCH 4/4 v5] dt-bindings: mfd: rk808: Convert bindings to yaml
Date: Thu, 3 Mar 2022 20:56:43 -0600 [thread overview]
Message-ID: <YiF/6zvlK6xkMZhd@robh.at.kernel.org> (raw)
In-Reply-To: <20220303203958.4904-5-macroalpha82@gmail.com>
On Thu, 03 Mar 2022 14:39:58 -0600, Chris Morgan wrote:
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Convert the rk808 bindings into yaml format. clock-output-names varies
> in maxItems depending on whether or not the clock-cells is 0 or 1. For
> the rk805, rk809, and rk817. This preserves behavior with the existing
> driver handling setting the clock for these specific PMICs. When this
> driver is corrected and the devicetrees updated this logic can be
> removed (since the rk805, rk808, and rk817 only have one actual clock).
>
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
> ---
> .../devicetree/bindings/mfd/rk808.txt | 465 ------------------
> .../bindings/mfd/rockchip,rk805.yaml | 219 +++++++++
> .../bindings/mfd/rockchip,rk808.yaml | 257 ++++++++++
> .../bindings/mfd/rockchip,rk809.yaml | 284 +++++++++++
> .../bindings/mfd/rockchip,rk817.yaml | 330 +++++++++++++
> .../bindings/mfd/rockchip,rk818.yaml | 282 +++++++++++
> 6 files changed, 1372 insertions(+), 465 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/mfd/rk808.txt
> create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk805.yaml
> create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk808.yaml
> create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk809.yaml
> create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk817.yaml
> create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk818.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-03-04 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 20:39 [PATCH 0/4 v5] rk808: Convert bindings to yaml Chris Morgan
2022-03-03 20:39 ` [PATCH 1/4 v5] arm64: dts: rockchip: Remove vcc13 and vcc14 for rk808 Chris Morgan
2022-03-03 20:39 ` [PATCH 2/4 v5] dts: rockchip: Add #clock-cells value for rk805 Chris Morgan
2022-03-03 20:39 ` [PATCH 3/4 v5] dts: rockchip: Update regulator name for PX3 Chris Morgan
2022-03-04 13:47 ` Robin Murphy
2022-03-03 20:39 ` [PATCH 4/4 v5] dt-bindings: mfd: rk808: Convert bindings to yaml Chris Morgan
2022-03-04 2:56 ` Rob Herring [this message]
2022-03-05 17:35 ` (subset) [PATCH 0/4 v5] " 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=YiF/6zvlK6xkMZhd@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=arnaud.ferraris@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=knaerzche@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=mbrugger@suse.com \
--cc=robh+dt@kernel.org \
--cc=strit@manjaro.org \
--cc=zhangqing@rock-chips.com \
--cc=zyw@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).