[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5320280C.6080004@ti.com>
Date: Wed, 12 Mar 2014 11:25:32 +0200
From: Jyri Sarha <jsarha@...com>
To: Nicolin Chen <Guangyu.Chen@...escale.com>, <broonie@...nel.org>
CC: <robh+dt@...nel.org>, <pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<rob@...dley.net>, <lgirdwood@...il.com>,
<kuninori.morimoto.gx@...esas.com>, <devicetree@...r.kernel.org>,
<Li.Xiubo@...escale.com>, <moinejf@...e.fr>,
<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<alsa-devel@...a-project.org>
Subject: Re: [PATCH v2] ASoC: simple-card: overwrite cpu_dai->fmt with codec_dai->fmt
On 03/12/2014 05:02 AM, Nicolin Chen wrote:
> The current simple-card driver separates the daimft for cpu_dai and codec_dai.
> So we might get different values for them (0x4003 and 0x1003 for example):
>
> asoc-simple-card sound-cs42888.12: cpu : 2024000.esai / 4003 / 132000000
> asoc-simple-card sound-cs42888.12: codec : cs42888 / 1003 / 24576000
> asoc-simple-card sound-cs42888.12: cs42888 <-> 2024000.esai mapping ok
>
> This is not allowed at all as we need to keep the DAIFMT settings identical
> for both the ends of the link.
>
> Thus this patch fixes it by overwriting the cpu_dai->fmt with codec_dai->fmt
> since we defined the DAIFMT_MASTER basing on CODEC at the first place while
> the other bits are same.
>
> Signed-off-by: Nicolin Chen <Guangyu.Chen@...escale.com>
> ---
Hi Nicolin,
This patch is an improvement, but in my opinion the binding is still a
bit confusing.
How about changing 'frame-master' and 'bitclock-master' to
'codec-frame-master' and 'codec-bitclock-master'. We could possibly keep
the old names as aliases until all the .dts files out there have been fixed.
At the same go we could add SND_SOC_DAIFMT_MASTER_MASK here:
> /* get CPU/CODEC common format via simple-audio-card,format */
> priv->daifmt = snd_soc_of_parse_daifmt(node, "simple-audio-card,") &
> (SND_SOC_DAIFMT_FORMAT_MASK | SND_SOC_DAIFMT_INV_MASK);
or leave the masking out all together. Can't see why
SND_SOC_DAIFMT_CONT/GATED could not be defined at dai-link level too.
This way the norm would be defining the daifmt at link level. We could
still keep the possibility to overwrite the setting at dai level if
there is need for that.
Best regards,
Jyri
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists