From: Igor Grinberg <hidden> Date: 2012-08-27 22:26:14
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 <redacted>
Reviewed-by: Paul Walmsley <paul@pwsan.com>
---
arch/arm/mach-omap2/timer.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg [off-list ref] 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.
Signed-off-by: Igor Grinberg <redacted>
Reviewed-by: Paul Walmsley <paul@pwsan.com>
---
From: Igor Grinberg <hidden> Date: 2012-08-29 22:01:13
On 08/28/12 01:43, Shilimkar, Santosh wrote:
On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg [off-list ref] wrote:
quoted
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 <redacted>
Reviewed-by: Paul Walmsley <paul@pwsan.com>
---
Acked-by: Santosh Shilimkar <redacted>
Thanks Santosh!
Tony, apparently, this bug has been there for a while,
so probably I should have added:
Cc: stable at vger.kernel.org
Thanks!
--
Regards,
Igor.
On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg [off-list ref] wrote:
quoted
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 <redacted>
Reviewed-by: Paul Walmsley <paul@pwsan.com>
---
Acked-by: Santosh Shilimkar <redacted>
Thanks Santosh!
Tony, apparently, this bug has been there for a while,
so probably I should have added:
Cc: stable at vger.kernel.org
Thanks I'll apply this into fixes with Cc: stable. Note that
Cc: stable is usually added at commit time, or at least you're
not supposed to send the patch for review there.
Regards,
Tony
From: Igor Grinberg <hidden> Date: 2012-08-30 22:26:51
On 08/30/12 23:20, Tony Lindgren wrote:
* Igor Grinberg [off-list ref] [120829 15:02]:
quoted
On 08/28/12 01:43, Shilimkar, Santosh wrote:
quoted
On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg [off-list ref] wrote:
quoted
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 <redacted>
Reviewed-by: Paul Walmsley <paul@pwsan.com>
---
Acked-by: Santosh Shilimkar <redacted>
Thanks Santosh!
Tony, apparently, this bug has been there for a while,
so probably I should have added:
Cc: stable at vger.kernel.org
Thanks I'll apply this into fixes with Cc: stable. Note that
Cc: stable is usually added at commit time, or at least you're
not supposed to send the patch for review there.
Yeah yeah, I know, I just forgot to add it while committing.
Thanks!
--
Regards,
Igor.