From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org, lgirdwood@gmail.com,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
bgoswami@codeaurora.org, rohitkr@codeaurora.org,
vkoul@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: core: add support to card re-bind/unbind using component framework
Date: Thu, 12 Jul 2018 16:58:17 +0100 [thread overview]
Message-ID: <20180712155817.GG10369@sirena.org.uk> (raw)
In-Reply-To: <s5hsh4o8nq1.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
On Thu, Jul 12, 2018 at 05:42:30PM +0200, Takashi Iwai wrote:
> Pierre-Louis Bossart wrote:
> > On 7/11/18 3:43 AM, Srinivas Kandagatla wrote:
> > > This patch aims at add achieving dynamic behaviour of audio card when
> > > the dependent components disappear and reappear.
> > Humm, no real comment on this patch proper but rather on how userspace
> > would deal with this dynamic behavior?
> > We had similar opens when we worked on the BYT/CHT HDMI stuff and
> > ended-up with quite a few issues in userspace (PulseAudio mainly)
> > related to dynamic behavior at the kernel level as a result of
> > plug/unplug. Also not sure how an Android HAL would deal with a card
> > disappearing temporarily if DSP resources become unavailable or
> > unresponsive. Any thoughts or guidance you might think of?
> Was the card-level register / unregister really problematic with PA?
> It's basically similar as the hotplug like USB, so I thought it would
> work as is.
Yeah, I'd expect normal desktop stuff to be able to cope with this due
to physically hotpluggable hardware. The main use case for doing things
like this with module unload is in a development context where hopefully
people can also arrange to use a userspace that can cope or to do
whatever to reset it, any limitations in some userspace shouldn't prevent
people from having the facility available.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-12 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 8:43 Srinivas Kandagatla
2018-07-12 10:59 ` Vinod
2018-07-12 12:02 ` Srinivas Kandagatla
2018-07-12 12:39 ` Vinod
[not found] ` <68715fbc-9447-dfaf-3fe5-4200684c2cbc@linux.intel.com>
2018-07-12 15:42 ` [alsa-devel] " Takashi Iwai
2018-07-12 15:54 ` Pierre-Louis Bossart
2018-07-12 16:17 ` Mark Brown
2018-07-12 15:58 ` Mark Brown [this message]
2018-07-12 16:43 ` Vinod
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=20180712155817.GG10369@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rohitkr@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vkoul@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
Powered by JetHome