linux-kernel - Re: [PATCH 01/01] MFD: add ADC support to DA9052/53 MFD core v2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1329823897.30549.175.camel@dhruva>
Date:	Tue, 21 Feb 2012 17:01:37 +0530
From:	Ashish Jangam <ashish.jangam@...tcummins.com>
To:	<broonie@...nsource.wolfsonmicro.com>
CC:	<arnd@...db.de>, <sameo@...ux.intel.com>,
	<linux-kernel@...r.kernel.org>, <dajun.chen@...semi.com>
Subject: Re: [PATCH 01/01] MFD: add ADC support to DA9052/53 MFD  core v2

> On Mon, Feb 20, 2012 at 12:07:27PM +0000, Arnd Bergmann wrote:
> 
> > Also, I would recommend using request_irq instead of 
> > request_threaded_irq here because the function only has a single 
> > "complete()" call in it, just like a threaded IRQ handler has. There 
> > is no point going through another thread just to wake up the one that is blocked.
> 
> Actually in this case that won't work as the interrupt is generated by the chip interrupt controller and as the chip is I2C/SPI controlled it is itself threaded and can only generate threaded interrupts as genirq can't get back into hard interrupt context.
> 
> As a result of this restriction when an interrupt handler doesn't care what context it runs in it's better to use request_any_context_irq().
> This will do a normal IRQ when it can but will bind successfully to a threaded IRQ if that's what's provided.

as threaded IRQs are only being used, request_any_context_irq() will
internally call request_threaded_irq() so is there any other need to
replace the current request_threaded_irq()?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/