All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Sekhar Nori <nsekhar@ti.com>, Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <bcousson@baylibre.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Device Tree Mailing List <devicetree@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: AM4372: clk: efuse based crystal frequency detect
Date: Fri, 23 May 2014 14:05:57 +0300	[thread overview]
Message-ID: <537F2B95.1010808@ti.com> (raw)
In-Reply-To: <062e8a534b1e372db7ed3daa3df7e3c5b885ffab.1400062517.git.nsekhar@ti.com>

On 05/14/2014 02:36 PM, Sekhar Nori wrote:
> From: Afzal Mohammed <afzal@ti.com>
>
> Currently oscillator frequency is determined based on sysboot settings,
> it may not be the case always. To determine it properly, efuse settings
> also has to be read. CONTROL_STATUS register holds this information.
> Bit 31:	if 0, frequency to be determined based on sysboot
> 	if 1, frequency to be determined based on efuse
> Bit 29,30 - for efuse detection of frequency
> Bit 22,23 - for sysboot detection of frequency
>
> Add clock nodes (mux) to determine oscillator frequency as above.
>
> Signed-off-by: Afzal Mohammed <afzal@ti.com>
> Acked-by: Tero Kristo <t-kristo@ti.com>
> Signed-off-by: Sekhar Nori <nsekhar@ti.com>

Thanks, queued for 3.16.

-Tero

> ---
>   arch/arm/boot/dts/am43xx-clocks.dtsi |   16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am43xx-clocks.dtsi b/arch/arm/boot/dts/am43xx-clocks.dtsi
> index 142009c..71b029c 100644
> --- a/arch/arm/boot/dts/am43xx-clocks.dtsi
> +++ b/arch/arm/boot/dts/am43xx-clocks.dtsi
> @@ -11,6 +11,22 @@
>   	sys_clkin_ck: sys_clkin_ck {
>   		#clock-cells = <0>;
>   		compatible = "ti,mux-clock";
> +		clocks = <&sysboot_freq_sel_ck>, <&crystal_freq_sel_ck>;
> +		ti,bit-shift = <31>;
> +		reg = <0x0040>;
> +	};
> +
> +	crystal_freq_sel_ck: crystal_freq_sel_ck {
> +		#clock-cells = <0>;
> +		compatible = "ti,mux-clock";
> +		clocks = <&virt_19200000_ck>, <&virt_24000000_ck>, <&virt_25000000_ck>, <&virt_26000000_ck>;
> +		ti,bit-shift = <29>;
> +		reg = <0x0040>;
> +	};
> +
> +	sysboot_freq_sel_ck: sysboot_freq_sel_ck@44e10040 {
> +		#clock-cells = <0>;
> +		compatible = "ti,mux-clock";
>   		clocks = <&virt_19200000_ck>, <&virt_24000000_ck>, <&virt_25000000_ck>, <&virt_26000000_ck>;
>   		ti,bit-shift = <22>;
>   		reg = <0x0040>;
>


WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: AM4372: clk: efuse based crystal frequency detect
Date: Fri, 23 May 2014 14:05:57 +0300	[thread overview]
Message-ID: <537F2B95.1010808@ti.com> (raw)
In-Reply-To: <062e8a534b1e372db7ed3daa3df7e3c5b885ffab.1400062517.git.nsekhar@ti.com>

On 05/14/2014 02:36 PM, Sekhar Nori wrote:
> From: Afzal Mohammed <afzal@ti.com>
>
> Currently oscillator frequency is determined based on sysboot settings,
> it may not be the case always. To determine it properly, efuse settings
> also has to be read. CONTROL_STATUS register holds this information.
> Bit 31:	if 0, frequency to be determined based on sysboot
> 	if 1, frequency to be determined based on efuse
> Bit 29,30 - for efuse detection of frequency
> Bit 22,23 - for sysboot detection of frequency
>
> Add clock nodes (mux) to determine oscillator frequency as above.
>
> Signed-off-by: Afzal Mohammed <afzal@ti.com>
> Acked-by: Tero Kristo <t-kristo@ti.com>
> Signed-off-by: Sekhar Nori <nsekhar@ti.com>

Thanks, queued for 3.16.

-Tero

> ---
>   arch/arm/boot/dts/am43xx-clocks.dtsi |   16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am43xx-clocks.dtsi b/arch/arm/boot/dts/am43xx-clocks.dtsi
> index 142009c..71b029c 100644
> --- a/arch/arm/boot/dts/am43xx-clocks.dtsi
> +++ b/arch/arm/boot/dts/am43xx-clocks.dtsi
> @@ -11,6 +11,22 @@
>   	sys_clkin_ck: sys_clkin_ck {
>   		#clock-cells = <0>;
>   		compatible = "ti,mux-clock";
> +		clocks = <&sysboot_freq_sel_ck>, <&crystal_freq_sel_ck>;
> +		ti,bit-shift = <31>;
> +		reg = <0x0040>;
> +	};
> +
> +	crystal_freq_sel_ck: crystal_freq_sel_ck {
> +		#clock-cells = <0>;
> +		compatible = "ti,mux-clock";
> +		clocks = <&virt_19200000_ck>, <&virt_24000000_ck>, <&virt_25000000_ck>, <&virt_26000000_ck>;
> +		ti,bit-shift = <29>;
> +		reg = <0x0040>;
> +	};
> +
> +	sysboot_freq_sel_ck: sysboot_freq_sel_ck at 44e10040 {
> +		#clock-cells = <0>;
> +		compatible = "ti,mux-clock";
>   		clocks = <&virt_19200000_ck>, <&virt_24000000_ck>, <&virt_25000000_ck>, <&virt_26000000_ck>;
>   		ti,bit-shift = <22>;
>   		reg = <0x0040>;
>

  reply	other threads:[~2014-05-23 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 11:36 [PATCH] ARM: dts: AM4372: clk: efuse based crystal frequency detect Sekhar Nori
2014-05-14 11:36 ` Sekhar Nori
2014-05-23 11:05 ` Tero Kristo [this message]
2014-05-23 11:05   ` Tero Kristo

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=537F2B95.1010808@ti.com \
    --to=t-kristo@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=tony@atomide.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.