From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: jianqun <xjq@rock-chips.com>,
broonie@kernel.org, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.de, tbleung@chromium.org, dgreid@chromium.org,
kevin.strasser@intel.com, swarren@nvidia.com,
ralph.birt@maximintegrated.com
Cc: alsa-devel@alsa-project.org, heiko@sntech.de,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: max98090 add irq valid check
Date: Wed, 30 Jul 2014 17:21:42 +0300 [thread overview]
Message-ID: <53D8FF76.7090707@linux.intel.com> (raw)
In-Reply-To: <1406710457-6195-1-git-send-email-xjq@rock-chips.com>
Hi
On 07/30/2014 11:54 AM, jianqun wrote:
> From: Jianqun <xjq@rock-chips.com>
>
> Since IRQ pin from max98090 may NC, the irq number will be zero, that is
> invalid for request_threaded_irq, so just add irq valid check there.
>
> Since hardware may not MUST to use IRQ pin of max98090 as jack detect, the
> driver can work well without it, can report jack trigger to CPU by a GPIO.
>
> But here driver will register fail caused by failed to request irq.
>
> Signed-off-by: Jianqun <xjq@rock-chips.com>
> ---
> sound/soc/codecs/max98090.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/sound/soc/codecs/max98090.c b/sound/soc/codecs/max98090.c
> index 566919c..9dc0e8c 100644
> --- a/sound/soc/codecs/max98090.c
> +++ b/sound/soc/codecs/max98090.c
> @@ -2478,12 +2478,14 @@ static int max98090_probe(struct snd_soc_codec *codec)
> /* Register for interrupts */
> dev_dbg(codec->dev, "irq = %d\n", max98090->irq);
>
> - ret = request_threaded_irq(max98090->irq, NULL,
> - max98090_interrupt, IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> - "max98090_interrupt", codec);
> - if (ret < 0) {
> - dev_err(codec->dev, "request_irq failed: %d\n",
> - ret);
> + if (max98090->irq) {
> + ret = request_threaded_irq(max98090->irq, NULL,
> + max98090_interrupt, IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> + "max98090_interrupt", codec);
> + if (ret < 0) {
> + dev_err(codec->dev, "request_irq failed: %d\n",
> + ret);
> + }
> }
>
Remember to add also "return ret;" at the end of if () {} in case
request_threaded_irq() fails since code should not continue probing now
after adding a test for valid irq.
Should the if (max98090->irq) test be >0? I'm not sure is there
possibility that can i2c->irq actually pass both -1 and 0 depending how
struct i2c_board_info etc are initialized?
I forgot that I have a fix changing request_threaded_irq() to
devm_request_threaded_irq() so you should redo your patch on top of
for-next branch of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git.
--
Jarkko
prev parent reply other threads:[~2014-07-30 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 1:50 [PATCH] ASoC: max98090 not need to return fail if fail to request hpdet irq jianqun
2014-07-30 6:29 ` Jarkko Nikula
2014-07-30 9:00 ` Jianqun
2014-07-30 8:54 ` [PATCH] ASoC: max98090 add irq valid check jianqun
2014-07-30 14:21 ` Jarkko Nikula [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=53D8FF76.7090707@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dgreid@chromium.org \
--cc=heiko@sntech.de \
--cc=kevin.strasser@intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=ralph.birt@maximintegrated.com \
--cc=swarren@nvidia.com \
--cc=tbleung@chromium.org \
--cc=tiwai@suse.de \
--cc=xjq@rock-chips.com \
/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).