From: Jean-Francois Moine <moinejf@free.fr>
To: Xiubo Li <Li.Xiubo@freescale.com>
Cc: broonie@kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Jyri Sarha <jsarha@ti.com>, Nicolin Chen <nicoleotsuka@gmail.com>
Subject: Re: [RFC][PATCH] ASoC: simple-card: Merge single and muti DAI link code.
Date: Sun, 31 Aug 2014 18:27:25 +0200 [thread overview]
Message-ID: <20140831182725.3135db4f@armhf> (raw)
In-Reply-To: <1409294797-21948-1-git-send-email-Li.Xiubo@freescale.com>
On Fri, 29 Aug 2014 14:46:37 +0800
Xiubo Li <Li.Xiubo@freescale.com> wrote:
> This patch merge single DAI link and muti-DAI links code together,
> and simply the simple-card driver code.
>
> And also do some other improvement:
>
> Since from the DAI format micro SND_SOC_DAIFMT_CBx_CFx, the 'CBx'
> mean Codec's bit clock is as master/slave and the 'CFx' mean Codec's
> frame clock is as master/slave.
>
> So these same DAI formats should be informed to CPU and CODE DAIs at
> the same time. For the Codec driver will set the bit clock and frame
> clock as the DAI formats said, but for the CPU driver, if the the
> bit clock or frame clock is as Codec master, so it should be set CPU
> DAI device as bit clock or frame clock as slave, and vice versa.
>
> The old code will cause confusion, and we should be clear that the
> letter 'C' here mean to Codec.
>
> Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Cc: Jean-Francois Moine <moinejf@free.fr>
> Cc: Jyri Sarha <jsarha@ti.com>
> Cc: Nicolin Chen <nicoleotsuka@gmail.com>
> ---
>
> Hi,
>
> This patch will break the old DT, so i just send one RFC version, and
> will add the old DT patches in next version if this patch can work
> well.
>
> Any comments and advices are welcome.
Hi Xiubo,
My DT is
sound {
compatible = "simple-audio-card";
simple-audio-card,name = "Cubox Audio";
simple-audio-card,dai-link@0 { /* I2S - HDMI */
format = "i2s";
cpu {
sound-dai = <&audio1 0>;
};
codec {
sound-dai = <&hdmi 0>;
};
};
...
I was getting 0x1001 as the format (codec clk & FRM master and i2s').
With your patch, I get 0x4000 (clk master & frame slave and no format).
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2014-08-31 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 6:46 [RFC][PATCH] ASoC: simple-card: Merge single and muti DAI link code Xiubo Li
[not found] ` <1409294797-21948-1-git-send-email-Li.Xiubo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-08-29 12:00 ` Mark Brown
[not found] ` <20140829120035.GW29327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-09-01 2:02 ` Li.Xiubo-KZfg59tc24xl57MIdRCFDg
2014-09-01 9:39 ` Jyri Sarha
[not found] ` <54043EBE.9020808-l0cyMroinI0@public.gmane.org>
2014-09-02 9:05 ` Li.Xiubo-KZfg59tc24xl57MIdRCFDg
2014-08-31 16:27 ` Jean-Francois Moine [this message]
2014-09-01 2:57 ` Li.Xiubo
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=20140831182725.3135db4f@armhf \
--to=moinejf@free.fr \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicoleotsuka@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).