[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1704151153280.2327@nanos>
Date:   Sat, 15 Apr 2017 11:54:50 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     David Howells <dhowells@...hat.com>
cc:     LKML <linux-kernel@...r.kernel.org>, gnomes@...rguk.ukuu.org.uk,
        gregkh@...uxfoundation.org,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
        Jens Rottmann <JRottmann@...PERTEmbedded.de>,
        Andres Salomon <dilinger@...ued.net>
Subject: Re: [PATCH 06/38] Annotate hardware config module parameters in
 drivers/clocksource/
On Sat, 15 Apr 2017, David Howells wrote:
> Thomas Gleixner <tglx@...utronix.de> wrote:
> 
> > > Btw, is it possible to use IRQ grants to prevent a device that has limited
> > > IRQ options from being drivable?
> > 
> > What do you mean with 'IRQ grants' ?
> 
> request_irq().
I still can't parse the sentence above. If request_irq() fails the device
initialization fails. If you request the wrong irq then request_irq() might
succeed but the device won't work.
Thanks,
	tglx
Powered by blists - more mailing lists
 
