From: Tabi Timur-B04825 <B04825@freescale.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@ti.com" <lrg@ti.com>
Subject: Re: [PATCH] ASoC: mpc8610: tell the CS4270 codec that it's the master
Date: Wed, 23 Nov 2011 05:30:08 +0000 [thread overview]
Message-ID: <4ECC84DE.6010802@freescale.com> (raw)
In-Reply-To: <20111122230558.GC3005@opensource.wolfsonmicro.com>
Mark Brown wrote:
> On Tue, Nov 22, 2011 at 02:38:59PM -0600, Timur Tabi wrote:
>> Commit ac601555 ("ASoC: Return early with -EINVAL if invalid dai format is
>> detected") requires the machine driver to tell the CS4270 codec driver
>> whether the CS4270 should be configured for master or slave operation.
>
> Applied, thanks.
So it turns out that the commit message for this patch is wrong. Sorry.
The commit that broke the MPC8610 is "ASoC: Allow DAI formats to be
specified in the dai_link", which changed the definition of
SND_SOC_DAIFMT_CBM_CFM to a non-zero value. Patch "ASoC: Return early
with -EINVAL if invalid dai format is detected" doesn't really do anything.
I don't know if it's too late to amend the commit, but if it isn't, the
proper message is:
Commit 4eae080d ("ASoC: Add cs4270 support for slave mode configurations")
requires the machine driver to set one of the SND_SOC_DAIFMT_CBx_xxx
values. The MPC8610 machine driver should be setting
SND_SOC_DAIFMT_CBM_CFM, but since that value is zero, no one noticed.
Commit 75d9ac46 ("ASoC: Allow DAI formats to be specified in the
dai_link"), however, changed the value of SND_SOC_DAIFMT_CBM_CFM from zero
to a non-zero value, which means that it now needs to be specifically set
by the machine driver.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-11-23 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 20:38 [PATCH] ASoC: mpc8610: tell the CS4270 codec that it's the master Timur Tabi
2011-11-22 23:05 ` Mark Brown
2011-11-23 5:30 ` Tabi Timur-B04825 [this message]
2011-11-23 10:30 ` 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=4ECC84DE.6010802@freescale.com \
--to=b04825@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.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.