From: Jerome Brunet <jbrunet@baylibre.com>
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Kevin Hilman <khilman@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: [PATCH 0/2] ASoC: soc-core: update dai_link init
Date: Wed, 26 Jun 2019 15:36:15 +0200 [thread overview]
Message-ID: <20190626133617.25959-1-jbrunet@baylibre.com> (raw)
My initial goal with this patchset was to allow a dai_link to have no
no platform component, instead of having dummy by default.
However, when rebasing, I discovered that Kuninori Morimoto had recently
done that in a different way :)
I am still submitting my change since it should allow multiple platform
components on a dai_link, which is one of the FIXME note in soc-core.
I have also added a check on the codecs component availability to align
on what was done for platforms and cpus
Jerome Brunet (2):
ASoC: soc-core: defer card registration if codec component is missing
ASoC: soc-core: support dai_link with platforms_num != 1
include/sound/soc.h | 6 ++++
sound/soc/soc-core.c | 72 +++++++++++++++++++++-----------------------
2 files changed, 41 insertions(+), 37 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-26 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 13:36 Jerome Brunet [this message]
2019-06-26 13:36 ` [PATCH 1/2] ASoC: soc-core: defer card registration if codec component is missing Jerome Brunet
2019-06-26 21:20 ` [alsa-devel] " Pierre-Louis Bossart
2019-06-26 13:36 ` [PATCH 2/2] ASoC: soc-core: support dai_link with platforms_num != 1 Jerome Brunet
2019-06-26 23:44 ` Kuninori Morimoto
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=20190626133617.25959-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).