public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: david-b@pacbell.net
Cc: James.Bottomley@hansenpartnership.com,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
	alessandro.zummo@towertech.it
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC
Date: Mon, 08 Sep 2008 16:44:27 -0700 (PDT)	[thread overview]
Message-ID: <20080908.164427.216880550.davem@davemloft.net> (raw)
In-Reply-To: <200809081629.21125.david-b@pacbell.net>

From: David Brownell <david-b@pacbell.net>
Date: Mon, 8 Sep 2008 16:29:20 -0700

> That said, there's a bit of unresolved stuff around NTP hooks
> in the kernel.  Some patches are pending to let thtem work with
> the RTC framework -- where writing an RTC may need to sleep,
> for example because the RTC is on an I2C or SPI bus.  And
> then there's the discussion of whether that shouldn't all be
> handled by NTPD anyway, no special kernel support desired.
> Alessandro has opinions there.  ;)

My update_persistent_clock() on sparc64 is:

int update_persistent_clock(struct timespec now)
{
	struct rtc_device *rtc = rtc_class_open("rtc0");

	if (rtc)
		return rtc_set_mmss(rtc, now.tv_sec);

	return -1;
}

and that should handle this NTP shouldn't it?

  reply	other threads:[~2008-09-08 23:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 15:53 [PATCH] fix RTC_CLASS regression with PARISC James Bottomley
2008-09-08 18:19 ` David Brownell
2008-09-08 18:39   ` James Bottomley
2008-09-08 19:13     ` David Brownell
2008-09-08 20:28       ` James Bottomley
2008-09-08 21:29         ` David Brownell
2008-09-08 21:35           ` David Miller
2008-09-08 23:00             ` James Bottomley
2008-09-08 23:04               ` David Miller
2008-09-08 23:23                 ` James Bottomley
2008-09-08 23:32                   ` David Brownell
2008-09-08 23:43                   ` David Miller
2008-09-08 23:29                 ` David Brownell
2008-09-08 23:44                   ` David Miller [this message]
2008-09-09  0:55                     ` David Brownell
2008-09-09  2:52                       ` David Miller
2008-09-09  3:17                         ` David Brownell
2008-09-09  3:51                           ` David Miller
2008-09-09  4:14                             ` David Brownell
2008-09-10 21:04                         ` Andrew Morton
2008-09-10 21:09                           ` Randy.Dunlap
2008-09-10 21:19                             ` David Brownell
2008-09-10 21:20                               ` David Miller
2008-09-10 21:36                                 ` David Brownell
2008-09-10 21:40                                   ` David Miller
2008-09-09  1:22                     ` Paul Mackerras
2008-09-08 21:37           ` James Bottomley

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=20080908.164427.216880550.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=alessandro.zummo@towertech.it \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=torvalds@linux-foundation.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