Re: [PATCH 1/3] ARM: OMAP2+: 32k-counter: Use hwmod lookup to check presence of 32k timer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 3, 2012 at 12:05 AM, Kevin Hilman <khilman@xxxxxx> wrote:
> "Shilimkar, Santosh" <santosh.shilimkar@xxxxxx> writes:
>
> [...]
>
>> I don't personally like to add features which hardly anybody use and
>> fundamentally broken with full kernel.
>
> Let's keep sane defaults, but not make it unreasonable to tweak eaither.
>
Exactly. Thanks for echoing the concern.

> I suggest what has already been mentioned.
>
> Register both timers, but have the sync timer have a higher rating.  On
> AMxxx where there is no sync timer, GPtimer will be used.
>
Technically it's a hack just from clock precision point of view but I don't mind
this.

> For those who want to use GPtimer, they can boot using clocksource= to
> override the default.
>
Sounds good to me.

> Santosh is right, GPtimer will not work on a PM enabled kernel, but
> there are lots of ways to use the cmdline to get a non-working kernel,
> so that's OK by me.
>
> Let's just ensure that the boot-defaults are sane.
>
Absolutely.

Regards
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux