All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Simon <horms@verge.net.au>,
	Liam Girdwood <liam.r.girdwood@intel.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: [PATCH 1/2] ASoC: add snd_soc_register_chip()
Date: Fri, 08 Mar 2013 13:53:19 -0700	[thread overview]
Message-ID: <513A4FBF.5050802@wwwdotorg.org> (raw)
In-Reply-To: <87ehfqaccl.wl%kuninori.morimoto.gx@renesas.com>

On 03/07/2013 06:50 PM, Kuninori Morimoto wrote:
> Current ASoC has register function for platform/codec/dai/card,
> but doesn't have for cpu.
> It often produces confusion and fault on ASoC.
> 
> As result of ASoC community discussion,
> we consider new struct snd_soc_chip for CPU/CODEC,
> and will switch over to use it.
> 
> This patch adds very basic struct snd_soc_chip,
> and register function for it.

Conceptually this seems fine.

I would have called this a "component" rather than a "chip", since:

a) That aligns better with the phrase "multi-component" for related ASoC
features.

b) This struct doesn't always represent a whole chip, but perhaps just
an IP block within a chip. Consider an SoC with 5 completely separate
I2S block and an SPDIF block. Those are probably each separate Linux
platform devices, and each would register as its own snd_soc_chip.

To be fully useful, we'd have to convert snd_soc_sodec to be a
snd_soc_chip too. Should CODEC be a "sub-class" of chip? Should we
instead rename snd_soc_codec to snd_soc_chip/component? How do we get
there from here?

  reply	other threads:[~2013-03-08 20:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08  1:49 [PATCH 0/2] ASoC: add new struct snd_soc_chip Kuninori Morimoto
2013-03-08  1:50 ` [PATCH 1/2] ASoC: add snd_soc_register_chip() Kuninori Morimoto, Kuninori Morimoto
2013-03-08 20:53   ` Stephen Warren [this message]
2013-03-08  1:53 ` [PATCH 2/2] ASoC: fsi: use snd_soc_register_chip() instead of snd_soc_register_dais() Kuninori Morimoto, Kuninori Morimoto
2013-03-12  1:26 ` [PATCH 0/2 v2] ASoC: add new struct snd_soc_component Kuninori Morimoto
2013-03-12  1:27   ` [PATCH 1/2 v2] ASoC: add snd_soc_register_component() Kuninori Morimoto
2013-03-12 18:19     ` Stephen Warren
2013-03-12 18:57       ` Lars-Peter Clausen
2013-03-12 19:40         ` Mark Brown
2013-03-12 21:35     ` Stephen Warren
2013-03-13 10:13       ` Mark Brown
2013-03-13 11:08     ` Mark Brown
2013-03-12  1:27   ` [PATCH 2/2 v2] ASoC: fsi: use snd_soc_register_component() instead of snd_soc_register_dais() Kuninori Morimoto
2013-03-12 20:02     ` Mark Brown
2013-03-13  0:38       ` Kuninori Morimoto
2013-03-13 10:14         ` Mark Brown
2013-03-14  7:18           ` [PATCH 1/2] ASoC: add .name for snd_soc_component_driver Kuninori Morimoto
2013-03-15  1:25             ` Mark Brown
2013-03-14  7:19           ` [PATCH 2/2] ASoC: fsi: use snd_soc_register_component() instead of snd_soc_register_dais() 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=513A4FBF.5050802@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lars@metafoo.de \
    --cc=liam.r.girdwood@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.