From: Lars-Peter Clausen <lars@metafoo.de>
To: Xiubo Li <Li.Xiubo@freescale.com>
Cc: broonie@kernel.org, lgirdwood@gmail.com,
alsa-devel@alsa-project.org, kuninori.morimoto.gx@renesas.com,
tiwai@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH v2 1/3] ASoC: binding: add tdm-slot.txt
Date: Wed, 12 Feb 2014 10:26:52 +0100 [thread overview]
Message-ID: <52FB3E5C.8040701@metafoo.de> (raw)
In-Reply-To: <1392191112-27028-2-git-send-email-Li.Xiubo@freescale.com>
On 02/12/2014 08:45 AM, Xiubo Li wrote:
> TDM slot:
>
> This specifies audio DAI's TDM slot.
>
> Each entry is has four non-negative integer values in DT:
> <tx_mask, rx_mask, slots, slot_width>
>
> For instance:
> simple-slot-info = <0xffffffc 0xffffffc 2 0>;
The current internal API for TDM is very poor, I don't think we want to
expose that 1 to 1 to the devicetree. Since this means we'd have to support
that forever. The first thing is that the semantics of
snd_soc_dai_set_tdm_slot() are very unclear. E.g. some drivers use a zero
bit for a active slot, some drivers use a 1 bit for a active slot. The
second thing is that we are not able to specify which channel should be
mapped to which slot. You can merely specify from/to which slots the CODEC
should read/write and then it is up to the driver to guess which channel
should go to which slot. In my opinion a binding that allows to specify a
explicit mapping of which channel goes to which slot would be much better.
Also those are four different settings. In my opinion they should not be
expressed in one property, but rather in four. E.g. specifying a tx_mask for
a rx only device does not make much sense.
- Lars
next prev parent reply other threads:[~2014-02-12 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 7:45 [PATCH v2 0/3] Add tdm slot support Xiubo Li
2014-02-12 7:45 ` [PATCH v2 1/3] ASoC: binding: add tdm-slot.txt Xiubo Li
2014-02-12 9:26 ` Lars-Peter Clausen [this message]
2014-02-12 11:10 ` [alsa-devel] " Mark Brown
2014-02-13 7:32 ` Li.Xiubo
2014-02-12 7:45 ` [PATCH v2 2/3] ASoC: core: add slot information parsing supports Xiubo Li
2014-02-12 7:45 ` [PATCH v2 3/3] ASoC: simple-card: " Xiubo Li
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=52FB3E5C.8040701@metafoo.de \
--to=lars@metafoo.de \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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