From: Jonathan Cameron <jic23@kernel.org>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>
Subject: Re: [PATCH] iio: light: isl29125: fix iio_triggered_buffer_{predisable,postenable} positions
Date: Mon, 13 Apr 2020 18:04:39 +0100 [thread overview]
Message-ID: <20200413180439.61cbf7b6@archlinux> (raw)
In-Reply-To: <5ced40e32260e5e99ca37dcf8ecdc77b25eb5153.camel@analog.com>
On Wed, 25 Mar 2020 11:42:31 +0000
"Ardelean, Alexandru" <alexandru.Ardelean@analog.com> wrote:
> On Wed, 2020-03-04 at 10:24 +0200, Alexandru Ardelean 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 reworks the predisable/postenable hooks so that the pollfunc is
> > attached/detached in the correct position.
> > It also balances the calls a bit, by grouping the preenable and the
> > iio_triggered_buffer_postenable() into a single
> > isl29125_buffer_postenable() function.
>
> ping on this patch
Long enough. Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.
Thanks,
Jonathan
>
> >
> > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> > ---
> > drivers/iio/light/isl29125.c | 28 +++++++++++++++++++---------
> > 1 file changed, 19 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/iio/light/isl29125.c b/drivers/iio/light/isl29125.c
> > index e37894f0ae0b..95611f5eff01 100644
> > --- a/drivers/iio/light/isl29125.c
> > +++ b/drivers/iio/light/isl29125.c
> > @@ -213,13 +213,24 @@ static const struct iio_info isl29125_info = {
> > .attrs = &isl29125_attribute_group,
> > };
> >
> > -static int isl29125_buffer_preenable(struct iio_dev *indio_dev)
> > +static int isl29125_buffer_postenable(struct iio_dev *indio_dev)
> > {
> > struct isl29125_data *data = iio_priv(indio_dev);
> > + int err;
> > +
> > + err = iio_triggered_buffer_postenable(indio_dev);
> > + if (err)
> > + return err;
> >
> > data->conf1 |= ISL29125_MODE_RGB;
> > - return i2c_smbus_write_byte_data(data->client, ISL29125_CONF1,
> > + err = i2c_smbus_write_byte_data(data->client, ISL29125_CONF1,
> > data->conf1);
> > + if (err) {
> > + iio_triggered_buffer_predisable(indio_dev);
> > + return err;
> > + }
> > +
> > + return 0;
> > }
> >
> > static int isl29125_buffer_predisable(struct iio_dev *indio_dev)
> > @@ -227,19 +238,18 @@ static int isl29125_buffer_predisable(struct iio_dev
> > *indio_dev)
> > struct isl29125_data *data = iio_priv(indio_dev);
> > int ret;
> >
> > - ret = iio_triggered_buffer_predisable(indio_dev);
> > - if (ret < 0)
> > - return ret;
> > -
> > data->conf1 &= ~ISL29125_MODE_MASK;
> > data->conf1 |= ISL29125_MODE_PD;
> > - return i2c_smbus_write_byte_data(data->client, ISL29125_CONF1,
> > + ret = i2c_smbus_write_byte_data(data->client, ISL29125_CONF1,
> > data->conf1);
> > +
> > + iio_triggered_buffer_predisable(indio_dev);
> > +
> > + return ret;
> > }
> >
> > static const struct iio_buffer_setup_ops isl29125_buffer_setup_ops = {
> > - .preenable = isl29125_buffer_preenable,
> > - .postenable = &iio_triggered_buffer_postenable,
> > + .postenable = isl29125_buffer_postenable,
> > .predisable = isl29125_buffer_predisable,
> > };
> >
prev parent reply other threads:[~2020-04-13 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 8:24 [PATCH] iio: light: isl29125: fix iio_triggered_buffer_{predisable,postenable} positions Alexandru Ardelean
2020-03-25 11:42 ` Ardelean, Alexandru
2020-04-13 17:04 ` 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=20200413180439.61cbf7b6@archlinux \
--to=jic23@kernel.org \
--cc=alexandru.Ardelean@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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