From: Steve Muckle <smuckle@google.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH] rtc: class: support hctosys from modular RTC drivers
Date: Wed, 6 Nov 2019 15:37:49 -0800 [thread overview]
Message-ID: <b96f085b-8a0c-7c71-4fde-8af83d49823a@google.com> (raw)
In-Reply-To: <20191106231923.GK8309@piout.net>
On 11/6/19 3:19 PM, Alexandre Belloni wrote:
> On 06/11/2019 11:46:25-0800, Steve Muckle wrote:
>> Due to distribution constraints it may not be possible to statically
>> compile the required RTC driver into the kernel.
>>
>> Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled
>> or not) by checking at the end of RTC device registration whether the
>> time should be synced.
>>
>
> This does not really help distributions because most of them will still
> have "rtc0" hardcoded and rtc0 is often the rtc that shouldn't be used.
Just for my own edification, why is that? Is rtc0 normally useless on PC
for some reason?
On the platforms I'm working with I believe it can be assured that rtc0
will be the correct rtc. That doesn't help typical distributions though.
What about a kernel parameter to optionally override the rtc hctosys
device at runtime?
> Can't you move away from HCTOSYS and do the correct thing in userspace
> instead of the crap hctosys is doing?
Yes, I just figured it's a small change, and if hctosys can be made to
work might as well use that.
next prev parent reply other threads:[~2019-11-06 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 19:46 [PATCH] rtc: class: support hctosys from modular RTC drivers Steve Muckle
2019-11-06 23:19 ` Alexandre Belloni
2019-11-06 23:37 ` Steve Muckle [this message]
2019-11-15 13:36 ` Alexandre Belloni
2019-12-27 20:26 ` Steve Muckle
2020-01-31 18:35 ` Steve Muckle
[not found] ` <CAL21Ktd3JmRbkwPCCb77knXg4AWi0vWdU147sVaDaoWeEMauDQ@mail.gmail.com>
2020-03-23 20:06 ` Alexandre Belloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b96f085b-8a0c-7c71-4fde-8af83d49823a@google.com \
--to=smuckle@google.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).