Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de,
	ffado-devel@lists.sf.net
Subject: Re: [PATCH 9/9] ctl: add test program for control element set
Date: Thu, 16 Jun 2016 15:52:17 +0200	[thread overview]
Message-ID: <s5h7fdp9r72.wl-tiwai@suse.de> (raw)
In-Reply-To: <1466002665-30048-10-git-send-email-o-takashi@sakamocchi.jp>

On Wed, 15 Jun 2016 16:57:45 +0200,
Takashi Sakamoto wrote:
> 
> The feature of control element set has been abandoned for a long time since
> firstly introduced in 2003 (approx). Furthermore, there's few applications
> to utilize this feature. These situations bring a hard work to the persons
> who need the feature. Especially, a lack of test program make it harder to
> fix much bugs in this feature.
> 
> This commit adds a test program as a sample of the feature. This program
> adds element sets of each element type to 'hw:0' in this order; boolean,
> integer, enumerated, bytes, IEC958 and integer64. Each iteration includes
> below scheme:
> 
> 1. add an element set with 900 elements. Each of them has maximum number
>    of members allowed by ALSA ctl core.
> 2. check all of events generated by above operation.
> 3. retrieve information of each element, then validate it.
> 4. unlock each member of all elements because they're initially locked.
> 5. write to all of members in all elements and read.
> 6. check all of events generated by above operation.
> 7. write information for threshold level to the element set and read it.
> 8. check all of events generated by above operation.
> 9. remove the element set.
> 10.check all of events generated by above operation.
> 
> When any of these operations fail, it means regression occurs. Then, added
> elements still remain in a certain sound card. In this case, unloading
> drivers corresponding to the card is an easy way to recover.
> 
> Besides, this program doesn't perform below element operations of ALSA ctl
> feature:
>  - list
>  - lock
>  - replace
> 
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>

The contents are good, but could you reformat it in kernel coding
style, i.e. with a hard tab and indent level 8?  We aren't so strict
in alsa user-space stuff, but it's still better to have some unified
style.

I already applied all other patches, so just resubmit only this one.


thanks,

Takashi

  reply	other threads:[~2016-06-16 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 14:57 [alsa-lib][PATCH 0/9 v3] ctl: add APIs for control element set Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 1/9] ctl: add an overview for design of ALSA control interface Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 2/9] ctl: improve comments for handling element data Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 3/9] ctl: add functions to add an element set Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 4/9] ctl: improve comments for API to add an element of IEC958 type Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 5/9] ctl: change former APIs as wrapper functions of element set APIs Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 6/9] pcm: use new APIs to add a control element set for softvol plugin Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 7/9] ctl: add explanation about threshold level feature Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 8/9] ctl: improve API documentation for threshold level operations Takashi Sakamoto
2016-06-15 14:57 ` [PATCH 9/9] ctl: add test program for control element set Takashi Sakamoto
2016-06-16 13:52   ` Takashi Iwai [this message]
2016-06-16 13:54 ` [alsa-lib][PATCH 0/9 v3] ctl: add APIs " Takashi Iwai
2016-06-16 15:44   ` Takashi Sakamoto

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=s5h7fdp9r72.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=ffado-devel@lists.sf.net \
    --cc=o-takashi@sakamocchi.jp \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox