From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
b02247@freescale.com, linux-kernel@vger.kernel.org,
timur@tabi.org, Li.Xiubo@freescale.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] ASoC: fsl-asoc-card: Don't bypass settings if cpu-dai is Master
Date: Mon, 27 Oct 2014 10:42:02 -0700 [thread overview]
Message-ID: <20141027174201.GA3408@Asurada> (raw)
In-Reply-To: <20141027173031.GA18557@sirena.org.uk>
On Mon, Oct 27, 2014 at 05:30:31PM +0000, Mark Brown wrote:
> On Fri, Oct 24, 2014 at 04:48:11PM -0700, Nicolin Chen wrote:
> > When cpu-dai is the DAI Master (CBM_CFx), it may need some configurations,
> > set_sysclk() call for eample, for cpu-dai side in the hw_params(), even if
> > the set_bias_level() has already taken care of the codec-dai side.
> >
> > So this patch just simply adds an additional condition.
>
> This was threaded with another patch series - did you intend to submit
> this or did it get sent by accident?
I created this one without "--thread" (separately from that series) but
accidentally sent the patch along with the series in one git-send-mail
command. So I think I don't need to resend it since it's already there.
Please regard this one as one single patch.
Thank you.
Nicolin
next prev parent reply other threads:[~2014-10-27 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 23:48 [PATCH 0/2] ASoC: fsl: Use dynamic slot width for ESAI Nicolin Chen
2014-10-24 23:48 ` [PATCH] ASoC: fsl-asoc-card: Don't bypass settings if cpu-dai is Master Nicolin Chen
2014-10-27 17:30 ` Mark Brown
2014-10-27 17:42 ` Nicolin Chen [this message]
2014-10-28 16:05 ` Mark Brown
2014-10-24 23:48 ` [PATCH 1/2] ASoC: fsl_esai: Use dynamic slot width as default Nicolin Chen
2014-10-24 23:48 ` [PATCH 2/2] ASoC: fsl-asoc-card: Add slot_width setting for cpu-dai Nicolin Chen
2014-10-31 18:12 ` [PATCH 0/2] ASoC: fsl: Use dynamic slot width for ESAI Mark Brown
2014-10-31 18:16 ` Nicolin Chen
2014-11-25 12:47 ` 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=20141027174201.GA3408@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=b02247@freescale.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=timur@tabi.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).