[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51BB6DD9.6010200@linaro.org>
Date: Fri, 14 Jun 2013 12:24:09 -0700
From: John Stultz <john.stultz@...aro.org>
To: Alexander Holler <holler@...oftware.de>
CC: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
rtc-linux@...glegroups.com, Thomas Gleixner <tglx@...utronix.de>,
Alessandro Zummo <a.zummo@...ertech.it>
Subject: Re: [PATCH 5/9 v3] RFC: timekeeping: rtc: Introduce new kernel parameter
hctosys
On 06/14/2013 09:52 AM, Alexander Holler wrote:
> hctosys= specifies the driver (RTC) name which sets the system clock at
> boot, if and only if userspace hasn't set the time before the driver will
> be loaded.
>
> If hctosys will not be specified, the first available hardware clock
> with a valid time will be used (again, if and only if ...).
>
> If you don't want that the system clock will be set by any hardware clock,
> just specify a non-existent RTC driver name, e.g. with hctosys=none.
So what was the rational for this to be a boot time argument instead of
using the existing compile time CONFIG_RTC_HCTOSYS_DEVICE?
If we need a boot argument, that's still doable, but it probably should
fall back to CONFIG_RTC_HCTOSYS_DEVICE if not specified.
thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists