From: Takashi Iwai <tiwai@suse.de>
To: "Opensource [Adam Thomson]" <Adam.Thomson.Opensource@diasemi.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Support Opensource <Support.Opensource@diasemi.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: da7218: Enable mic level detection reporting to user-space
Date: Thu, 03 Dec 2015 12:37:25 +0100 [thread overview]
Message-ID: <s5h8u5bn4p6.wl-tiwai@suse.de> (raw)
In-Reply-To: <2E89032DDAA8B9408CB92943514A0337D460FA37@SW-EX-MBX01.diasemi.com>
On Thu, 03 Dec 2015 12:15:41 +0100,
Opensource [Adam Thomson] wrote:
>
> On December 03, 2015 10:56, Takashi Iwai wrote:
>
> > > This patch adds support to the codec driver to handle mic level
> > > detect related IRQs, and report these to user-space using a uevent
> > > variable.
> >
> > Is the uevent the best way for this?
> >
> >
> > thanks,
> >
> > Takashi
>
> Well originally I was using an input device mechanism to report to user-space,
> albeit using KEY_VOICECOMMAND, which Mark mentioned wasn't correct for this
> scenario, which was fair enough. He also mentioned that there had been a general
> push back on using input devices so that code was dropped. See thread below:
>
> https://lkml.org/lkml/2015/11/10/347
>
> uevent seemed like the simplest solution to report this event, and allow
> user-space to act based on it. As mentioned before though, I am open to
> suggestions if there's a better way.
I'm not strongly opposing to uevent as long as it's well considered.
But then please describe how it's notified properly and why it was
chosen. The patch changelog has enough free room to write more
details, fortunately. Tell more your story for Christmas :)
In general, you can use an ALSA control notification for this kind of
event. But it also depends on the user-space side. With alsa-lib,
it's pretty easy to use, while with tinyalsa that lacks of the notifier
handling, you'd need to implement more code there.
For a plug/unplug type event, we have a generic jack layer, but this
doesn't seem fitting perfectly, either.
Takashi
>
> > >
> > > Signed-off-by: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
> > > ---
> > > sound/soc/codecs/da7218.c | 19 ++++++++++++++-----
> > > 1 file changed, 14 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/sound/soc/codecs/da7218.c b/sound/soc/codecs/da7218.c
> > > index 4fee7ae..752ed04 100644
> > > --- a/sound/soc/codecs/da7218.c
> > > +++ b/sound/soc/codecs/da7218.c
> > > @@ -2202,6 +2202,16 @@ int da7218_hpldet(struct snd_soc_codec *codec,
> > struct snd_soc_jack *jack)
> > > }
> > > EXPORT_SYMBOL_GPL(da7218_hpldet);
> > >
> > > +static void da7218_micldet_irq(struct snd_soc_codec *codec)
> > > +{
> > > + char *envp[] = {
> > > + "EVENT=MIC_LEVEL_DETECT",
> > > + NULL,
> > > + };
> > > +
> > > + kobject_uevent_env(&codec->dev->kobj, KOBJ_CHANGE, envp);
> > > +}
> > > +
> > > static void da7218_hpldet_irq(struct snd_soc_codec *codec)
> > > {
> > > struct da7218_priv *da7218 = snd_soc_codec_get_drvdata(codec);
> > > @@ -2232,6 +2242,10 @@ static irqreturn_t da7218_irq_thread(int irq, void
> > *data)
> > > if (!status)
> > > return IRQ_NONE;
> > >
> > > + /* Mic level detect */
> > > + if (status & DA7218_LVL_DET_EVENT_MASK)
> > > + da7218_micldet_irq(codec);
> > > +
> > > /* HP detect */
> > > if (status & DA7218_HPLDET_JACK_EVENT_MASK)
> > > da7218_hpldet_irq(codec);
> > > @@ -2936,11 +2950,6 @@ static int da7218_probe(struct snd_soc_codec *codec)
> > > }
> > >
> > > if (da7218->irq) {
> > > - /* Mask off mic level events, currently not handled */
> > > - snd_soc_update_bits(codec, DA7218_EVENT_MASK,
> > > - DA7218_LVL_DET_EVENT_MSK_MASK,
> > > - DA7218_LVL_DET_EVENT_MSK_MASK);
> > > -
> > > ret = devm_request_threaded_irq(codec->dev, da7218->irq, NULL,
> > > da7218_irq_thread,
> > > IRQF_TRIGGER_LOW |
> > IRQF_ONESHOT,
> > > --
> > > 1.9.3
> > >
> > >
next prev parent reply other threads:[~2015-12-03 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 10:45 Adam Thomson
2015-12-03 10:55 ` Takashi Iwai
2015-12-03 11:15 ` Opensource [Adam Thomson]
2015-12-03 11:37 ` Takashi Iwai [this message]
2015-12-03 14:45 ` Opensource [Adam Thomson]
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=s5h8u5bn4p6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=Support.Opensource@diasemi.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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
all inboxes | Powered by JetHome®