mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
	linux-next@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP systems
Date: Mon, 7 Jul 2008 22:17:23 +0200	[thread overview]
Message-ID: <200807072217.24590.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.55.0807072054310.20615@cliff.in.clinika.pl>

On Monday, 7 of July 2008, Maciej W. Rozycki wrote:
> On Mon, 7 Jul 2008, Rafael J. Wysocki wrote:
> 
> > @@ -1714,12 +1721,14 @@ static inline void __init check_timer(vo
> >  		apic2 = apic1;
> >  	}
> >  
> > -	replace_pin_at_irq(0, 0, 0, apic1, pin1);
> > -	apic1 = 0;
> > -	pin1 = 0;
> > -	setup_timer_IRQ0_pin(apic1, pin1, cfg->vector);
> > +	if (disable_irq0_through_ioapic) {
> > +		clear_IO_APIC_pin(apic1, pin1);
> > +	} else {
> > +		replace_pin_at_irq(0, 0, 0, apic1, pin1);
> > +		apic1 = 0;
> > +		pin1 = 0;
> > +		setup_timer_IRQ0_pin(apic1, pin1, cfg->vector);
> >  
> > -	if (pin1 != -1) {
> >  		/*
> >  		 * Ok, does IRQ0 through the IOAPIC work?
> >  		 */
> 
>  This is completely broken -- you cannot blindly assume IRQ0 is wired to
> the pin #0 of the I/O APIC #0.  You have to respect routing information
> provided by the system.
> 
>  Ingo, from the sequence above, I gather this code is currently in the 
> tree:
> 
> -	replace_pin_at_irq(0, 0, 0, apic1, pin1);
> -	apic1 = 0;
> -	pin1 = 0;
> 
> Please revert the change which introduced it.  While I recall posting a
> patch which added code like this, I clearly stated it was solely for
> diagnostics of Rafael's system and not to apply to any tree.

Shouldn't the setup_timer_IRQ0_pin(apic1, pin1, cfg->vector) be removed as
well?

Rafael

  reply	other threads:[~2008-07-07 20:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  0:12 Maciej W. Rozycki
2008-07-01  0:17 ` Matthew Garrett
2008-07-01  8:46   ` Ingo Molnar
2008-07-01 19:58     ` Rafael J. Wysocki
2008-07-01 20:24       ` Ingo Molnar
2008-07-04 21:21         ` Rafael J. Wysocki
2008-07-06 23:02         ` Rafael J. Wysocki
2008-07-07  1:19           ` Rafael J. Wysocki
2008-07-07  7:17             ` Ingo Molnar
2008-07-07  7:36               ` Ingo Molnar
2008-07-07 12:24                 ` Rafael J. Wysocki
2008-07-07 11:41               ` Maciej W. Rozycki
2008-07-07 12:23                 ` Rafael J. Wysocki
2008-07-07 14:01                   ` Maciej W. Rozycki
2008-07-07 18:03                     ` Rafael J. Wysocki
2008-07-07 20:10                       ` Maciej W. Rozycki
2008-07-07 20:31                         ` Rafael J. Wysocki
2008-07-07 21:39                           ` Maciej W. Rozycki
2008-07-07 22:10                             ` Rafael J. Wysocki
2008-07-07 12:28                 ` Rafael J. Wysocki
2008-07-07 17:10                   ` Maciej W. Rozycki
2008-07-07 17:51                     ` Ray Lee
2008-07-07 18:09                     ` Rafael J. Wysocki
2008-07-07 19:59             ` Maciej W. Rozycki
2008-07-07 20:17               ` Rafael J. Wysocki [this message]
2008-07-07 21:38                 ` Maciej W. Rozycki
2008-07-07 20:30               ` Maciej W. Rozycki
2008-07-07  3:54 ` Zhao Forrest
2008-07-07 12:34   ` Rafael J. Wysocki
2008-07-08 11:24 ` Andreas Herrmann
2008-07-08 14:39   ` Maciej W. Rozycki
2008-07-08 15:27   ` Rafael J. Wysocki
2008-07-08 16:25     ` Maciej W. Rozycki
2008-07-08 16:54       ` Rafael J. Wysocki
     [not found] <fa.OuKI5CNmq3HqeBQCfWOUtrq4+oA@ifi.uio.no>
2008-07-03  5:44 ` Robert Hancock

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=200807072217.24590.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=andi@firstfloor.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®