From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Cc: Simon <horms@verge.net.au>,
Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-SH <linux-sh@vger.kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 0/2][RFC] ASoC: fsi/rcar: fixup SND_SOC_DAIFMT_CBx_CFx flags
Date: Thu, 13 Mar 2014 10:48:36 +0000 [thread overview]
Message-ID: <20140313104836.GN366@sirena.org.uk> (raw)
In-Reply-To: <87txb3rjzw.wl%kuninori.morimoto.gx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Tue, Mar 11, 2014 at 11:47:36PM -0700, Kuninori Morimoto wrote:
>
> Hi Mark, Simon
>
> These patches fixup Renesas fsi/rcar driver's
> SND_SOC_DAIFMT_CBx_CFx flag settings.
>
> I had misunderstand these settings...
> But this is still [RFC], since it modifies DT side code too.
>
> >> Mark
>
> #1 patch depends on Jyri's
> "Fix simple-card *-master DT parameter handling"
> if it was accepted
>
> >> Simon
>
> Can you check #1 patch which modifys SH-ARM platform ?
So, we need to do something quickly here since this affects DT bindings
but it would be *much* better to avoid having to set the master flags on
both ends of the link since that's going to make the binding confusing
if we're stuck with it as an ABI.
Simon, are you OK with the arch side of cleanups for this going via my
tree?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-13 10:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 6:47 [PATCH 0/2][RFC] ASoC: fsi/rcar: fixup SND_SOC_DAIFMT_CBx_CFx flags Kuninori Morimoto
2014-03-12 6:48 ` [PATCH 1/2][RFC] ASoC: fsi: " Kuninori Morimoto
2014-03-13 23:55 ` Simon Horman
2014-03-12 6:48 ` [PATCH 2/2][RFC] ASoC: rcar: " Kuninori Morimoto
2014-03-13 10:48 ` Mark Brown [this message]
2014-03-13 23:55 ` [PATCH 0/2][RFC] ASoC: fsi/rcar: " Kuninori Morimoto
2014-03-13 23:55 ` Simon Horman
2014-03-14 10:26 ` Mark Brown
2014-03-17 0:15 ` Simon Horman
2014-03-14 0:54 ` [PATCH 0/2 v2] " Kuninori Morimoto
2014-03-14 0:56 ` [PATCH 1/2 v2] ASoC: fsi: " Kuninori Morimoto
2014-03-14 19:31 ` Mark Brown
2014-03-14 0:56 ` [PATCH 2/2] ASoC: rcar: " Kuninori Morimoto
2014-03-14 19:34 ` Mark Brown
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=20140313104836.GN366@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sh@vger.kernel.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 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).