From: Alexander Holler <holler@ahsoftware.de>
To: John Stultz <john.stultz@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: John Whitmore <arigead@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: [PATCH 0/2][RFC] Try to handle hctosys w/ rtc modules
Date: Sat, 28 Jun 2014 09:32:50 +0200 [thread overview]
Message-ID: <53AE6FA2.7000808@ahsoftware.de> (raw)
In-Reply-To: <53AE6C3C.5090308@ahsoftware.de>
Am 28.06.2014 09:18, schrieb Alexander Holler:
> Am 27.06.2014 19:27, schrieb John Stultz:
>> Its been pointed out that the RTC hctosys functionality doesn't
>> work well with RTC modules, which may not be loaded until after
>> late_init().
>>
>> While there have been other attempts to sovle this, this patchset
>> is a very quick 10 minute effort to show how I'd try to resolve
>> this. There likely are still issues here, but I'd be happy to
>> make fixes and adjustments to ensure it works.
How long you needed to getthe idea?
>>
>> Feedback and comments always appreciated!
>
> And it still uses the non-deterministic and therefor almost unusable
> rtcN. Well done.
Besides that the current hctosys-mechanism doesn't really work with
hot-plugable devices at all. Guess what N will be when you unplug and
plug in such a RTC again.
Looks good but doesn't work => high quality. ;)
next prev parent reply other threads:[~2014-06-28 7:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 17:27 [PATCH 0/2][RFC] Try to handle hctosys w/ rtc modules John Stultz
2014-06-27 17:27 ` [PATCH 1/2][RFC] time: Introduce do_first_settimeofday() John Stultz
2014-06-27 17:27 ` [PATCH 2/2][RFC] rtc: Rework hctosys so that it is called on RTC registration John Stultz
2014-06-28 7:18 ` [PATCH 0/2][RFC] Try to handle hctosys w/ rtc modules Alexander Holler
2014-06-28 7:32 ` Alexander Holler [this message]
2014-06-28 18:54 ` Marc Dietrich
2014-06-28 20:50 ` Alexander Holler
2014-06-30 19:37 ` Alessandro Zummo
2014-07-01 18:42 ` Alexander Holler
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=53AE6FA2.7000808@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=a.zummo@towertech.it \
--cc=arigead@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@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