From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
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 17:17:28 +0100 [thread overview]
Message-ID: <20180712161728.GH10369@sirena.org.uk> (raw)
In-Reply-To: <0f437d5d-5857-a608-8d8f-345c832a0ee1@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
On Thu, Jul 12, 2018 at 10:54:05AM -0500, Pierre-Louis Bossart wrote:
> On 7/12/18 10:42 AM, Takashi Iwai wrote:
> > It's basically similar as the hotplug like USB, so I thought it would
> > work as is.
> Such transitions would probably not break userspace but they result from an
> explicit user action. The DSP going off and back is less clear, you might
> want the system to wait before triggering re-routing to different outputs,
> etc.
> Again I wasn't trying to push back but rather ask what the side effects of
> this patch might be for userspace.
For userspace it's just another reason why a card might hotplug, it
doesn't make much difference - this doesn't add hotplugging of the DSP,
it just supports components getting removed like we used to. If someone
decides to start randomly rebooting their DSP that's probably going to
be disruptive no matter what.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-12 16:17 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 [this message]
2018-07-12 15:58 ` Mark Brown
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=20180712161728.GH10369@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