From: Heiko Stuebner <heiko@sntech.de>
To: Xing Zheng <zhengxing@rock-chips.com>
Cc: dianders@google.com, linux-rockchip@lists.infradead.org,
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: Re: [PATCH v4 0/2] Add support rockchip,grf property for RK3399 PMU/GRU
Date: Fri, 13 Jan 2017 20:10:54 +0100 [thread overview]
Message-ID: <3210111.1N6x2AkRMx@phil> (raw)
In-Reply-To: <1484028930-20305-1-git-send-email-zhengxing@rock-chips.com>
Am Dienstag, 10. Januar 2017, 14:15:28 CET schrieb Xing Zheng:
> 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.
applied both for 4.11
binding-change is in my clock-branch (so that dt-binding doc changes stay
together) and the dts change is of course in the dts64 branch.
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] Add support rockchip, grf property for RK3399 PMU/GRU
Date: Fri, 13 Jan 2017 20:10:54 +0100 [thread overview]
Message-ID: <3210111.1N6x2AkRMx@phil> (raw)
In-Reply-To: <1484028930-20305-1-git-send-email-zhengxing@rock-chips.com>
Am Dienstag, 10. Januar 2017, 14:15:28 CET schrieb Xing Zheng:
> 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.
applied both for 4.11
binding-change is in my clock-branch (so that dt-binding doc changes stay
together) and the dts change is of course in the dts64 branch.
Thanks
Heiko
next prev parent reply other threads:[~2017-01-13 19:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 6:15 [PATCH v4 0/2] Add support rockchip,grf property for RK3399 PMU/GRU Xing Zheng
2017-01-10 6:15 ` Xing Zheng
[not found] ` <1484028930-20305-1-git-send-email-zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
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 6:15 ` Xing Zheng
2017-01-10 6:15 ` Xing Zheng
[not found] ` <1484028930-20305-2-git-send-email-zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-01-10 18:45 ` Doug Anderson
2017-01-10 18:45 ` Doug Anderson
2017-01-10 18:45 ` Doug Anderson
2017-01-10 19:46 ` Heiko Stübner
2017-01-10 19:46 ` Heiko Stübner
2017-01-10 19:46 ` Heiko Stübner
2017-01-10 19:58 ` Heiko Stübner
2017-01-10 19:58 ` Heiko Stübner
2017-01-10 19:58 ` Heiko Stübner
2017-01-12 0:50 ` Doug Anderson
2017-01-12 0:50 ` Doug Anderson
[not found] ` <CAD=FV=WMQ22G67YoQx2t7J6_ZuB3sUjVjXh-0KhPEO_6zbiyUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-12 1:28 ` Heiko Stuebner
2017-01-12 1:28 ` Heiko Stuebner
2017-01-12 1:28 ` Heiko Stuebner
[not found] ` <CAD=FV=Wwu3q_LqwYUWcJQRvp5neVOS9szgsYFONWTRJ0X8hRTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-11 1:04 ` Xing Zheng
2017-01-11 1:04 ` Xing Zheng
2017-01-11 1:04 ` Xing Zheng
[not found] ` <58758498.40309-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-01-11 1:12 ` Heiko Stuebner
2017-01-11 1:12 ` Heiko Stuebner
2017-01-11 1:12 ` Heiko Stuebner
2017-01-11 2:02 ` Xing Zheng
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 6:15 ` [PATCH v4 2/2] dt-bindings: clk: add rockchip, grf " Xing Zheng
2017-01-10 6:15 ` Xing Zheng
2017-01-10 18:34 ` [PATCH v4 2/2] dt-bindings: clk: add rockchip,grf " Doug Anderson
2017-01-10 18:34 ` [PATCH v4 2/2] dt-bindings: clk: add rockchip, grf " Doug Anderson
2017-01-10 18:34 ` Doug Anderson
2017-01-13 16:41 ` [PATCH v4 2/2] dt-bindings: clk: add rockchip,grf " Rob Herring
2017-01-13 16:41 ` Rob Herring
2017-01-13 16:41 ` Rob Herring
2017-01-13 19:10 ` Heiko Stuebner [this message]
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=3210111.1N6x2AkRMx@phil \
--to=heiko@sntech.de \
--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=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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.