linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Daniel Baluta <daniel.baluta@gmail.com>,
	Irina Tirdea <irina.tirdea@intel.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools: iio: generic_buffer: Fix generic scale extraction
Date: Sat, 28 Mar 2015 11:03:01 +0000	[thread overview]
Message-ID: <55168A65.6020200@kernel.org> (raw)
In-Reply-To: <CAEnQRZBFjx9y6QgNOFFdeyNF5960X+yNLSi6kkMCTNLOb2kiRw@mail.gmail.com>

On 27/03/15 12:57, Daniel Baluta wrote:
> On Fri, Mar 27, 2015 at 1:53 PM, Irina Tirdea <irina.tirdea@intel.com> wrote:
>> When using generic_buffer to read data, the scale is not properly
>> detected for scale shared by type. This is caused by a problem
>> with the generation of generic name out of the full name.
>> E.g.: for current->name in_accel_z, the extracted generic name
>> is "in" (when it should be "in_accel"). This is used in generic_buffer
>> to generate scale and offset paths (in_accel_scale).
>>
>> Consider the in_ or out_ prefix when extracting the generic name
>> from the full name.
>>
>> Signed-off-by: Irina Tirdea <irina.tirdea@intel.com>
> 
> Reviewed-by: Daniel Baluta <daniel.baluta@intel.com>
Applied to the togreg branch of iio.git.  Might be worth backporting
once it is in mainline.

J
> 
>> ---
>>  tools/iio/iio_utils.c | 20 +++++++++++++++++---
>>  1 file changed, 17 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/iio/iio_utils.c b/tools/iio/iio_utils.c
>> index aea9282..63fbf99 100644
>> --- a/tools/iio/iio_utils.c
>> +++ b/tools/iio/iio_utils.c
>> @@ -18,6 +18,11 @@
>>
>>  const char *iio_dir = "/sys/bus/iio/devices/";
>>
>> +static char * const iio_direction[] = {
>> +       "in",
>> +       "out",
>> +};
>> +
>>  /**
>>   * iioutils_break_up_name() - extract generic name from full channel name
>>   * @full_name: the full channel name
>> @@ -28,10 +33,19 @@ int iioutils_break_up_name(const char *full_name,
>>  {
>>         char *current;
>>         char *w, *r;
>> -       char *working;
>> +       char *working, *prefix = "";
>> +       int i;
>>
>> -       current = strdup(full_name);
>> +       for (i = 0; i < sizeof(iio_direction) / sizeof(iio_direction[0]); i++)
>> +               if (!strncmp(full_name, iio_direction[i],
>> +                            strlen(iio_direction[i]))) {
>> +                       prefix = iio_direction[i];
>> +                       break;
>> +               }
>> +
>> +       current = strdup(full_name + strlen(prefix) + 1);
>>         working = strtok(current, "_\0");
>> +
>>         w = working;
>>         r = working;
>>
>> @@ -43,7 +57,7 @@ int iioutils_break_up_name(const char *full_name,
>>                 r++;
>>         }
>>         *w = '\0';
>> -       *generic_name = strdup(working);
>> +       asprintf(generic_name, "%s_%s", prefix, working);
>>         free(current);
>>
>>         return 0;
>> --
>> 1.9.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2015-03-28 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 11:53 [PATCH] tools: iio: generic_buffer: Fix generic scale extraction Irina Tirdea
2015-03-27 12:57 ` Daniel Baluta
2015-03-28 11:03   ` Jonathan Cameron [this message]

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=55168A65.6020200@kernel.org \
    --to=jic23@kernel.org \
    --cc=daniel.baluta@gmail.com \
    --cc=irina.tirdea@intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).