From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: santosh.shilimkar@ti.com
Cc: galak@codeaurora.org, linux@arm.linux.org.uk,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
grygorii.strashko@ti.com, m-karicheri2@ti.com
Subject: Re: [Patch] ARM: dts: keystone: add pll controller syscon entry
Date: Wed, 21 May 2014 17:56:25 +0300 [thread overview]
Message-ID: <537CBE99.9090800@ti.com> (raw)
In-Reply-To: <1400681875-24432-1-git-send-email-ivan.khoronzhuk@ti.com>
Ignore this. It'll be included in "Introduce keystone reset driver"
patch series
On 05/21/2014 05:17 PM, Ivan Khoronzhuk wrote:
> The pll controller register set includes sets of registers with
> different purposes, so it's logically to add syscon entry to be able
> to access them from appropriate places.
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> ---
>
> Based on linux-next/master
>
> arch/arm/boot/dts/keystone.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/keystone.dtsi b/arch/arm/boot/dts/keystone.dtsi
> index d9f99e7..5e67c5b 100644
> --- a/arch/arm/boot/dts/keystone.dtsi
> +++ b/arch/arm/boot/dts/keystone.dtsi
> @@ -66,6 +66,11 @@
> ranges = <0x0 0x0 0x0 0xc0000000>;
> dma-ranges = <0x80000000 0x8 0x00000000 0x80000000>;
>
> + pllctrl: pll_controller {
> + compatible = "ti,keystone-pllctrl", "syscon";
> + reg = <0x2310000 0x200>;
> + };
> +
> rstctrl: reset-controller {
> compatible = "ti,keystone-reset";
> reg = <0x023100e8 4>; /* pll reset control reg */
--
Regards,
Ivan Khoronzhuk
next prev parent reply other threads:[~2014-05-21 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 14:17 [Patch] ARM: dts: keystone: add pll controller syscon entry Ivan Khoronzhuk
2014-05-21 14:56 ` Ivan Khoronzhuk [this message]
2014-05-21 18:18 ` Sergei Shtylyov
[not found] ` <537CEE13.5040908-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-05-21 18:22 ` Sergei Shtylyov
[not found] ` <537CEEFA.8080805-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-05-22 13:51 ` Ivan Khoronzhuk
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=537CBE99.9090800@ti.com \
--to=ivan.khoronzhuk@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m-karicheri2@ti.com \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.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).