The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: BUG? genirq: irq 14 uses trigger mode 8; requested 0
Date: Mon, 7 Nov 2016 17:00:25 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1611071658310.3709@nanos> (raw)
In-Reply-To: <3c6f015b-e4d3-5835-fc8e-412fa3f6a481@nvidia.com>

On Mon, 7 Nov 2016, Jon Hunter wrote:
> On 07/11/16 14:59, Mika Westerberg wrote:
> > On Mon, Nov 07, 2016 at 02:40:47PM +0000, Marc Zyngier wrote:
> >> Sorry, missed this discussion entirely, as I was on the other side of
> >> the world. Not having a irq_set_type definitely seems odd (and 
> >> configuring the trigger outside of the IRQ framework is quite ugly).
> >>
> >> Mika, can you please try the following (which is fully untested)?
> >>
> >> diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
> >> index 48e6d84..822a6b8 100644
> >> --- a/arch/x86/kernel/apic/io_apic.c
> >> +++ b/arch/x86/kernel/apic/io_apic.c
> >> @@ -1868,6 +1868,15 @@ static int ioapic_set_affinity(struct irq_data *irq_data,
> >>  	return ret;
> >>  }
> >>  
> >> +static int ioapic_set_type(struct irq_data *data, unsigned int flow_type)
> >> +{
> >> +	/*
> >> +	 * The IOAPIC has already been programmed behind our back,
> >> +	 * just pretend it all went OK, and too bad if it didn't.
> >> +	 */
> >> +	return 0;
> >> +}
> >> +
> >>  static struct irq_chip ioapic_chip __read_mostly = {
> >>  	.name			= "IO-APIC",
> >>  	.irq_startup		= startup_ioapic_irq,
> >> @@ -1876,6 +1885,7 @@ static struct irq_chip ioapic_chip __read_mostly = {
> >>  	.irq_ack		= irq_chip_ack_parent,
> >>  	.irq_eoi		= ioapic_ack_level,
> >>  	.irq_set_affinity	= ioapic_set_affinity,
> >> +	.irq_set_type		= ioapic_set_type,
> >>  	.flags			= IRQCHIP_SKIP_SET_WAKE,
> >>  };
> > 
> > Thanks! This fixes the problem for me.
> 
> Good to know. The more I think about this, the more I wonder if we
> should have a dummy 'set_type' as this is just hiding the issue. If the
> original warning does not impact the overall behaviour (ie. interrupts
> still working) then may be it is legitimate as far as gen-irq is concerned?

No. We don't want a dummy set_type to paper over the issue. As Mika
correctly figured out that the ioapic is already configured, but it does
not propagate it to the irq descriptor. That wants to be fixed. I'll have a
look.

Thanks,

	tglx

  reply	other threads:[~2016-11-07 16:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-01 13:02 BUG? genirq: irq 14 uses trigger mode 8; requested 0 Mika Westerberg
2016-11-01 14:24 ` Jon Hunter
2016-11-01 14:44   ` Mika Westerberg
2016-11-07 11:49     ` Mika Westerberg
2016-11-07 13:32       ` Jon Hunter
2016-11-07 14:40         ` Marc Zyngier
2016-11-07 14:59           ` Mika Westerberg
2016-11-07 15:50             ` Jon Hunter
2016-11-07 16:00               ` Thomas Gleixner [this message]
2016-11-07 19:29                 ` Thomas Gleixner
2016-11-08  9:17                   ` Mika Westerberg
2016-11-08 14:22                   ` [tip:irq/urgent] genirq: Use irq type from irqdata instead of irqdesc tip-bot for Thomas Gleixner

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=alpine.DEB.2.20.1611071658310.3709@nanos \
    --to=tglx@linutronix.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mika.westerberg@linux.intel.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