All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Qiao Zhou <zhouqiao@marvell.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Eric Miao <eric.y.miao@gmail.com>, Takashi Iwai <tiwai@suse.de>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	"trinity.qiao.zhou@gmail.com" <trinity.qiao.zhou@gmail.com>,
	Chao Xie <cxie4@marvell.com>
Subject: Re: [PATCH V0] ASoC: pxa-ssp: add TISSP mode support
Date: Mon, 11 Nov 2013 11:21:15 +0000	[thread overview]
Message-ID: <20131111112115.GF2674@sirena.org.uk> (raw)
In-Reply-To: <52803B02.6000008@marvell.com>


[-- Attachment #1.1: Type: text/plain, Size: 403 bytes --]

On Mon, Nov 11, 2013 at 10:03:46AM +0800, Qiao Zhou wrote:

> Yes, it should be an improvement of current driver. The format is
> not a new one, and the DSP_A mode is suitable for it. The question
> here is to handle both PSP and SSP mode here. should I pass another
> parameter here to support it?

Can't the driver just do whatever is best automatically - why would the
user need to configure things?

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2013-11-11 11:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  8:30 [PATCH V0] ASoC: pxa-ssp: add TISSP mode support Qiao Zhou
2013-11-06 11:24 ` Mark Brown
2013-11-08  1:52   ` Qiao Zhou
2013-11-08 10:19     ` Mark Brown
2013-11-10  1:50       ` Qiao Zhou
2013-11-10 11:10         ` Mark Brown
2013-11-11  2:03           ` Qiao Zhou
2013-11-11 11:21             ` Mark Brown [this message]
2013-11-15  8:57               ` Qiao Zhou
2013-11-10  9:29     ` Daniel Mack
2013-11-11  1:59       ` Qiao Zhou

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=20131111112115.GF2674@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cxie4@marvell.com \
    --cc=eric.y.miao@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.de \
    --cc=trinity.qiao.zhou@gmail.com \
    --cc=zhouqiao@marvell.com \
    /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.