All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] pcmcia: irq probe can be done without risking an IRQ storm
Date: Thu, 26 Apr 2007 21:06:31 +0200	[thread overview]
Message-ID: <1177614391.25960.38.camel@localhost.localdomain> (raw)
In-Reply-To: <1177608704.25960.21.camel@localhost.localdomain>

On Thu, 2007-04-26 at 19:31 +0200, Thomas Gleixner wrote:
> > >  #ifdef CONFIG_PCMCIA_PROBE
> > > +	if (!(req->Attributes & IRQ_HANDLE_PRESENT))
> > > +		type |= IRQ_NOAUTOEN;
> > > +
> > >  	if (s->irq.AssignedIRQ != 0) {
> > >  		/* If the interrupt is already assigned, it must be the same */
> > >  		irq = s->irq.AssignedIRQ;
> > 
> > alpha:
> > 
> > drivers/pcmcia/pcmcia_resource.c: In function 'pcmcia_request_irq':
> > drivers/pcmcia/pcmcia_resource.c:816: error: 'IRQ_NOAUTOEN' undeclared (first use in this function)
> > drivers/pcmcia/pcmcia_resource.c:816: error: (Each undeclared identifier is reported only once
> > drivers/pcmcia/pcmcia_resource.c:816: error: for each function it appears in.)
> > 
> > Problem is, IRQ_NOAUTOEN is a generic-irq thing, so architectures which
> > don't use generic-irqs break.  And it's defined in linux/irq.h which
> > (stupidly) cannot be included in generic code.
> 
> Hrmpf. We need a IRQF_NOAUTOEN, which can be handed to reqeust_irq().
> 
> I cook a patch.

Not that simple. For non shared interrupts it is straight forward, but
for shared ones we have to decide, whether we 

A) reject the request
B) disable the interrupt and rely on the caller, that it reenables it
C) ignore it

sorted by ugliness order :)

A) is definitely the most safe bet, but B) might work as well.

	tglx



      reply	other threads:[~2007-04-26 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 13:09 [PATCH] pcmcia: irq probe can be done without risking an IRQ storm Alan Cox
2007-04-26  4:18 ` Andrew Morton
2007-04-26 17:31   ` Thomas Gleixner
2007-04-26 19:06     ` Thomas Gleixner [this message]

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=1177614391.25960.38.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.