From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: [PATCH 0/2] ASoC: soc-core: adjust platform for new style
Date: Tue, 11 Sep 2018 06:50:31 +0000 [thread overview]
Message-ID: <8736ug5yb7.wl-kuninori.morimoto.gx@renesas.com> (raw)
Hi Mark
These are v2 of
"ASoC: soc-core: use more generic method to find platform"
but, renamed patch series naming.
v1 patch set had bug under DPCM which can't probe sound card.
The cause was "platform name" management and "component" finding loop.
These patch set solved this issue.
And then, patch set became reduced
Now, ALSA SoC is using snd_soc_dai_link_component for platform
instead of legacy style (= platform_name/platform_of_node/platform).
OTOH, CPU/Codec are finding its DAI by using common snd_soc_find_dai()
function which uses snd_soc_dai_link_component.
Then, of course, we want to use same style for platform.
These patch do it.
Kuninori Morimoto (2):
ASoC: soc-core: manage platform name under snd_soc_init_platform()
ASoC: soc-core: add snd_soc_is_matching_component()
sound/soc/soc-core.c | 73 +++++++++++++++++++++++++++-------------------------
1 file changed, 38 insertions(+), 35 deletions(-)
--
2.7.4
next reply other threads:[~2018-09-11 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 6:50 Kuninori Morimoto [this message]
2018-09-11 6:51 ` [PATCH 1/2] ASoC: soc-core: manage platform name under snd_soc_init_platform() Kuninori Morimoto
2018-09-17 21:21 ` Applied "ASoC: soc-core: manage platform name under snd_soc_init_platform()" to the asoc tree Mark Brown
2018-09-11 6:51 ` [PATCH 2/2] ASoC: soc-core: add snd_soc_is_matching_component() Kuninori Morimoto
2018-09-17 21:21 ` Applied "ASoC: soc-core: add snd_soc_is_matching_component()" to the asoc tree 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=8736ug5yb7.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@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 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.