Re: [RFC PATCH] ARM: clocksource: make ARM_GLOBAL_TIMER selectable

From	Sören Brinkmann <soren.brinkmann@xilinx.com>
Newsgroups	linux.kernel
Subject	Re: [RFC PATCH] ARM: clocksource: make ARM_GLOBAL_TIMER selectable
Date	2016-02-26 16:30 +0100
Message-ID	<r6sv7-5gy-1@gated-at.bofh.it> (permalink)
References	<qYwPf-5Eq-5@gated-at.bofh.it> <qYAJd-8hU-31@gated-at.bofh.it> <qYBlT-lJ-7@gated-at.bofh.it> <qYBFg-u5-21@gated-at.bofh.it> <r6qjD-3Lu-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, 2016-02-26 at 15:03:19 +0200, Grygorii Strashko wrote:
> On 02/05/2016 01:39 AM, Sören Brinkmann wrote:
> > On Thu, 2016-02-04 at 15:14:47 -0800, Moritz Fischer wrote:
> >> Hi Soeren,
> >>
> >> On Thu, Feb 4, 2016 at 2:41 PM, Sören Brinkmann
> >> <soren.brinkmann@xilinx.com> wrote:
> >>
> >>> But with this change the 'if !CPU_FREQ' becomes obsolete.
> >> I'm confused, could you explain that statement? You don't want people
> >> accidentally running with GT when CPU_FREQ is on, right?
> > 
> > Correct. But with this Kconfig rework you can just deselect it in
> > Kconfig. The generic HAVE_GT could always be selected.
> > 
> 
> 
> Don't know whom should i ask - but what will be the final conclusion here?
> Can it be merged?

I think we don't break anything either way. Would just be some
additional clean up to get rid of that mentioned constraint (which
doesn't really work well anyway in the multi-arch kernel). So, no real
objections to merging it from my side.

	Thanks,
	Sören

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

Thread

Re: [RFC PATCH] ARM: clocksource: make ARM_GLOBAL_TIMER selectable Grygorii Strashko <grygorii.strashko@ti.com> - 2016-02-26 14:10 +0100
  Re: [RFC PATCH] ARM: clocksource: make ARM_GLOBAL_TIMER selectable Sören Brinkmann <soren.brinkmann@xilinx.com> - 2016-02-26 16:30 +0100

csiph-web