All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Lu Guanqun <guanqun.lu@intel.com>
Cc: ALSA <alsa-devel@alsa-project.org>,
	"clemens@ladisch.de" <clemens@ladisch.de>
Subject: Re: [PATCH 3/3] ALSA: core: set kcontrol's count field correctly
Date: Wed, 24 Aug 2011 15:06:41 +0200	[thread overview]
Message-ID: <s5hk4a39cwu.wl%tiwai@suse.de> (raw)
In-Reply-To: <20110824124638.GC1811@guanqun-laptop.ccr.corp.intel.com>

At Wed, 24 Aug 2011 20:46:38 +0800,
Lu Guanqun wrote:
> 
> On Wed, Aug 24, 2011 at 08:05:56PM +0800, Takashi Iwai wrote:
> > > Hi Takashi,
> > > 
> > > I don't how this approach can solve this problem.
> > 
> > There is no problem.  You can't copy the data from ELEM_INFO for
> > ELEM_ADD/REPLACE.  It was a wrong assumption to reuse the data.
> > Instead, you had to set up the struct field manually.
> > That is, the test procedure was simply wrong.
> > 
> > > There's still an
> > > implicit assumption here that user space application will clear
> > > info->elem_count to zero before it issues the REPLACE ioctl, right?
> > 
> > Yes, the point is that it's no longer same structure.  So, you can't
> > copy from the result from ELEM_INFO ioctl any more.  Instead, you need
> > to set up the struct field manually.
> 
> Thanks Takashi, that's the info I'm looking for. We need to state this
> requirements explicitly, it seems we lack these kind of documentation and
> thus it results in poorly written test cases in user space.

Yep.

> Is there any man pages or documentation we can state this clearly?

No.  Partly because the user-space apps are supposed to use alsa-lib.

> I can
> help to contribute some documentation or even add some sample programs
> there.

Yes, please, that'll be helpful.


thanks,

Takashi

  reply	other threads:[~2011-08-24 13:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  3:12 [PATCH 1/3] ALSA: core: trivial code style fix Lu Guanqun
2011-08-24  3:12 ` [PATCH 2/3] ALSA: core: release the constraint check for replace ops Lu Guanqun
2011-08-24  6:01   ` Takashi Iwai
2011-08-24  6:08     ` Lu Guanqun
2011-08-24  6:45       ` [PATCH v2] " Lu Guanqun
2011-08-24  8:41         ` Takashi Iwai
2011-08-24  3:12 ` [PATCH 3/3] ALSA: core: set kcontrol's count field correctly Lu Guanqun
2011-08-24  6:06   ` Takashi Iwai
2011-08-24  6:17     ` Lu Guanqun
2011-08-24  6:26       ` Takashi Iwai
2011-08-24  8:42         ` Takashi Iwai
2011-08-24 11:46           ` Lu Guanqun
2011-08-24 12:05             ` Takashi Iwai
2011-08-24 12:46               ` Lu Guanqun
2011-08-24 13:06                 ` Takashi Iwai [this message]
2011-08-24  6:18     ` Takashi Iwai
2011-08-24  8:40 ` [PATCH 1/3] ALSA: core: trivial code style fix 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=s5hk4a39cwu.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=guanqun.lu@intel.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.