public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: John Stultz <john.stultz@linaro.org>
Cc: Kay Sievers <kay@vrfy.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCK changes?
Date: Wed, 24 Apr 2013 07:12:09 +0200	[thread overview]
Message-ID: <517769A9.5060308@ahsoftware.de> (raw)
In-Reply-To: <51774F44.2060704@linaro.org>

Hello,

Am 24.04.2013 05:19, schrieb John Stultz:

> On x86 the persistent_clock() is backed by the
> CMOS/EFI/kvm-wall/xen/vrtc clock (all via x86_platform.get_wallclock)
> should be present and we'll initialize the time in timekeeping_init()
> there.
>
> Its only systems where there isn't a persistent_clock is where the RTC
> layer and the HCTOSYS is helpful.

I'm a bit confused too. ;)

Doesn't this remove the users choice of RTC on x86 systems?

Why is there a difference made between the CMOS/EFI/... clocks and other 
RTCs?

And why is RTC_SYSTOHC now gone on x86?

Regards,

Alexander

  parent reply	other threads:[~2013-04-24  5:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  1:34 CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCK changes? Kay Sievers
2013-04-24  2:43 ` John Stultz
2013-04-24  3:05   ` Kay Sievers
2013-04-24  3:19     ` John Stultz
2013-04-24  3:33       ` Kay Sievers
2013-04-24  3:51         ` Kay Sievers
2013-04-24 16:33           ` John Stultz
2013-04-24 16:30         ` John Stultz
2013-04-24 16:51           ` Kay Sievers
2013-04-24  5:12       ` Alexander Holler [this message]
2013-04-24 16:07         ` John Stultz
2013-04-24 16:32           ` Kay Sievers
2013-04-24 16:42             ` John Stultz
2013-04-25  7:11           ` Alexander Holler
2013-04-25 16:01             ` Kay Sievers
2013-04-25 16:13             ` John Stultz
2013-04-25 18:33               ` Jason Gunthorpe
2013-04-25 19:45                 ` Kay Sievers
2013-04-25 19:54                   ` John Stultz
2013-04-25 20:35                     ` Jason Gunthorpe
2013-04-25 20:03                 ` John Stultz
2013-04-25 21:02                   ` Jason Gunthorpe

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=517769A9.5060308@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=john.stultz@linaro.org \
    --cc=kay@vrfy.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