On 08/30/12 23:20, Tony Lindgren wrote:
> * Igor Grinberg [120829 15:02]:
>> On 08/28/12 01:43, Shilimkar, Santosh wrote:
>>> On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg
>>> wrote:
Currently, omap2_sync32k_clocksource_init() function initializes the 32K
timer as the system clock sou
* Igor Grinberg [120829 15:02]:
> On 08/28/12 01:43, Shilimkar, Santosh wrote:
> > On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg
> > wrote:
> >> Currently, omap2_sync32k_clocksource_init() function initializes the 32K
> >> timer as the system clock source regardless of the CONFIG_OMAP_32K_TIMER
On 08/28/12 01:43, Shilimkar, Santosh wrote:
> On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg
> wrote:
>> Currently, omap2_sync32k_clocksource_init() function initializes the 32K
>> timer as the system clock source regardless of the CONFIG_OMAP_32K_TIMER
>> setting.
>> Fix this by providing a def
On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg wrote:
> Currently, omap2_sync32k_clocksource_init() function initializes the 32K
> timer as the system clock source regardless of the CONFIG_OMAP_32K_TIMER
> setting.
> Fix this by providing a default implementation for
> !CONFIG_OMAP_32K_TIMER case.
Currently, omap2_sync32k_clocksource_init() function initializes the 32K
timer as the system clock source regardless of the CONFIG_OMAP_32K_TIMER
setting.
Fix this by providing a default implementation for
!CONFIG_OMAP_32K_TIMER case.
Signed-off-by: Igor Grinberg
Reviewed-by: Paul Walmsley
---