linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Denis Carikli <denis@eukrea.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Fabio Estevam <festevam@gmail.com>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	Hartmut Knaack <knaack.h@gmx.de>
Cc: "Eric Bénard" <eric@eukrea.com>,
	"Sascha Hauer" <kernel@pengutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	"Lee Jones" <lee.jones@linaro.org>,
	linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Markus Pargmann" <mpa@pengutronix.de>
Subject: Re: [PATCH v3 3/6] iio: adc: fsl,imx25-gcq driver
Date: Mon, 23 Jun 2014 19:13:14 +0100	[thread overview]
Message-ID: <53A86E3A.6000400@kernel.org> (raw)
In-Reply-To: <53A85922.1000209@eukrea.com>

On 23/06/14 17:43, Denis Carikli wrote:
> On 06/21/2014 12:51 PM, Jonathan Cameron wrote:
>>> +static irqreturn_t mx25_gcq_irq(int irq, void *data)
>>> +{
>>> +    struct mx25_gcq_priv *priv = data;
>>> +    u32 stats;
>> Not that much in here, but perhaps still makes sense for this to be a
>> threaded
>> irq?
> What would be the advantage of converting it to be a threaded IRQ?
>
> I guess that there will be no use of IRQF_SHARED and that only this driver will have to handle the GCQ IRQ in the future.
>
Fair enough.  Was more of an idle thought that anything else!





  reply	other threads:[~2014-06-23 18:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16  9:28 [PATCH v3 1/6] mfd: fsl imx25 Touchscreen ADC driver Denis Carikli
2014-06-16  9:28 ` [PATCH v3 2/6] input: touchscreen: imx25 tcq driver Denis Carikli
     [not found] ` <1402910933-20534-1-git-send-email-denis-fO0SIAKYzcbQT0dZR+AlfA@public.gmane.org>
2014-06-16  9:28   ` [PATCH v3 3/6] iio: adc: fsl,imx25-gcq driver Denis Carikli
     [not found]     ` <1402910933-20534-3-git-send-email-denis-fO0SIAKYzcbQT0dZR+AlfA@public.gmane.org>
2014-06-21 10:45       ` Jonathan Cameron
2014-06-21 10:51       ` Jonathan Cameron
2014-06-23 16:43         ` Denis Carikli
2014-06-23 18:13           ` Jonathan Cameron [this message]
2014-06-16  9:28   ` [PATCH v3 4/6] ARM: dts: imx25: Add TSC and ADC support Denis Carikli
2014-06-16  9:28   ` [PATCH v3 5/6] ARM: dts: imx25: mbimxsd25: Add touchscreen support Denis Carikli
2014-06-16  9:28   ` [PATCH v3 6/6] ARM: imx_v4_v5_defconfig: Add I.MX25 Touchscreen controller and ADC support Denis Carikli
2014-06-16 11:26   ` [PATCH v3 1/6] mfd: fsl imx25 Touchscreen ADC driver Lee Jones
2014-06-16 15:55     ` Denis Carikli

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=53A86E3A.6000400@kernel.org \
    --to=jic23@kernel.org \
    --cc=denis@eukrea.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric@eukrea.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=mpa@pengutronix.de \
    --cc=pmeerw@pmeerw.net \
    --cc=sameo@linux.intel.com \
    --cc=shawn.guo@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).