From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Lars-Peter Clausen <lars@metafoo.de>,
Vinod Koul <vinod.koul@intel.com>, Takashi Iwai <tiwai@suse.de>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-renesas-soc@vger.kernel.org, Simon <horms@verge.net.au>
Subject: Re: Question about struct snd_soc_dai() :: cpu_dai->codec
Date: Fri, 29 Jul 2016 09:30:19 +0900 [thread overview]
Message-ID: <579AA39B.5030100@sakamocchi.jp> (raw)
In-Reply-To: <579A6C1B.2060904@metafoo.de>
Lars,
On Jul 29 2016 05:33, Lars-Peter Clausen wrote:
> Hotplug is something that always pops up sooner or later. E.g. if someone
> puts a ASoC supported CODEC on a hot-pluggable device (maybe USB) we
> don't want to duplicate the code, but be able to reuse.
(A bit to sidetrack)
To me, it's unclear for devices on USB. When ALSA SoC part supports
these devices, what is the scenario you assumed? In short, assuming we
put codes to ALSA SoC part, what is the shape of the corresponding
devices and links of pairs of endpoints? Additionally, in this case,
what codes are able to be reused?
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2016-07-29 0:30 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 5:41 Question about struct snd_soc_dai() :: cpu_dai->codec Kuninori Morimoto
2016-07-26 5:41 ` Kuninori Morimoto
2016-07-27 3:21 ` [alsa-devel] " Vinod Koul
2016-07-27 3:42 ` Kuninori Morimoto
2016-07-27 3:42 ` Kuninori Morimoto
2016-07-27 5:57 ` Takashi Iwai
2016-07-27 6:36 ` Kuninori Morimoto
2016-07-27 6:36 ` Kuninori Morimoto
2016-07-27 17:21 ` Vinod Koul
2016-07-27 18:04 ` Mark Brown
2016-07-27 18:11 ` Takashi Iwai
2016-07-27 18:22 ` Mark Brown
2016-07-27 20:22 ` Takashi Iwai
2016-07-28 3:46 ` Vinod Koul
2016-07-28 20:33 ` Lars-Peter Clausen
2016-07-28 20:42 ` Takashi Iwai
2016-07-28 20:43 ` Lars-Peter Clausen
2016-07-28 20:44 ` Mark Brown
2016-07-29 0:30 ` Takashi Sakamoto [this message]
2016-07-29 9:07 ` Lars-Peter Clausen
2016-07-29 16:07 ` Vinod Koul
2016-07-29 20:41 ` Takashi Iwai
2016-07-29 21:45 ` Takashi Sakamoto
2016-07-29 22:08 ` Mark Brown
2016-08-04 3:17 ` Takashi Sakamoto
2016-08-04 10:28 ` Mark Brown
2016-08-04 12:12 ` Takashi Sakamoto
2016-08-04 12:27 ` Takashi Iwai
2016-08-04 13:39 ` Takashi Sakamoto
2016-08-04 13:52 ` Takashi Iwai
2016-07-28 20:24 ` [alsa-devel] " Lars-Peter Clausen
2016-07-29 2:24 ` Kuninori Morimoto
2016-07-29 2:24 ` Kuninori Morimoto
2016-07-29 9:01 ` Lars-Peter Clausen
2016-07-29 14:41 ` Mark Brown
2016-08-01 3:45 ` Kuninori Morimoto
2016-08-01 3:45 ` [alsa-devel] " Kuninori Morimoto
2016-08-02 6:47 ` Kuninori Morimoto
2016-08-02 6:47 ` [alsa-devel] " Kuninori Morimoto
2016-08-03 19:32 ` Lars-Peter Clausen
2016-08-04 2:38 ` Kuninori Morimoto
2016-08-04 2:38 ` [alsa-devel] " Kuninori Morimoto
2016-08-04 8:21 ` Lars-Peter Clausen
2016-08-04 8:21 ` [alsa-devel] " Lars-Peter Clausen
2016-08-04 20:56 ` Mark Brown
2016-08-05 7:29 ` Kuninori Morimoto
2016-08-04 20: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=579AA39B.5030100@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--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=lgirdwood@gmail.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.com \
/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.