Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
	"Jin, Yao" <yao.jin@linux.intel.com>,
	Mark Brown <broonie@kernel.org>,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 07/13] topology: Add private data parser
Date: Wed, 08 Jul 2015 15:21:15 +0100	[thread overview]
Message-ID: <1436365275.2474.41.camel@loki> (raw)
In-Reply-To: <s5hoajmhh3q.wl-tiwai@suse.de>

On Wed, 2015-07-08 at 16:14 +0200, Takashi Iwai wrote:
> On Wed, 08 Jul 2015 15:31:27 +0200,
> Jin, Yao wrote:
> > 
> > 
> > 
> > On 2015/7/8 16:57, Liam Girdwood wrote:
> > > On Tue, 2015-07-07 at 18:19 +0200, Takashi Iwai wrote:
> > >> On Tue, 07 Jul 2015 17:54:02 +0200,
> > >> Liam Girdwood wrote:
> > >>>
> > >>> On Wed, 2015-07-01 at 18:20 +0200, Takashi Iwai wrote:
> > >>>
> > >>>>
> > >>>>> +static int get_hex_num(const char *str)
> > >>>>> +{
> > >>>>> +	char *tmp, *s = NULL;
> > >>>>> +	int i = 0;
> > >>>>> +
> > >>>>> +	tmp = strdup(str);
> > >>>>> +	if (tmp == NULL)
> > >>>>> +		return -ENOMEM;
> > >>>>> +
> > >>>>> +	s = strtok(tmp, ",");
> > >>>>> +	while (s != NULL) {
> > >>>>> +		s = strtok(NULL, ",");
> > >>>>> +		i++;
> > >>>>> +	}
> > >>>>> +
> > >>>>> +	free(tmp);
> > >>>>> +	return i;
> > >>>>
> > >>>> Hmm, this just counts the number of comma + 1, so you don't need to
> > >>>> duplicate the string?
> > >>>>
> > >>>
> > >>> The string here is duplicated since strtok is destructive (it overwrites
> > >>> the delimiters with NULL) and the string is being used later on by the
> > >>> calling function.
> > >>
> > >> Yes, but what I meant is something like below:
> > >>
> > >> static int get_hex_num(const char *str)
> > >> {
> > >> 	int i = 0;
> > >>
> > >> 	if (!*str)
> > >> 		return 0;
> > >> 	for (;;) {
> > >> 		i++;
> > >> 		str = strchr(str, ',');
> > >> 		if (!str)
> > >> 			return i;
> > >> 		str++;
> > >> 	}
> > >> }
> > >>
> > >> ... so that it works without strdup().
> > >>
> > >> But it seems that strtok() skips the starting delimiter or handles
> > >> multiple delimiters as a single, so the result will become
> > >> inconsistent.  That is, all the following strings will give "a" and
> > >> "b" via strtok():
> > >> 	a,b
> > >> 	a,,b
> > >> 	,a,b
> > >> 	a,b,
> > >>
> > >> I guess you don't want to have an empty list element, right?
> > >>
> > > 
> > > Lets ask the author :) but IMO an empty list should be skipped here.
> > > 
> > > Yao, what's your rational behind this code ?
> > 
> > Sorry for replying late, I just see this mail.
> > 
> > The get_hex_num() returns the number of hexadecimal in string.
> > 
> > Say the string is "0x12,0x34,0x56,0x78" or "0x12,0x34,0x56,0x78,",
> > the get_hex_num() returns 4.
> > 
> > But if I use strchr, for above string, I get different number (3 or 4).
> > That's the reason I choose the strtok().
> > 
> > I do this is because I think user may append the comma at the end of
> > string.
> 

Ok, lets make commas at the end illegal.

> So, is this allowed intentionally as a valid syntax?  As I showed,
> a string like ",,,0x12,,0x34,,,,0x56,0x78,," would be handled as a
> valid string.
> 
> The above may look strange, but the strtok() behavior is natural if
> you imagine to replace "," with a space.
> 

So I'll fix this to be "0x01, 0x02, 0x03" syntax only. i.e. comma
between each value and no comma at the end.

Liam

  reply	other threads:[~2015-07-08 14:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 13:44 [PATCH v2 01/13] topology: uapi: Add UAPI headers for topology ABI Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 02/13] conf: topology: Add topology file for broadwell audio DSP Liam Girdwood
2015-07-01 15:47   ` Takashi Iwai
2015-07-01 16:16     ` Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 03/13] topology: Add topology core parser Liam Girdwood
2015-07-01 16:00   ` Takashi Iwai
2015-07-01 13:44 ` [PATCH v2 04/13] topology: Add text section parser Liam Girdwood
2015-07-01 16:03   ` Takashi Iwai
2015-07-01 13:44 ` [PATCH v2 05/13] topology: Add PCM parser Liam Girdwood
2015-07-01 16:14   ` Takashi Iwai
2015-07-01 16:20     ` Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 06/13] topology: Add operations parser Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 07/13] topology: Add private data parser Liam Girdwood
2015-07-01 16:20   ` Takashi Iwai
2015-07-07 15:54     ` Liam Girdwood
2015-07-07 16:19       ` Takashi Iwai
2015-07-08  8:57         ` Liam Girdwood
2015-07-08 13:31           ` Jin, Yao
2015-07-08 14:14             ` Takashi Iwai
2015-07-08 14:21               ` Liam Girdwood [this message]
2015-07-01 13:44 ` [PATCH v2 08/13] topology: Add DAPM object parser Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 09/13] topology: Add CTL parser Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 10/13] topology: Add Channel map parser Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 11/13] topology: Add binary file builder Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 12/13] topology: autotools: Add build support for topology core Liam Girdwood
2015-07-01 13:44 ` [PATCH v2 13/13] topology: doxygen: Add doxygen " Liam Girdwood

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=1436365275.2474.41.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.com \
    --cc=yao.jin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox