From: Xing Zheng <zhengxing@rock-chips.com>
To: heiko@sntech.de
Cc: dianders@google.com, linux-rockchip@lists.infradead.org,
Xing Zheng <zhengxing@rock-chips.com>,
Douglas Anderson <dianders@chromium.org>,
David Wu <david.wu@rock-chips.com>,
Jianqun Xu <jay.xu@rock-chips.com>,
devicetree@vger.kernel.org, Stephen Boyd <sboyd@codeaurora.org>,
Elaine Zhang <zhangqing@rock-chips.com>,
Brian Norris <briannorris@chromium.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Shawn Lin <shawn.lin@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Caesar Wang <wxt@rock-chips.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] Add support rockchip,grf property for RK3399 PMU/GRU
Date: Tue, 10 Jan 2017 14:15:28 +0800 [thread overview]
Message-ID: <1484028930-20305-1-git-send-email-zhengxing@rock-chips.com> (raw)
Hi,
The structure rockchip_clk_provider needs to refer the GRF regmap
in somewhere, if the CRU node has not "rockchip,grf" property,
calling syscon_regmap_lookup_by_phandle will return an invalid GRF
regmap, and the MUXGRF type clock will be not supported.
Therefore, we need to add them.
Thanks.
Changes in v4:
- separte the binding patch
- update the decription for rockchip,grf property
Changes in v3:
- add optional roperty rockchip,grf in rockchip,rk3399-cru.txt
Changes in v2:
- referring pmugrf for PMUGRU
- fix the typo "invaild" in COMMIT message
Xing Zheng (2):
arm64: dts: rockchip: add "rockchip, grf" property for RK3399
PMUCRU/CRU
dt-bindings: clk: add rockchip,grf property for RK3399
Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt | 6 ++++++
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 2 ++
2 files changed, 8 insertions(+)
--
2.7.4
next reply other threads:[~2017-01-10 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 6:15 Xing Zheng [this message]
2017-01-10 6:15 ` [PATCH v4 1/2] arm64: dts: rockchip: add "rockchip, grf" property for RK3399 PMUCRU/CRU Xing Zheng
2017-01-10 18:45 ` Doug Anderson
2017-01-10 19:46 ` Heiko Stübner
2017-01-10 19:58 ` Heiko Stübner
2017-01-12 0:50 ` Doug Anderson
2017-01-12 1:28 ` Heiko Stuebner
2017-01-11 1:04 ` Xing Zheng
2017-01-11 1:12 ` Heiko Stuebner
2017-01-11 2:02 ` Xing Zheng
2017-01-10 6:15 ` [PATCH v4 2/2] dt-bindings: clk: add rockchip,grf property for RK3399 Xing Zheng
2017-01-10 18:34 ` Doug Anderson
2017-01-13 16:41 ` Rob Herring
2017-01-13 19:10 ` [PATCH v4 0/2] Add support rockchip,grf property for RK3399 PMU/GRU 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=1484028930-20305-1-git-send-email-zhengxing@rock-chips.com \
--to=zhengxing@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dianders@google.com \
--cc=heiko@sntech.de \
--cc=jay.xu@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=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shawn.lin@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=wxt@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).