[PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER

Jon Hunter jon-hunter at ti.com
Mon Nov 12 14:15:29 EST 2012

On 11/11/2012 05:28 AM, Igor Grinberg wrote:
> On 11/08/12 21:16, Jon Hunter wrote:
>> On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
>>> On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
>>>> On 11/08/2012 01:59 AM, Igor Grinberg wrote:
>>>> [snip]
>>>>> There is no reliable way to determine which source should be used in runtime
>>>>> for boards that do not have the 32k oscillator wired.
>>>> So thinking about this some more and given that we are moving away from
>>>> board files, if a board does not provide a 32kHz clock source, then this
>>>> should be reflected in the device-tree source file for that board.
>>>> Hence, at boot time we should be able to determine if a 32kHz clock
>>>> source can be used.
>>> Let me feed some more thoughts here :)
>>> The way it is being detected currently is based on timer idle status bit.
>>> I am worried that, this is the only option we have.
>> Why not use device-tree to indicate the presence of a 32k clock source?
>> This seems like a board level configuration and so device-tree seems to
>> be the perfect place for this IMO.
> Well, that is what my commit message says...

Sorry, but that was not clear to me from whats in the commit message.

Should we be doing this now instead of adding all these static timer
init functions?

Are there any boards today (supported in the kernel that is), that don't
support a 32k?

If not, then this becomes simpler for the non-DT case and given that
boards such as the AM335x will only support DT boot then we can figure
out how to detect the presence of the 32k for DT only.


More information about the linux-arm-kernel mailing list