From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Simon <horms@verge.net.au>, Liam Girdwood <lrg@ti.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: [RFC][PATCH 1/2] ASoC: add snd_soc_of_parse_daifmt()
Date: Thu, 29 Nov 2012 15:12:35 +0000 [thread overview]
Message-ID: <20121129151235.GJ32691@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50B6F0F7.1050902@wwwdotorg.org>
[-- Attachment #1.1: Type: text/plain, Size: 410 bytes --]
On Wed, Nov 28, 2012 at 10:21:59PM -0700, Stephen Warren wrote:
> But isn't there a lot more to the DAI format than just the format enum
> itself?
There is but it should be OK to represent that as separate properties
rather than trying to glom all the combinations into a single property.
For the frame inversion flags we can assume a reasonable default of non
inverted so it seems OK to leave them for now.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-11-29 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 4:31 [RFC][PATCH 0/2] ASoC: add DT support on simple-card Kuninori Morimoto
2012-11-29 4:31 ` [RFC][PATCH 1/2] ASoC: add snd_soc_of_parse_daifmt() Kuninori Morimoto
2012-11-29 5:21 ` Stephen Warren
2012-11-29 15:12 ` Mark Brown [this message]
2012-11-30 0:35 ` Kuninori Morimoto
2012-12-04 20:18 ` Stephen Warren
2012-12-05 7:55 ` Kuninori Morimoto
2012-12-05 20:42 ` Stephen Warren
2012-12-06 9:02 ` Kuninori Morimoto
2012-11-29 4:32 ` [RFC][PATCH 2/2] ASoC: simple-card: add DT support Kuninori Morimoto
2012-11-29 5:20 ` Stephen Warren
2012-11-29 6:05 ` Kuninori Morimoto
2012-11-30 10:38 ` Daniel Mack
2012-12-03 0:18 ` Kuninori Morimoto
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=20121129151235.GJ32691@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lrg@ti.com \
--cc=swarren@wwwdotorg.org \
/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.