[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZCFFAmArh20Sn7Z-FTYfreWw9cXfVN6iJNR1wAQD7gpg@mail.gmail.com>
Date: Tue, 20 Nov 2018 10:53:10 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: fthain@...egraphics.com.au
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, schwab@...ux-m68k.org,
Arnd Bergmann <arnd@...db.de>, schivers@....com.au,
Thomas Gleixner <tglx@...utronix.de>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
schmitzmic@...il.com, John Stultz <john.stultz@...aro.org>,
linux-m68k@...ts.linux-m68k.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v2 07/14] m68k: atari: Convert to clocksource API
On Tue, Nov 20, 2018 at 10:30 AM Finn Thain <fthain@...egraphics.com.au> wrote:
> On Tue, 20 Nov 2018, Linus Walleij wrote:
> > As with the Amiga, this chip also has an RTC clock that should go to the
> > RTC subsystem, naturally.
>
> I think some Atari's have an MC146818, which is drivers/rtc/rtc-cmos.c,
> arch/alpha/kernel/rtc.c etc.
Indeed, some systems have more than one RTC, often one in their
SoC silicon and one battery backed elsewhere (like a dedicated
chip on I2C or inside a PMIC).
We usually just register more of them. The RTC subsystem can
handle any amount. It's up to userspace to figure out which RTC
to actually use, which is not so good, we should probably
have some heuristic like a quality indicator on them.
Yours,
Linus Walleij
Powered by blists - more mailing lists