All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: Applied "ASoC: soc-core: add .num_platform for dai_link" to the asoc tree
Date: 24 Jan 2019 11:14:35 +0900	[thread overview]
Message-ID: <87o986stfw.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20190122203637.GM7579@sirena.org.uk>


Hi Mark

> >    I think "platform" settings is not mandatory in this case.
> >    So we can allow "no platform" in modern style.
> >    But what do you think ?
> 
> Yes, I think that's fine especially when you start looking at things
> like CODEC<->CODEC links.

Yeah, indeed.
I will investigate it

> > 2) On legacy style, if sound card dirver doesn't indicate specific "platform",
> >    then, "snd-soc-dummy" platform will be selected automatically.
> >    It is implemented on snd_soc_init_platform() today.
> >    In modern style, we can force to indicate necessary platform,
> >    or, not allow implicit snd-soc-dummy platform selection.
> >    But what do you think ?
> 
> IIRC the goal with dummy was twofold.  One was to avoid having to list
> dummy in things like DT bindings where we don't want platform specifics
> (but I'm sure we could arrange something there).  The other was to
> ensure that we always have something there so we don't need to test for
> platform operations being there outside of init which again we could
> deal with I think.

Thanks.
Current implementation is that all CPU/Codec/Platform are
listed component, and it is selected via dai_link settings, I think.
So, maybe above concerns are no longer needed.
But, I want to investigate more.

Best regards
---
Kuninori Morimoto

  reply	other threads:[~2019-01-24  2:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  0:32 [PATCH 0/6] ASoC: soc-core: cleanup and platform Kuninori Morimoto
2019-01-21  0:32 ` [PATCH 1/6] ASoC: soc-core: add .num_platform for dai_link Kuninori Morimoto
2019-01-21 19:20   ` Applied "ASoC: soc-core: add .num_platform for dai_link" to the asoc tree Mark Brown
2019-01-22  2:10     ` Kuninori Morimoto
2019-01-22 20:36       ` Mark Brown
2019-01-24  2:14         ` Kuninori Morimoto [this message]
2019-01-21  0:32 ` [PATCH 2/6] ASoC: soc-core: add new snd_soc_flush_all_delayed_work() Kuninori Morimoto
2019-01-21  0:32 ` [PATCH 3/6] ASoC: soc-core: merge card resources cleanup method Kuninori Morimoto
2019-01-21  0:32 ` [PATCH 4/6] ASoC: soc-core: reduce if/else nest on soc_probe_link_dais Kuninori Morimoto
2019-01-21  0:32 ` [PATCH 5/6] ASoC: soc-core: add soc_cleanup_component() Kuninori Morimoto
2019-01-21 19:20   ` Applied "ASoC: soc-core: add soc_cleanup_component()" to the asoc tree Mark Brown
2019-01-21  0:32 ` [PATCH 6/6] ASoC: soc-core: use for_each_link_codecs() for dai_link codecs Kuninori Morimoto
2019-01-21 19:20   ` Applied "ASoC: soc-core: use for_each_link_codecs() for dai_link codecs" to the asoc tree Mark Brown
2019-01-22 15:43   ` [PATCH 6/6] ASoC: soc-core: use for_each_link_codecs() for dai_link codecs Sylwester Nawrocki
2019-01-22 17:39     ` Mark Brown
2019-01-24  2:55       ` Kuninori Morimoto
2019-01-24  9:48         ` Sylwester Nawrocki
2019-01-28  1:05           ` 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=87o986stfw.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.