From: Takashi Iwai <tiwai@suse.de>
To: Alan Young <Alan.Young@IEE.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] [updated] pcm: rate: Add capability to pass configuration node to plugins
Date: Fri, 17 Feb 2017 17:53:14 +0100 [thread overview]
Message-ID: <s5hwpcosqrp.wl-tiwai@suse.de> (raw)
In-Reply-To: <a66a494e-3bd6-c813-6786-ca9deceabdc0@IEE.org>
On Wed, 15 Feb 2017 13:28:38 +0100,
Alan Young wrote:
>
> On 14/02/17 07:30, Alan Young wrote:
> > However, looking at that again now, I see that the test is flawed
> > because it has no marker to check that it is only applied on the
> > first iteration, so the loop would always stop after testing the
> > second alternative. I could fix that or remove the test altogether -
> > what do you think?
>
> Here is an updated patch with a more robust check.
I still doubt whether it works as you expected...
> else if (snd_config_get_type(converter) == SND_CONFIG_TYPE_COMPOUND) {
> snd_config_iterator_t i, next;
> snd_config_for_each(i, next, converter) {
> snd_config_t *n = snd_config_iterator_entry(i);
> + const char *id;
> if (snd_config_get_string(n, &type) < 0)
> break;
> - err = rate_open_func(rate, type, 0);
> + err = rate_open_func(rate, type, converter, 0);
> if (!err)
> break;
> + if (snd_config_get_id(n, &id) >= 0 && id && !isdigit(*id))
> + break; /* not a simple array of types */
> }
The problem is that you pass always the compound object as the
converter argument. As you already suggested, there are two cases:
one is a string array and another is a compound with optional args.
In your code, the first iteration doesn't check which type is. So it
always fails if the string array is passed.
That is, the right implementation is to check whether the given
compound is a string array is. If yes, it goes to the old style
loop (and you can check "name" argument properly). If not, it goes
with the new compound argument. That's simple enough, and more
understandable the condition you used for the loop termination.
BTW, one another thing:
> @@ -1386,7 +1414,7 @@ int snd_pcm_rate_open(snd_pcm_t **pcmp, const char *name,
> #else
> type = "linear";
> open_func = SND_PCM_RATE_PLUGIN_ENTRY(linear);
> - err = open_func(SND_PCM_RATE_PLUGIN_VERSION, &rate->obj, &rate->ops);
> + err = open_func(SND_PCM_RATE_PLUGIN_VERSION, &rate->obj, &rate->ops, 0);
Is this really correct? I thought SND_PCM_RATE_PLUGIN_ENTRY() refers
to the old style?
thanks,
Takashi
next prev parent reply other threads:[~2017-02-17 16:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 15:24 [PATCH] pcm_rate: Do not discard slave reported delay in status result Alan Young
2016-11-17 15:26 ` Alan Young
2016-11-17 16:47 ` Takashi Iwai
2016-11-17 16:51 ` Alan Young
2016-11-17 16:55 ` Takashi Iwai
2016-11-17 17:12 ` [PATCH RESEND] " Alan Young
2016-11-28 19:11 ` Takashi Iwai
2016-12-13 11:43 ` Alan Young
2016-12-13 11:49 ` Takashi Iwai
2016-12-13 13:05 ` Alan Young
2016-12-14 14:29 ` Takashi Iwai
2017-02-08 10:50 ` [PATCH] pcm: rate: Add capability to pass configuration node to plugins Alan Young
2017-02-08 15:36 ` Takashi Iwai
2017-02-09 15:41 ` Alan Young
2017-02-09 15:48 ` Alan Young
2017-02-13 17:20 ` [PATCH] [updated] " Alan Young
2017-02-14 7:08 ` Takashi Iwai
2017-02-14 7:30 ` Alan Young
2017-02-15 12:28 ` Alan Young
2017-02-17 16:53 ` Takashi Iwai [this message]
2017-02-17 17:44 ` Alan Young
2017-02-17 17:59 ` Takashi Iwai
2017-02-21 12:02 ` Alan Young
2017-02-21 12:39 ` Takashi Iwai
2017-02-21 14:34 ` Alan Young
2017-02-21 14:43 ` Takashi Iwai
2017-02-21 15:04 ` Alan Young
2017-02-21 15:14 ` Takashi Iwai
2017-02-21 15:24 ` Alan Young
2017-02-21 15:28 ` Takashi Iwai
2017-02-21 16:14 ` Alan Young
2017-02-21 21:30 ` 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=s5hwpcosqrp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Alan.Young@IEE.org \
--cc=alsa-devel@alsa-project.org \
/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