From: Arnd Bergmann <arnd@arndb.de>
To: Ashish Jangam <ashish.jangam@kpitcummins.com>
Subject: Re: [PATCH 01/01] MFD: add ADC support to DA9052/53 MFD  core v2
Date: Tue, 21 Feb 2012 12:04:45 +0000
User-Agent: KMail/1.12.2 (Linux/3.3.0-rc1; KDE/4.3.2; x86_64; ; )
Cc: broonie@opensource.wolfsonmicro.com, sameo@linux.intel.com,
        linux-kernel@vger.kernel.org, dajun.chen@diasemi.com
References: <C3AE124F08223B42BC95AEB82F0F6CED2B996CCD@KCHJEXMB01.kpit.com> <1329823897.30549.175.camel@dhruva>
In-Reply-To: <1329823897.30549.175.camel@dhruva>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201202211204.45658.arnd@arndb.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1593
Lines: 28

On Tuesday 21 February 2012, Ashish Jangam wrote:
> > 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()?

No, it's certainly ok to keep using request_threaded_irq, my suggestion was
only in order to improve performance, which it will not do as Mark commented.

I don't any strong reason one way or another.

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