Hi Alexandre,
On 2 January 2018 at 15:47, Alexandre Belloni
wrote:
> Hi Baolin,
>
> Could you have a look at
> https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git/commit/?h=rtc-ranges
>
> My approach has multiple advantages as it works for
Hi Alexandre,
On 2 January 2018 at 15:47, Alexandre Belloni
wrote:
> Hi Baolin,
>
> Could you have a look at
> https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git/commit/?h=rtc-ranges
>
> My approach has multiple advantages as it works for 64-bit counters and
> the range can be
Hi Baolin,
Could you have a look at
https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git/commit/?h=rtc-ranges
My approach has multiple advantages as it works for 64-bit counters and
the range can be updated at runtime.
On 02/01/2018 at 13:10:05 +0800, Baolin Wang wrote:
> In order
Hi Baolin,
Could you have a look at
https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git/commit/?h=rtc-ranges
My approach has multiple advantages as it works for 64-bit counters and
the range can be updated at runtime.
On 02/01/2018 at 13:10:05 +0800, Baolin Wang wrote:
> In order
In order to the setting time values are not beyond the limitation
supported by RTC hardware, we introduce one interface to tell the
hardware range to the RTC core, which are used to valid if the
setting time values are in the RTC hardware range.
Moreover we also need the RTC hardware range to
In order to the setting time values are not beyond the limitation
supported by RTC hardware, we introduce one interface to tell the
hardware range to the RTC core, which are used to valid if the
setting time values are in the RTC hardware range.
Moreover we also need the RTC hardware range to
6 matches
Mail list logo