Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Stas Sergeev <stsp@list.ru>
Cc: ALSA devel <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>,
	"Gabriel M. Beddingfield" <gabrbedd@gmail.com>,
	stsp@users.sourceforge.net
Subject: Re: [PATCH] ASoC: define playback and capture streams in dummy codec
Date: Fri, 12 Apr 2013 17:31:19 +0200	[thread overview]
Message-ID: <516828C7.5090203@metafoo.de> (raw)
In-Reply-To: <51682633.70008@list.ru>

On 04/12/2013 05:20 PM, Stas Sergeev wrote:
> 12.04.2013 19:13, Gabriel M. Beddingfield пишет:
>> On 04/12/2013 07:19 AM, Stas Sergeev wrote:
>>> On Fri, 12 Apr 2013 11:59:44 +0100
>>> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>>>>> This patch adds a playback and capture streams to the dummy codec DAI
>>>>> configuration. Most permissive set of sampling rates and formats is
>>>>> used.
>>>> The changelog ought to explain why this is required...
>>> I can only tell that without this patch I am not getting any
>>> sound at all... which is probably a rather poor statement for
>>> the changelog. Could you please correct the changelog with the
>>> better knowledge of the details?
>>
>> He means that the commit message. Your commit message says what the
>> patch does. It does not say why the patch is needed.
> Yes.
> But what should I add to the commit message, if the
> only thing I know about this patch, is that I am not getting
> any sound without it? :) The reason should be obvious for
> whoever is familiar with that subsystem, but its not me.

Well, if not explicitly initialized a field is set to 0. Which is kind of the
most restrictive option for many of the fields. E.g. channels_max, rates,
formats, etc. When the ASoC core creates a new PCM device it will take the
intersection of the CPU DAI and CODEC DAI fields to initialize the fields the
PCM. So if for example channels_max is 0 for the CODEC DAI, channels_max will
also be 0 for the PCM, no matter what channels_max is set to for the CPU DAI.
Same goes for formats and rates. So a dummy CODEC should have set its fields in
a way that it is most permissive, so that the intersection of the CODEC DAI
fields with the CPU DAI fields will be equal to the CPU DAI fields.

- Lars
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2013-04-12 15:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 10:53 [PATCH] ASoC: define playback and capture streams in dummy codec Stas Sergeev
2013-04-12 10:59 ` Mark Brown
2013-04-12 14:19   ` Stas Sergeev
2013-04-12 15:13     ` Gabriel M. Beddingfield
2013-04-12 15:20       ` Stas Sergeev
2013-04-12 15:24         ` Gabriel M. Beddingfield
2013-04-16 16:34           ` Stas Sergeev
2013-04-12 15:31         ` Lars-Peter Clausen [this message]
2013-04-12 16:37           ` Stas Sergeev
2013-04-12 16:55             ` Lars-Peter Clausen
2013-04-12 19:19               ` Stas Sergeev
2013-04-17 12:34   ` Stas Sergeev
2013-04-17 13:31     ` 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=516828C7.5090203@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gabrbedd@gmail.com \
    --cc=lrg@ti.com \
    --cc=stsp@list.ru \
    --cc=stsp@users.sourceforge.net \
    /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