From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
"Aaltonen Matti.J (Nokia-MS/Tampere)"
<matti.j.aaltonen@nokia.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH v2 0/1] *** SUBJECT HERE ***
Date: Thu, 22 Jul 2010 13:04:46 +0100 [thread overview]
Message-ID: <20100722120446.GG4737@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <s5hpqyfzrcg.wl%tiwai@suse.de>
On Thu, Jul 22, 2010 at 01:30:23PM +0200, Takashi Iwai wrote:
> The hw constrains are basically for hw_params setup. So, the question
> is whether do we want to make open successful but further setup fails,
> or do we give the error at open time? IMO, the latter looks
> straightforward. That is, changing the flag before open call is
> needed, or we need to check explicitly in the open callback itself.
> Or, let me know if I misunderstand the discussion here...
I think you understand correctly but we decided we can just totally
ignore this setting since from the point of view of application software
it can happily do full duplex operations with this device, the device
will just discard the data sent to it in some configurations.
next prev parent reply other threads:[~2010-07-22 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 9:38 [PATCH v2 0/1] *** SUBJECT HERE *** Matti J. Aaltonen
2010-07-22 9:38 ` [PATCH v2 1/1] ASoC: TI WL1273 FM Radio Codec Matti J. Aaltonen
2010-07-22 9:48 ` [PATCH v2 0/1] *** SUBJECT HERE *** Mark Brown
2010-07-22 10:57 ` Peter Ujfalusi
2010-07-22 11:02 ` Mark Brown
2010-07-22 11:07 ` Peter Ujfalusi
2010-07-22 11:30 ` Takashi Iwai
2010-07-22 12:04 ` Mark Brown [this message]
2010-07-22 11:18 ` matti.j.aaltonen
2010-07-22 11:25 ` Peter Ujfalusi
2010-07-22 11:37 ` matti.j.aaltonen
2010-07-22 12:02 ` Mark Brown
2010-07-22 12:11 ` matti.j.aaltonen
2010-07-22 13:05 ` Mark Brown
2010-07-22 14:13 ` Matti J. Aaltonen
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=20100722120446.GG4737@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=matti.j.aaltonen@nokia.com \
--cc=peter.ujfalusi@nokia.com \
--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.