From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio: light: gp2ap020a00f: fix iio_triggered_buffer_{predisable,postenable} positions
Date: Sat, 7 Mar 2020 15:52:20 +0000 [thread overview]
Message-ID: <20200307155220.2e238b0c@archlinux> (raw)
In-Reply-To: <20200306111137.23572-1-alexandru.ardelean@analog.com>
On Fri, 6 Mar 2020 13:11:37 +0200
Alexandru Ardelean <alexandru.ardelean@analog.com> wrote:
> The iio_triggered_buffer_{predisable,postenable} functions attach/detach
> the poll functions.
>
> For the predisable hook, the disable code should occur before detaching
> the poll func, and for the postenable hook, the poll func should be
> attached before the enable code.
>
> This change moves the postenable/predisable hooks into the correct
> positions.
>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
Seems unlikely anyone who knows this driver well will respond, so
applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to poke at it - maybe...
There is an odd warning I'm getting in here on x86 builds but it
has nothing to do with your patch so hopefully autobuilders won't
moan about.
thanks,
Jonathan
> ---
>
> Changelog v1 -> v2:
> * Fix omitted compiler warnings: 'warning: unused label 'error_unlock' [-Wunused-label]'
> Reported-by: kbuild test robot <lkp@intel.com>
>
> drivers/iio/light/gp2ap020a00f.c | 23 ++++++++++++-----------
> 1 file changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/iio/light/gp2ap020a00f.c b/drivers/iio/light/gp2ap020a00f.c
> index 4d70c5bf35da..7fbbce0d4bc7 100644
> --- a/drivers/iio/light/gp2ap020a00f.c
> +++ b/drivers/iio/light/gp2ap020a00f.c
> @@ -1390,6 +1390,12 @@ static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
>
> mutex_lock(&data->lock);
>
> + err = iio_triggered_buffer_postenable(indio_dev);
> + if (err < 0) {
> + mutex_unlock(&data->lock);
> + return err;
> + }
> +
> /*
> * Enable triggers according to the scan_mask. Enabling either
> * LIGHT_CLEAR or LIGHT_IR scan mode results in enabling ALS
> @@ -1420,14 +1426,12 @@ static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
> goto error_unlock;
>
> data->buffer = kmalloc(indio_dev->scan_bytes, GFP_KERNEL);
> - if (!data->buffer) {
> + if (!data->buffer)
> err = -ENOMEM;
> - goto error_unlock;
> - }
> -
> - err = iio_triggered_buffer_postenable(indio_dev);
>
> error_unlock:
> + if (err < 0)
> + iio_triggered_buffer_predisable(indio_dev);
> mutex_unlock(&data->lock);
>
> return err;
> @@ -1436,14 +1440,10 @@ static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
> static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
> {
> struct gp2ap020a00f_data *data = iio_priv(indio_dev);
> - int i, err;
> + int i, err = 0;
>
> mutex_lock(&data->lock);
>
> - err = iio_triggered_buffer_predisable(indio_dev);
> - if (err < 0)
> - goto error_unlock;
> -
> for_each_set_bit(i, indio_dev->active_scan_mask,
> indio_dev->masklength) {
> switch (i) {
> @@ -1465,7 +1465,8 @@ static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
> if (err == 0)
> kfree(data->buffer);
>
> -error_unlock:
> + iio_triggered_buffer_predisable(indio_dev);
> +
> mutex_unlock(&data->lock);
>
> return err;
prev parent reply other threads:[~2020-03-07 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 8:26 [PATCH] iio: light: gp2ap020a00f: fix iio_triggered_buffer_{predisable,postenable} positions Alexandru Ardelean
2020-03-06 11:11 ` [PATCH v2] " Alexandru Ardelean
2020-03-07 15:52 ` 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=20200307155220.2e238b0c@archlinux \
--to=jic23@kernel.org \
--cc=alexandru.ardelean@analog.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).