From: Jonathan Cameron <jic23@kernel.org>
To: Hartmut Knaack <knaack.h@gmx.de>,
linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [RFC]iio:industrialio-event fix error-handling in iio_device_add_event
Date: Wed, 01 Jan 2014 12:47:15 +0000 [thread overview]
Message-ID: <52C40E53.1040906@kernel.org> (raw)
In-Reply-To: <52C00D75.70302@gmx.de>
On 29/12/13 11:54, Hartmut Knaack wrote:
> __iio_add_chan_devattr returns -EBUSY, when registering the event-interface of
> ad799x, but iio_device_add_event does not catch it. So, handle it like in
> iio_device_add_info_mask_type. Not sure, if this is the right solution, but it
> makes the ad799x (and possibly others as well) usable.
>
> Signed-off-by: Hartmut Knaack <knaack.h@gmx.de>
I think the fix is correct, but I'm not entirely sure what is triggering
the bug in this particular driver. All of the elements of ad799x_events
are in mask separate so shared_by should be IIO_SEPARATE for all calls
to this function.
Lars, any idea's on what Hartmut is hitting?
Also, is the below patch as valid as it appears at first glance?
> ---
> diff --git a/drivers/iio/industrialio-event.c b/drivers/iio/industrialio-event.c
> index c10eab6..d37a907 100644
> --- a/drivers/iio/industrialio-event.c
> +++ b/drivers/iio/industrialio-event.c
> @@ -362,7 +362,9 @@ static int iio_device_add_event(struct iio_dev *indio_dev,
> &indio_dev->event_interface->dev_attr_list);
> kfree(postfix);
>
> - if (ret)
> + if ((ret == -EBUSY) && (shared_by != IIO_SEPARATE))
> + continue;
> + else if (ret < 0)
> return ret;
>
> attrcount++;
> --
> 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
>
next prev parent reply other threads:[~2014-01-01 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 11:54 [RFC]iio:industrialio-event fix error-handling in iio_device_add_event Hartmut Knaack
2014-01-01 12:47 ` Jonathan Cameron [this message]
2014-02-08 0:07 ` Hartmut Knaack
2014-02-08 10:14 ` Jonathan Cameron
2014-02-08 11:43 ` Hartmut Knaack
2014-02-08 12:08 ` Jonathan Cameron
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=52C40E53.1040906@kernel.org \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--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).