From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Lars-Peter <lars@metafoo.de>, Simon <horms@verge.net.au>
Subject: Re: [alsa-devel] [RFC][PATCH] ASoC: soc-core: verify Sound Card normality
Date: Tue, 4 Apr 2017 13:37:53 +0100 [thread overview]
Message-ID: <20170404123753.7tqnrrea4cce4tcp@sirena.org.uk> (raw)
In-Reply-To: <s5hefxdhop9.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
On Fri, Mar 31, 2017 at 09:48:02AM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > flag directly when we see a problem call a function to do it. That way
> > if we want to improve things in the future we can do that without having
> > to update the callers again.
> BTW, ALSA core has snd_card_disconnect() that does this kind of
> shut-up from user-space. It was introduced for hot-unplug, but
> basically unbinding is the software hot-unplug. So, if ASoC won't
> rebind a once-unbound component, you can simply call
> snd_card_disconnect() at the component unbinding time to assure that
> no further user actions can be done.
Ah, that's exactly the sort of improvement I was thinking of!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-04-04 12:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 2:45 [RFC][PATCH] ASoC: soc-core: verify Sound Card normality Kuninori Morimoto
2017-03-29 7:29 ` Geert Uytterhoeven
2017-03-29 7:29 ` Geert Uytterhoeven
2017-03-29 8:47 ` Kuninori Morimoto
2017-03-30 21:53 ` Mark Brown
2017-03-31 0:30 ` Kuninori Morimoto
2017-03-31 7:48 ` [alsa-devel] " Takashi Iwai
2017-04-03 6:29 ` Kuninori Morimoto
2017-04-03 6:41 ` Takashi Iwai
2017-04-03 8:26 ` Kuninori Morimoto
2017-04-03 8:37 ` Takashi Iwai
2017-04-03 8:37 ` Takashi Iwai
2017-04-04 12:42 ` [alsa-devel] " Mark Brown
2017-04-04 12:37 ` Mark Brown [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=20170404123753.7tqnrrea4cce4tcp@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lars@metafoo.de \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.