From: Nicolin Chen <b42378@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
linuxppc-dev@lists.ozlabs.org, lgirdwood@gmail.com,
timur@tabi.org
Subject: Re: [PATCH] ASoC: fsl_ssi: Implement symmetric_channels and symmetric_samplebits
Date: Wed, 4 Dec 2013 18:33:07 +0800 [thread overview]
Message-ID: <20131204103306.GF8609@MrMyself> (raw)
In-Reply-To: <20131204104230.GD29268@sirena.org.uk>
On Wed, Dec 04, 2013 at 10:42:30AM +0000, Mark Brown wrote:
> On Wed, Dec 04, 2013 at 03:27:03PM +0800, Nicolin Chen wrote:
>
> > Sir, shall we also implement these two to other drivers like codecs?
> > I know this symmetry is a new feature and might be still immature.
> > By implementing it might bring some side effects. But meanwhile, it
> > would also allows us to engage more people to test it, although myself
> > have done a branch of tests with different user cases on my platform.
>
> > Or we just wait for people engaging by themselves?
>
> It makes sense to roll it out, since it's in the core if there is a
> problem we only need to fix it in one place to fix all the users which
> makes life easier.
Fully Agreed. I'll try to generate patches to do the rolling job and send
them later.
Thank you for your reply,
Nicolin Chen
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <b42378@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
linuxppc-dev@lists.ozlabs.org, lgirdwood@gmail.com,
timur@tabi.org
Subject: Re: [alsa-devel] [PATCH] ASoC: fsl_ssi: Implement symmetric_channels and symmetric_samplebits
Date: Wed, 4 Dec 2013 18:33:07 +0800 [thread overview]
Message-ID: <20131204103306.GF8609@MrMyself> (raw)
In-Reply-To: <20131204104230.GD29268@sirena.org.uk>
On Wed, Dec 04, 2013 at 10:42:30AM +0000, Mark Brown wrote:
> On Wed, Dec 04, 2013 at 03:27:03PM +0800, Nicolin Chen wrote:
>
> > Sir, shall we also implement these two to other drivers like codecs?
> > I know this symmetry is a new feature and might be still immature.
> > By implementing it might bring some side effects. But meanwhile, it
> > would also allows us to engage more people to test it, although myself
> > have done a branch of tests with different user cases on my platform.
>
> > Or we just wait for people engaging by themselves?
>
> It makes sense to roll it out, since it's in the core if there is a
> problem we only need to fix it in one place to fix all the users which
> makes life easier.
Fully Agreed. I'll try to generate patches to do the rolling job and send
them later.
Thank you for your reply,
Nicolin Chen
next prev parent reply other threads:[~2013-12-04 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 10:38 [PATCH] ASoC: fsl_ssi: Implement symmetric_channels and symmetric_samplebits Nicolin Chen
2013-12-03 10:38 ` Nicolin Chen
2013-12-03 14:58 ` Mark Brown
2013-12-03 14:58 ` Mark Brown
2013-12-04 7:27 ` Nicolin Chen
2013-12-04 7:27 ` Nicolin Chen
2013-12-04 10:42 ` Mark Brown
2013-12-04 10:42 ` [alsa-devel] " Mark Brown
2013-12-04 10:33 ` Nicolin Chen [this message]
2013-12-04 10:33 ` Nicolin Chen
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=20131204103306.GF8609@MrMyself \
--to=b42378@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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 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.