All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Jun Sun <jsun@mvista.com>,
	"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Linux/MIPS Development <linux-mips@oss.sgi.com>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC] generic MIPS RTC driver
Date: Tue, 13 Nov 2001 14:42:40 +0100	[thread overview]
Message-ID: <20011113144240.B669@linux-m68k.org> (raw)
In-Reply-To: <3BF0371F.8040575B@linux-m68k.org>; from zippel@linux-m68k.org on Mon, Nov 12, 2001 at 09:54:55PM +0100

On Mon, Nov 12, 2001 at 09:54:55PM +0100, Roman Zippel wrote:
> Hi,
> 
> Geert Uytterhoeven wrote:
> 
> > > Geert, what is the abstraction they used?
> > 
> > At first sight, we only use get_rtc_time() and mach_hwclk().
> 
> Over the weekend I changed it into set_rtc_time()/get_rtc_time(), which
> are now defined in <asm/rtc.h>, so mach_hwclk() is gone in the generic
> part.
> Another feature is the emulation of the timer interrupt, although I have
> no idea which program is using this.

hwclock and a bunch of less known porgrams like chrony. 
Where the interrupt can be generated its a clear win, otherwise
it might be more reasonable to return EINVAL instead of trying
to emulate it - presumably hwclock can use some fallback method.

Btw the interrupt need not to be hardware, for the Q40 I test 
a rtc register once per jiffie and generate a "soft interrupt".
It could be done generic at least for m68k.

Bye
Richard

WARNING: multiple messages have this Message-ID (diff)
From: Richard Zidlicky <rz@linux-m68k.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Jun Sun <jsun@mvista.com>,
	"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Linux/MIPS Development <linux-mips@oss.sgi.com>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC] generic MIPS RTC driver
Date: Tue, 13 Nov 2001 14:42:40 +0100	[thread overview]
Message-ID: <20011113144240.B669@linux-m68k.org> (raw)
In-Reply-To: <3BF0371F.8040575B@linux-m68k.org>; from zippel@linux-m68k.org on Mon, Nov 12, 2001 at 09:54:55PM +0100


On Mon, Nov 12, 2001 at 09:54:55PM +0100, Roman Zippel wrote:
> Hi,
>
> Geert Uytterhoeven wrote:
>
> > > Geert, what is the abstraction they used?
> >
> > At first sight, we only use get_rtc_time() and mach_hwclk().
>
> Over the weekend I changed it into set_rtc_time()/get_rtc_time(), which
> are now defined in <asm/rtc.h>, so mach_hwclk() is gone in the generic
> part.
> Another feature is the emulation of the timer interrupt, although I have
> no idea which program is using this.

hwclock and a bunch of less known porgrams like chrony.
Where the interrupt can be generated its a clear win, otherwise
it might be more reasonable to return EINVAL instead of trying
to emulate it - presumably hwclock can use some fallback method.

Btw the interrupt need not to be hardware, for the Q40 I test
a rtc register once per jiffie and generate a "soft interrupt".
It could be done generic at least for m68k.

Bye
Richard

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-11-13 14:10 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11  7:17 [RFC] generic MIPS RTC driver Jun Sun
2001-11-11 10:14 ` Geert Uytterhoeven
2001-11-11 10:14   ` Geert Uytterhoeven
2001-11-12 12:59   ` Maciej W. Rozycki
2001-11-12 12:59     ` Maciej W. Rozycki
2001-11-12 13:11     ` Geert Uytterhoeven
2001-11-12 13:11       ` Geert Uytterhoeven
2001-11-12 13:29       ` Maciej W. Rozycki
2001-11-12 13:29         ` Maciej W. Rozycki
2001-11-12 16:14         ` Pete Popov
2001-11-12 16:14           ` Pete Popov
2001-11-12 18:26           ` Jun Sun
2001-11-12 18:26             ` Jun Sun
2001-11-12 18:56             ` Jun Sun
2001-11-12 18:56               ` Jun Sun
2001-11-12 21:51               ` Tom Rini
2001-11-12 21:51                 ` Tom Rini
2001-11-12 18:24         ` Jun Sun
2001-11-12 18:24           ` Jun Sun
2001-11-12 19:04           ` Maciej W. Rozycki
2001-11-12 19:04             ` Maciej W. Rozycki
2001-11-12 19:21             ` Jun Sun
2001-11-12 19:21               ` Jun Sun
2001-11-12 18:19       ` Jun Sun
2001-11-12 18:19         ` Jun Sun
2001-11-12 18:55         ` Maciej W. Rozycki
2001-11-12 18:55           ` Maciej W. Rozycki
2001-11-12 19:13           ` Jun Sun
2001-11-12 19:13             ` Jun Sun
2001-11-12 20:02         ` Geert Uytterhoeven
2001-11-12 20:02           ` Geert Uytterhoeven
2001-11-12 20:54           ` Roman Zippel
2001-11-12 20:54             ` Roman Zippel
2001-11-13  1:31             ` Tom Rini
2001-11-13  1:31               ` Tom Rini
2001-11-13  6:20               ` Geert Uytterhoeven
2001-11-13  6:20                 ` Geert Uytterhoeven
2001-11-13 14:44                 ` Tom Rini
2001-11-13 14:44                   ` Tom Rini
2001-11-13 14:47                   ` Geert Uytterhoeven
2001-11-13 14:47                     ` Geert Uytterhoeven
2001-11-13 15:30                   ` Roman Zippel
2001-11-13 15:30                     ` Roman Zippel
2001-11-13 15:30                     ` Roman Zippel
2001-11-13 13:42             ` Richard Zidlicky [this message]
2001-11-13 13:42               ` Richard Zidlicky
2001-11-13 15:32               ` Roman Zippel
2001-11-13 15:32                 ` Roman Zippel
2001-11-14  9:46                 ` Richard Zidlicky
2001-11-14  9:46                   ` Richard Zidlicky
2001-11-13 17:58               ` Jun Sun
2001-11-13 17:58                 ` Jun Sun
2001-11-14 10:08                 ` Richard Zidlicky
2001-11-14 10:08                   ` Richard Zidlicky
2001-11-15 17:41                   ` Jun Sun
2001-11-15 17:41                     ` Jun Sun
2001-11-12  1:45 ` Atsushi Nemoto
2001-11-12 19:26   ` Jun Sun

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=20011113144240.B669@linux-m68k.org \
    --to=rz@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=jsun@mvista.com \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.