Currently, when configuring the clock-events and clock-source timers
for OMAP2+ devices, we check whether the timer ID is 12 before
attempting to set the parent clock for the timer.
This test was added for OMAP3 general purpose devices (no security
features enabled) that a 12th timer available
On Mon, Feb 04, 2013 at 11:43:02AM -0600, Jon Hunter wrote:
@@ -280,22 +281,22 @@ static int __init omap_dm_timer_init_one(struct
omap_dm_timer *timer,
if (IS_ERR(timer-fclk))
return -ENODEV;
- /* FIXME: Need to remove hard-coded test on timer ID */
- if
On 02/04/2013 11:46 AM, Russell King - ARM Linux wrote:
On Mon, Feb 04, 2013 at 11:43:02AM -0600, Jon Hunter wrote:
@@ -280,22 +281,22 @@ static int __init omap_dm_timer_init_one(struct
omap_dm_timer *timer,
if (IS_ERR(timer-fclk))
return -ENODEV;
-/* FIXME: Need
