All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
To: Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH 2/2] ARM: omap5/dra7xx: Fix counter frequency drift for AM572x errata i856.
Date: Wed, 17 Dec 2014 10:27:10 -0500	[thread overview]
Message-ID: <20141217152710.GT24110@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20141217152225.GA737@kahuna>

On Wed, Dec 17, 2014 at 09:22:25AM -0600, Nishanth Menon wrote:
> A clock mux might do the job?
> 
> value 1, 2 , 3 will imply sysclk1 / 610
> value of 0 implies fixed 32768
> 
> soemthing like
> sys_clk32_crystal {
>                compatible = "fixed-clock";
>                clock-frequency = <32768>;
> }
> 
> sys_clk32_pseudo {
>                compatible = "fixed-clock";
>                compatible = "fixed-factor-clock";
>                clocks = <&sys_clkin1>;
>                clock-mult = <1>;
>                clock-div = <610>;
> }
> 
> sys_32k_ck: sys_32k_ck {
> 	compatible = "ti,mux-clock";
> 	clocks = <&sys_clk32_crystal>, <&sys_clk32_pseudo>, <&sys_clk32_pseudo>, <&sys_clk32_pseudo>;
> };
> 
> I think... The only issue is that the BOOTSTRAP register is not around
> the usual CM1,2 address region...

OK, I like where that idea is headed.  That looks promising.

-- 
Len Sorensen

WARNING: multiple messages have this Message-ID (diff)
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: omap5/dra7xx: Fix counter frequency drift for AM572x errata i856.
Date: Wed, 17 Dec 2014 10:27:10 -0500	[thread overview]
Message-ID: <20141217152710.GT24110@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20141217152225.GA737@kahuna>

On Wed, Dec 17, 2014 at 09:22:25AM -0600, Nishanth Menon wrote:
> A clock mux might do the job?
> 
> value 1, 2 , 3 will imply sysclk1 / 610
> value of 0 implies fixed 32768
> 
> soemthing like
> sys_clk32_crystal {
>                compatible = "fixed-clock";
>                clock-frequency = <32768>;
> }
> 
> sys_clk32_pseudo {
>                compatible = "fixed-clock";
>                compatible = "fixed-factor-clock";
>                clocks = <&sys_clkin1>;
>                clock-mult = <1>;
>                clock-div = <610>;
> }
> 
> sys_32k_ck: sys_32k_ck {
> 	compatible = "ti,mux-clock";
> 	clocks = <&sys_clk32_crystal>, <&sys_clk32_pseudo>, <&sys_clk32_pseudo>, <&sys_clk32_pseudo>;
> };
> 
> I think... The only issue is that the BOOTSTRAP register is not around
> the usual CM1,2 address region...

OK, I like where that idea is headed.  That looks promising.

-- 
Len Sorensen

  reply	other threads:[~2014-12-17 15:27 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 22:08 [PATCH 0/2] ARM: omap5/dra7xx counter frequency fixes Lennart Sorensen
2014-12-12 22:08 ` Lennart Sorensen
2014-12-12 22:08 ` [PATCH 1/2] ARM: omap5/dra7xx: Fix frequency typos Lennart Sorensen
2014-12-12 22:08   ` Lennart Sorensen
2014-12-16 11:38   ` Lokesh Vutla
2014-12-16 11:38     ` Lokesh Vutla
2014-12-16 11:38     ` Lokesh Vutla
2014-12-16 14:06   ` Nishanth Menon
2014-12-16 14:06     ` Nishanth Menon
2014-12-16 14:06     ` Nishanth Menon
2014-12-16 16:39     ` Lennart Sorensen
2014-12-16 16:39       ` Lennart Sorensen
2014-12-12 22:08 ` [PATCH 2/2] ARM: omap5/dra7xx: Fix counter frequency drift for AM572x errata i856 Lennart Sorensen
2014-12-12 22:08   ` Lennart Sorensen
2014-12-14  4:45   ` Lennart Sorensen
2014-12-14  4:45     ` Lennart Sorensen
2014-12-16 11:35     ` Lokesh Vutla
2014-12-16 11:35       ` Lokesh Vutla
2014-12-16 11:35       ` Lokesh Vutla
2014-12-16 14:58       ` Nishanth Menon
2014-12-16 14:58         ` Nishanth Menon
2014-12-16 14:58         ` Nishanth Menon
2014-12-16 16:36         ` Lennart Sorensen
2014-12-16 16:36           ` Lennart Sorensen
2014-12-16 18:59           ` Nishanth Menon
2014-12-16 18:59             ` Nishanth Menon
2014-12-16 18:59             ` Nishanth Menon
2014-12-16 19:27             ` Lennart Sorensen
2014-12-16 19:27               ` Lennart Sorensen
2014-12-16 19:33               ` Nishanth Menon
2014-12-16 19:33                 ` Nishanth Menon
2014-12-16 19:33                 ` Nishanth Menon
2014-12-17 13:21         ` Tero Kristo
2014-12-17 13:21           ` Tero Kristo
2014-12-17 13:21           ` Tero Kristo
2014-12-17 14:55           ` Lennart Sorensen
2014-12-17 14:55             ` Lennart Sorensen
2014-12-17 15:22             ` Nishanth Menon
2014-12-17 15:22               ` Nishanth Menon
2014-12-17 15:22               ` Nishanth Menon
2014-12-17 15:27               ` Lennart Sorensen [this message]
2014-12-17 15:27                 ` Lennart Sorensen
2014-12-17 15:45                 ` Tero Kristo
2014-12-17 15:45                   ` Tero Kristo
2014-12-17 15:45                   ` Tero Kristo
2014-12-17 15:49                   ` Lennart Sorensen
2014-12-17 15:49                     ` Lennart Sorensen
2014-12-17 15:53                   ` Nishanth Menon
2014-12-17 15:53                     ` Nishanth Menon
2014-12-17 15:53                     ` Nishanth Menon
2014-12-17 15:56                     ` Tero Kristo
2014-12-17 15:56                       ` Tero Kristo
2014-12-17 15:56                       ` Tero Kristo
2014-12-16 16:16       ` Lennart Sorensen
2014-12-16 16:16         ` Lennart Sorensen
2014-12-16 19:56         ` Nishanth Menon
2014-12-16 19:56           ` Nishanth Menon
2014-12-16 19:56           ` Nishanth Menon
2014-12-16 19:58           ` Lennart Sorensen
2014-12-16 19:58             ` Lennart Sorensen

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=20141217152710.GT24110@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=t-kristo@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 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.