From: Jonathan Cameron <jic23@kernel.org>
To: Hartmut Knaack <knaack.h@gmx.de>,
Linus Walleij <linus.walleij@linaro.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2] iio: generic_buffer: be helpful about enabling channels
Date: Sat, 15 Aug 2015 16:18:53 +0100 [thread overview]
Message-ID: <55CF585D.9080408@kernel.org> (raw)
In-Reply-To: <55CA3D04.6050005@gmx.de>
On 11/08/15 19:20, Hartmut Knaack wrote:
> Linus Walleij schrieb am 10.08.2015 um 10:55:
>> Currently if generic_buffer is invoked without first enabling any
>> channels in scan_elements/*_en, it will fail unable to enable the
>> buffer because bytes_per_datum inside the kernel will be zero if
>> no channels are available.
>>
>> It is implied that the user of the program should enable channels
>> manually or with a script before executing generic_buffer.
>>
>> Be more helpful by stopping execution if no enabled channels can
>> be found, and print a helptext that will tell you what is wrong
>> and what needs to be done.
>>
>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> Acked-by: Hartmut Knaack <knaack.h@gmx.de>
Applied. Thanks for clearing this up.
Jonathan
>> ---
>> ChangeLog v1->v2:
>> - Rebased on the "togreg" branch
>> - Print errors to stderr as requested by Hartmut
>> ---
>> tools/iio/generic_buffer.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/tools/iio/generic_buffer.c b/tools/iio/generic_buffer.c
>> index 9f7b85bf6ada..01c4f67801e0 100644
>> --- a/tools/iio/generic_buffer.c
>> +++ b/tools/iio/generic_buffer.c
>> @@ -328,6 +328,15 @@ int main(int argc, char **argv)
>> "diag %s\n", dev_dir_name);
>> goto error_free_triggername;
>> }
>> + if (!num_channels) {
>> + fprintf(stderr,
>> + "No channels are enabled, we have nothing to scan.\n");
>> + fprintf(stderr, "Enable channels manually in "
>> + FORMAT_SCAN_ELEMENTS_DIR
>> + "/*_en and try again.\n", dev_dir_name);
>> + ret = -ENOENT;
>> + goto error_free_triggername;
>> + }
>>
>> /*
>> * Construct the directory name for the associated buffer.
>>
>
> --
> 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
>
prev parent reply other threads:[~2015-08-15 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 8:55 [PATCH v2] iio: generic_buffer: be helpful about enabling channels Linus Walleij
2015-08-11 18:20 ` Hartmut Knaack
2015-08-15 15:18 ` 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=55CF585D.9080408@kernel.org \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@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).