From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
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: Fri, 31 Mar 2017 09:48:02 +0200 [thread overview]
Message-ID: <s5hefxdhop9.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170330215334.zwashvjerpfnkk3u@sirena.org.uk>
On Thu, 30 Mar 2017 23:53:34 +0200,
Mark Brown wrote:
>
> On Wed, Mar 29, 2017 at 02:45:37AM +0000, Kuninori Morimoto wrote:
>
> > To avoid Sound Card crash in (2) case, what we can do now is, add dirty
> > flag on Sound Card, and avoid to open Sound Card.
> > This patch solved this issue.
>
> I think this is a good direction to at least start to mitigate these
> problems (which we really should be doing) and hopefully make it easier
> to do further improvements in future. There's obviously more places
> where we should be checking the flag (controls for example) but they can
> be added later. One thing I would like to see is instead of setting the
> 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.
Takashi
next prev parent reply other threads:[~2017-03-31 7:48 UTC|newest]
Thread overview: 12+ 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 8:47 ` Kuninori Morimoto
2017-03-30 21:53 ` Mark Brown
2017-03-31 0:30 ` Kuninori Morimoto
2017-03-31 7:48 ` Takashi Iwai [this message]
2017-04-03 6:29 ` [alsa-devel] " 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-04 12:42 ` Mark Brown
2017-04-04 12:37 ` Mark Brown
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=s5hefxdhop9.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lars@metafoo.de \
--cc=linux-renesas-soc@vger.kernel.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