linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tony Luck <tony.luck@intel.com>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Helge Deller <deller@gmx.de>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Rich Felker <dalias@libc.org>,
	David Howells <dhowells@redhat.com>,
	Koichi Yasutake <yasutake.koichi@jp.panasonic.com>,
	Richard Henderson <rth@twiddle.net>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	alpha <linux-alpha@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	Parisc List <linux-parisc@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	RTCLINUX <rtc-linux@googlegroups.com>,
	Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: char: legacy RTC cleanups
Date: Wed, 27 Apr 2016 10:33:04 +0200	[thread overview]
Message-ID: <6883809.SRgmlLMdyd@wuerfel> (raw)
In-Reply-To: <CAMuHMdV=R3ad33vPdMZNvZZ8A_DF+F2C8nyAmXOmFiiP50D_UQ@mail.gmail.com>

On Wednesday 27 April 2016 09:54:41 Geert Uytterhoeven wrote:
> Hi Arnd,
> 
> On Tue, Apr 26, 2016 at 11:44 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > For the genrtc driver, rearranging the headers makes it simpler
> > to use and reduces duplication. In case of alpha and mn10300,
> > I've shown that the genrtc and rtc drivers are doing the same
> > thing, so we don't need them both. The remaining three
> > architectures (m68k, parisc, powerpc) actually all support
> > the newer rtc-generic driver, so we could remove genrtc completely
> > if we want to.
> 
> CONFIG_GEN_RTC is not enabled in any of the m68k defconfigs, so I think genrtc
> has been unused for a while.
> All defconfigs either use CONFIG_RTC_DRV_GENERIC, or enable a more specific
> RTC driver.

Ok, good to know. I'm guessing the same is true for parisc, but there are
also very few users.

Regarding the Q40 specific ioctls, what do you think this means, is it

a) nobody uses Q40 with modern kernels,
b) nobody calls RTC_PLL_GET/RTC_PLL_SET on q40, or
c) Q40 users have their own configurations and enable GEN_RTC?

On powerpc, a quarter of the defconfigs (mostly for really old hardware)
still use GEN_RTC, but I guess we can either bulk-convert them to RTC_GENERIC,
or convert the five implementations of .get_rtc_time/.set_rtc_time
(8xx, rtas, chrp, powermac, maple) into five regular RTC class drivers.

	Arnd

  reply	other threads:[~2016-04-27  8:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 21:44 char: legacy RTC cleanups Arnd Bergmann
2016-04-26 21:44 ` [PATCH 1/8] char/rtc: replace blacklist with whitelist Arnd Bergmann
2016-04-27  8:31   ` Alexandre Belloni
2016-04-26 21:44 ` [PATCH 2/8] char/rtc: legacy RTC is no longer supported on x86 Arnd Bergmann
2016-04-27  8:35   ` Alexandre Belloni
2016-04-27 10:05   ` Thomas Gleixner
2016-04-26 21:44 ` [PATCH 3/8] char/rtc: remove empty asm/mc146818rtc.h files Arnd Bergmann
2016-04-27  8:41   ` Alexandre Belloni
2016-04-26 21:44 ` [PATCH 4/8] char/rtc: move mc146818rtc code out of asm-generic/rtc.h Arnd Bergmann
2016-04-27  9:29   ` Alexandre Belloni
2016-04-27  9:59     ` Arnd Bergmann
2016-04-26 21:44 ` [PATCH 5/8] char/genrtc: powerpc: use asm-generic/rtc.h Arnd Bergmann
2016-04-26 21:44 ` [PATCH 6/8] char/genrtc: parisc: " Arnd Bergmann
2016-04-26 22:07   ` Rolf Eike Beer
2016-04-27 11:21     ` Arnd Bergmann
2016-04-27 11:35       ` Arnd Bergmann
2016-04-27 11:55         ` Geert Uytterhoeven
2016-04-27 12:44           ` Arnd Bergmann
2016-04-26 21:44 ` [PATCH 7/8] char/genrtc: disallow building on Alpha Arnd Bergmann
2016-04-26 21:44 ` [PATCH 8/8] char/genrtc: disallow building on mn10300 Arnd Bergmann
2016-04-27  7:54 ` char: legacy RTC cleanups Geert Uytterhoeven
2016-04-27  8:33   ` Arnd Bergmann [this message]
2016-04-27  8:41     ` Geert Uytterhoeven
2016-04-27  9:44 ` Alexandre Belloni
2016-04-27 10:07   ` Arnd Bergmann
2016-04-27 10:19     ` Geert Uytterhoeven
2016-04-27 11:30       ` Arnd Bergmann

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=6883809.SRgmlLMdyd@wuerfel \
    --to=arnd@arndb.de \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=benh@kernel.crashing.org \
    --cc=dalias@libc.org \
    --cc=deller@gmx.de \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jejb@parisc-linux.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=rtc-linux@googlegroups.com \
    --cc=rth@twiddle.net \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=yasutake.koichi@jp.panasonic.com \
    /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;
as well as URLs for NNTP newsgroup(s).