linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER
Date: Thu, 8 Nov 2012 12:34:54 -0600	[thread overview]
Message-ID: <509BFB4E.2090802@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1211081809470.20703@utopia.booyaka.com>


On 11/08/2012 12:17 PM, Paul Walmsley wrote:
> On Thu, 8 Nov 2012, Jon Hunter wrote:
> 
>> On 11/08/2012 11:58 AM, Paul Walmsley wrote:
>>> On Thu, 8 Nov 2012, Jon Hunter wrote:
>>>
>>>> Igor was mentioning a h/w scenario where the 32kHz source is not
>>>> present. However, I am not sure which devices support this and is
>>>> applicable too.
>>>
>>> Pretty sure Igor is referring to the AM3517/3505.  This is very poorly 
>>> documented, but can be observed in the AM3517 TRM Rev B (SPRUGR0B) Figure 
>>> 4-23 "PRM Clock Generator" and the AM3517 DM Rev C (SPRS550C) Section 4 
>>> "Clock Specifications".
>>
>> But AFAICT, even in that h/w configuration the internal 32k
>> oscillator will be used
> 
> Just to clarify, there's no internal 32k oscillator used on the 3517/3505; 
> just a divider from the HF clock.

Ah yes I see that now!

>> and so the gptimer will still have a 32k clock source.
> 
> That's a good question and you might want to check with Igor on that one,
> the AM3517 TRM conflicts with the DM as to whether it's available to the 
> GPTIMER or not :-(

Well the external 32k and internal divided down version go through the
same mux and so that seems to imply either they are both available to
the gptimer or neither is.

Cheers
Jon

  reply	other threads:[~2012-11-08 18:34 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 14:42 [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER Igor Grinberg
2012-11-07 17:33 ` Tony Lindgren
2012-11-08  7:13   ` Igor Grinberg
2012-11-08 16:20     ` Tony Lindgren
2012-11-08 17:09       ` Hiremath, Vaibhav
2012-11-11  9:16       ` Igor Grinberg
2012-11-12 19:05         ` Jon Hunter
2012-11-13  9:08           ` Igor Grinberg
2012-11-12 22:06         ` Tony Lindgren
2012-11-07 21:36 ` Jon Hunter
2012-11-08  7:59   ` Igor Grinberg
2012-11-08 16:16     ` Jon Hunter
2012-11-08 17:08       ` Hiremath, Vaibhav
2012-11-08 17:39         ` Jon Hunter
2012-11-08 17:47           ` Hiremath, Vaibhav
2012-11-08 17:58             ` Jon Hunter
2012-11-08 18:06               ` Hiremath, Vaibhav
2012-11-08 18:13                 ` Jon Hunter
2012-11-08 18:28                   ` Hiremath, Vaibhav
2012-11-08 18:47                     ` Jon Hunter
2012-11-09  0:55                 ` Jon Hunter
2012-11-12  6:42                   ` Hiremath, Vaibhav
2012-11-08 17:58           ` Paul Walmsley
2012-11-08 18:08             ` Jon Hunter
2012-11-08 18:17               ` Paul Walmsley
2012-11-08 18:34                 ` Jon Hunter [this message]
2012-11-11 11:35                   ` Igor Grinberg
2012-11-12  6:38                     ` Hiremath, Vaibhav
2012-11-12  7:24                       ` Igor Grinberg
2012-11-12 10:40                         ` Hiremath, Vaibhav
2012-12-10 20:49                     ` Paul Walmsley
2012-12-14 23:58         ` Russ Dill
2012-11-11 11:25       ` Igor Grinberg
2012-11-08 18:54     ` Jon Hunter
2012-11-08 18:59       ` Hiremath, Vaibhav
2012-11-08 19:16         ` Jon Hunter
2012-11-11 11:28           ` Igor Grinberg
2012-11-12 19:15             ` Jon Hunter
2012-11-13  9:14               ` Igor Grinberg
2012-11-13 16:13                 ` Jon Hunter
2012-11-14  7:23                   ` Igor Grinberg
2012-11-12 10:38           ` Hiremath, Vaibhav
2012-11-12 11:01             ` Benoit Cousson

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=509BFB4E.2090802@ti.com \
    --to=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).