public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	x86@kernel.org
Subject: Re: Ask help about pre_init_apic_IRQ0()
Date: Thu, 11 Sep 2014 17:03:01 +0300	[thread overview]
Message-ID: <1410444181.7023.25.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1409111225380.4178@nanos>

On Thu, 2014-09-11 at 14:58 +0200, Thomas Gleixner wrote:
[]

> According to the MID code the apbt horror is only used for moorestown.
> Medfield and later use the local apic timer without the apbt nonsense.
> 
> The best thing we can do is to drop moorestown support and get rid of
> that apbt nonsense alltogether.

Alan Cox removed Moorestown (as a platform) support in 2012 IIRC.
So, AFAIK you may safely remove those leftovers.

> I don't think anyone deeply cares about it not being supported from
> 3.18 on. The number of devices which sport a moorestown should be
> pretty limited and the only relevant use case of those is to act as a
> pocket heater with short battery life time. Its pretty pointless to
> update kernels on pocket heaters except for bragging reasons.
> 
> If someone at Intel really thinks that we need to keep moorestown
> alive for other than documentary and sentimental reasons, then we can
> move the apbt setup to x86_init.timers.setup_percpu_clockev(). At that
> point the IOAPIC is setup already, so it should just work. Untested
> patch below.

Suddenly I have one priority work to do and my Medfield tablet doesn't
boot by some reason. I would try to test it as soon as I can.

> 
> Thanks,
> 
> 	tglx
> 
> ------------------
> Index: linux/arch/x86/platform/intel-mid/intel-mid.c
> ===================================================================
> --- linux.orig/arch/x86/platform/intel-mid/intel-mid.c
> +++ linux/arch/x86/platform/intel-mid/intel-mid.c
> @@ -81,26 +81,34 @@ static unsigned long __init intel_mid_ca
>  	return 0;
>  }
>  
> +static void __init intel_mid_setup_bp_timer(void)
> +{
> +	apbt_time_init();
> +	setup_boot_APIC_clock();
> +}
> +
>  static void __init intel_mid_time_init(void)
>  {
>  	sfi_table_parse(SFI_SIG_MTMR, NULL, NULL, sfi_parse_mtmr);
> +
>  	switch (intel_mid_timer_options) {
>  	case INTEL_MID_TIMER_APBT_ONLY:
>  		break;
>  	case INTEL_MID_TIMER_LAPIC_APBT:
> -		x86_init.timers.setup_percpu_clockev = setup_boot_APIC_clock;
> +		/* Use apbt and local apic */
> +		x86_init.timers.setup_percpu_clockev = intel_mid_setup_bp_timer;
>  		x86_cpuinit.setup_percpu_clockev = setup_secondary_APIC_clock;
> -		break;
> +		return;
>  	default:
>  		if (!boot_cpu_has(X86_FEATURE_ARAT))
>  			break;
> +		/* Lapic only, no apbt */
>  		x86_init.timers.setup_percpu_clockev = setup_boot_APIC_clock;
>  		x86_cpuinit.setup_percpu_clockev = setup_secondary_APIC_clock;
>  		return;
>  	}
> -	/* we need at least one APB timer */
> -	pre_init_apic_IRQ0();
> -	apbt_time_init();
> +
> +	x86_init.timers.setup_percpu_clockev = apbt_time_init;
>  }
>  
>  static void intel_mid_arch_setup(void)


-- 
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy


  reply	other threads:[~2014-09-11 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  8:44 Ask help about pre_init_apic_IRQ0() Jiang Liu
2014-09-11  8:53 ` Mika Westerberg
2014-09-11  9:08   ` Andy Shevchenko
2014-09-11 23:17     ` David Cohen
2014-09-11 12:58 ` Thomas Gleixner
2014-09-11 14:03   ` Andy Shevchenko [this message]
2014-09-11 14:35     ` Thomas Gleixner
2014-09-11 15:15       ` Andy Shevchenko
2014-09-11 21:59         ` Thomas Gleixner
2014-09-12  8:19           ` Andy Shevchenko
2014-09-12  8:26             ` Thomas Gleixner
2014-09-12  9:25               ` Andy Shevchenko

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=1410444181.7023.25.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=jiang.liu@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox