All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Glöckner" <dg@emlix.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] tlv320aic3x: disable ADC/DAC while changing clock
Date: Wed, 01 Apr 2009 19:16:15 +0200	[thread overview]
Message-ID: <49D3A15F.7070105@emlix.com> (raw)
In-Reply-To: <20090401164847.GE21294@sirena.org.uk>

On 04/01/2009 06:48 PM, Mark Brown wrote:
> On Wed, Apr 01, 2009 at 06:21:19PM +0200, Daniel Glöckner wrote:
>> It was my impression that it is up to the pcm part to install these
>> constraints as this is where SNDRV_PCM_INFO_JOINT_DUPLEX can be put into
>> the snd_pcm_hardware structure.
> 
> JOINT_DUPLEX is just a hint to the application about how the card will
> behave - you still need to enforce the actual constraints you have in
> the driver.  In any case, the PCM driver shouldn't be setting that
> unless it has such a constraint itself since it should work with the
> widest possible range of systems.

Then there needs to be a way for codecs and machines to force this bit if
the PCM driver didn't set it.

IMHO joint duplex is a hack that works only by chance.
Constraints that depend on the configuration of the first stream on open of the
second stream are no longer valid when the first stream is closed.
It is also not possible to add constraints when the first stream has been opened
but not yet configured.

  Daniel

-- 
Dipl.-Math. Daniel Glöckner, emlix GmbH, http://www.emlix.com
Fon +49 551 30664-0, Fax -11, Bahnhofsallee 1b, 37081 Göttingen, Germany
Geschäftsführung: Dr. Uwe Kracke, Dr. Cord Seele, Ust-IdNr.: DE 205 198 055
Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160

emlix - your embedded linux partner

  reply	other threads:[~2009-04-01 17:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 13:21 [patch] tlv320aic3x: disable ADC/DAC while changing clock Daniel Glöckner
2009-03-26 13:45 ` Mark Brown
2009-03-30 12:48   ` Daniel Glöckner
2009-03-30 12:51     ` Mark Brown
2009-04-01 10:56 ` [PATCH v2] " Daniel Glöckner
2009-04-01 12:10   ` Mark Brown
2009-04-01 14:06     ` Daniel Glöckner
2009-04-01 15:24       ` Mark Brown
2009-04-01 16:21         ` Daniel Glöckner
2009-04-01 16:48           ` Mark Brown
2009-04-01 17:16             ` Daniel Glöckner [this message]
2009-04-01 17:34               ` Mark Brown
2009-04-02  7:39     ` Jarkko Nikula
2009-04-02 10:34       ` Mark Brown
2009-04-02 10:45         ` Daniel Glöckner

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=49D3A15F.7070105@emlix.com \
    --to=dg@emlix.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    /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.