From: Lars-Peter Clausen <lars@metafoo.de>
To: Xiubo Li <Li.Xiubo@freescale.com>
Cc: broonie@kernel.org, lgirdwood@gmail.com,
fabio.estevam@freescale.com, moinejf@free.fr,
alsa-devel@alsa-project.org, kuninori.morimoto.gx@renesas.com,
tiwai@suse.de, s.hauer@pengutronix.de, timur@tabi.org,
linux-kernel@vger.kernel.org, denis@eukrea.com,
Guangyu.Chen@freescale.com, mpa@pengutronix.de,
shawn.guo@linaro.org
Subject: Re: [alsa-devel] [PATCH 01/10] ASoC: core: Add snd_soc_dai_set_tdm_slot_xlate().
Date: Sat, 01 Mar 2014 14:19:44 +0100 [thread overview]
Message-ID: <5311DE70.7000901@metafoo.de> (raw)
In-Reply-To: <1393387175-15539-2-git-send-email-Li.Xiubo@freescale.com>
On 02/26/2014 04:59 AM, Xiubo Li wrote:
> For most cases the rx_mask and tx_mask params have no use for
> snd_soc_dai_set_tdm_slot(), because they could be generated by
> {XXX_ .}of_xlate_tdm_slot_mask().
>
> This patch add snd_soc_dai_set_tdm_slot_xlate() which will replace
> the snd_soc_dai_set_tdm_slot() in some use cases to simplify the
> code. And for some CODECs or CPU DAI devices there needed much more
> work to support the .of_xlate_tdm_slot_mask feature.
>
> This patch can be applied to most use case of the current DAI drivers.
Hi,
I'm not quite sure I fully understand what this patch is trying to solve. It
adds a variant snd_soc_dai_set_tdm_slot() that instead of taking a rx and tx
mask calculates the masks based on the number of slots? In that case I don't
really see how the xlate in the name relates to that. xlate is something
you'd typically expect in a devicetree context. Maybe one should be called
snd_soc_dai_set_tdm_slot() and the other snd_soc_dai_set_tdm_slot_and_masks()?
But another question is do we really need this? I don't see the problem that
is solved by this patchset.
- Lars
next prev parent reply other threads:[~2014-03-01 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 3:59 [PATCH 00/10] Simplify the code of TDM slot setting Xiubo Li
2014-02-26 3:59 ` [PATCH 01/10] ASoC: core: Add snd_soc_dai_set_tdm_slot_xlate() Xiubo Li
2014-03-01 13:19 ` Lars-Peter Clausen [this message]
2014-03-05 3:39 ` [alsa-devel] " Mark Brown
2014-03-05 3:55 ` Li.Xiubo
2014-03-05 6:30 ` Mark Brown
2014-02-26 3:59 ` [PATCH 02/10] ASoC: fsl-utils: Add fsl_asoc_of_xlate_tdm_slot_mask() support Xiubo Li
2014-02-26 3:59 ` [PATCH 03/10] ASoC: fsl-esai: Add .of_xlate_tdm_slot_mask() support Xiubo Li
2014-02-26 3:59 ` [PATCH 04/10] ASoC: fsl-ssi: " Xiubo Li
2014-02-26 3:59 ` [PATCH 05/10] ASoC: imx-ssi: " Xiubo Li
2014-02-26 3:59 ` [PATCH 06/10] ASoC: simple-card: Use snd_soc_dai_set_tdm_slot_xlate() Xiubo Li
2014-02-26 3:59 ` [PATCH 07/10] ASoC: blackfin: bf5xx-ad1836: " Xiubo Li
2014-02-26 3:59 ` [PATCH 08/10] ASoC: blackfin: bf5xx-ad193x: " Xiubo Li
2014-02-26 3:59 ` [PATCH 09/10] ASoC: fsl: eukrea-tlv320: " Xiubo Li
2014-02-26 3:59 ` [PATCH 10/10] ASoC: fsl: wm1133-ev1: " 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=5311DE70.7000901@metafoo.de \
--to=lars@metafoo.de \
--cc=Guangyu.Chen@freescale.com \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=denis@eukrea.com \
--cc=fabio.estevam@freescale.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=mpa@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=timur@tabi.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