Re: [PATCH v8 2/2] clocksource: add J-Core timer/clocksource driver

From	Rich Felker <dalias@libc.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v8 2/2] clocksource: add J-Core timer/clocksource driver
Date	2016-10-13 21:30 +0200
Message-ID	<srTRw-7Mi-29@gated-at.bofh.it> (permalink)
References	(2 earlier) <sr9OF-1Fj-15@gated-at.bofh.it> <srbQt-2QB-1@gated-at.bofh.it> <sro1j-2kL-1@gated-at.bofh.it> <srvcu-7ms-1@gated-at.bofh.it> <srzJ7-1PE-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, Oct 12, 2016 at 11:31:26PM +0200, Daniel Lezcano wrote:
> > > --> System Type
> > > 
> > > That is what you are looking for, a SUPERH config option selecting all the
> > > common options and then a JCORE config option adding the different missing
> > > bits, namely the CLKSRC_JCORE_PIT.
> > 
> > We do have something like "system type" in arch/sh, and it's what I'm
> > trying to deprecate since it's the switch to select between all the
> > hard-coded board files, _or_ device tree.
> > 
> > Since part of the goal of my DT overhaul is to be able (but not
> > forced) to produce kernels that run on a wide range of hardware,
> > rather than having a "system type (select one)" option, what about
> > individual boolean options like:
> > 
> > config JCORE_SOC
> > 	bool "Support for J-Core SoCs"
> > 	select CLKSRC_JCORE_PIT
> > 	select JCORE_AIC
> > 	...
> 
> I'm perfectly fine with this.

Does this adequately ensure that dependencies for the clocksource and
irq driver are met? If not, what else do I need to do?

Rich

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH v8 2/2] clocksource: add J-Core timer/clocksource driver Rich Felker <dalias@libc.org> - 2016-10-13 21:30 +0200
  Re: [PATCH v8 2/2] clocksource: add J-Core timer/clocksource driver Rich Felker <dalias@libc.org> - 2016-10-13 21:50 +0200

csiph-web