All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Peter Rosin <peda@axentia.se>,
	alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: pcm: allow changing the playback/capture rates for symmetric links
Date: Thu, 28 Apr 2016 14:02:21 +0200	[thread overview]
Message-ID: <s5hy47yszzm.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160428114150.GM3217@sirena.org.uk>

On Thu, 28 Apr 2016 13:41:50 +0200,
Mark Brown wrote:
> 
> On Thu, Apr 28, 2016 at 01:26:49PM +0200, Takashi Iwai wrote:
> > Mark Brown wrote:
> 
> > > We've had the code for years without anyone reporting issues so...  the
> > > idiomatic ALSA thing is to set everything in one call which helps a lot.
> 
> > Yes, most of such problems come from the inconsistent hw constraints,
> > and one-shot configuration helps indeed.  But, in this case, it
> > appears more like an overlooked case to me.
> 
> If there's a useful report with the ALSA API then let's look into that -
> if people can only see this with the OSS API and can't articulate an
> actual ALSA API level problem then I'm struggling to care.  Drivers that
> do parameter validation tend to fail with OSS anyway as it tries to set
> partially configured hw_params with invalid values in them and it's not
> clear to me that this isn't the same thing happening again.

Yeah, that's why I asked whether this really doesn't happen in ALSA
native API.


> > BTW, this reminds me of another question: don't we have a dummy ASoC
> > driver like snd-dummy?  It would be convenient for a casual API
> > testing.
> 
> No, someone would need to write a series of dummy drivers that exercised
> the various API features (almost all of which are kernel internal) and
> then instantiated them but nobody stepped up and did that yet.

Well, we don't support all API features there.  Developer can modify
the existing code and test it quickly if needed at any time once when
the base code is present.  So, yeah, we need a volunteer!


Takashi

  reply	other threads:[~2016-04-28 12:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27  8:49 [PATCH] ASoC: pcm: allow changing the playback/capture rates for symmetric links Peter Rosin
2016-04-27  8:49 ` Peter Rosin
2016-04-27 16:15 ` Mark Brown
2016-04-27 16:15   ` Mark Brown
2016-04-27 20:45   ` Peter Rosin
2016-04-27 20:45     ` Peter Rosin
2016-04-28 10:38     ` Mark Brown
2016-04-28 10:38       ` Mark Brown
2016-04-28 11:03       ` Takashi Iwai
2016-04-28 11:10         ` Mark Brown
2016-04-28 11:26           ` Takashi Iwai
2016-04-28 11:41             ` Mark Brown
2016-04-28 12:02               ` Takashi Iwai [this message]
2016-04-28 17:13                 ` Mark Brown
2016-04-28 17:13                   ` Mark Brown
2016-05-02  7:43       ` Peter Rosin
2016-05-02  7:43         ` Peter Rosin
2016-05-04 16:49         ` Mark Brown
2016-05-09 12:17           ` [alsa-devel] " Takashi Iwai
2016-05-09 12:17             ` Takashi Iwai

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=s5hy47yszzm.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=perex@perex.cz \
    /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.