From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jagath Jog J <jagathjog1996@gmail.com>,
Dan Robertson <dan@dlrobertson.com>,
linux-iio <linux-iio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/9] iio: accel: bma400: Add triggered buffer support
Date: Sun, 1 May 2022 17:20:37 +0100 [thread overview]
Message-ID: <20220501172037.5f3d446f@jic23-huawei> (raw)
In-Reply-To: <CAHp75Vf5pS_TGm5ptN7TyNmhZe_Oz8pVmETT27VeC=BZk9+ezg@mail.gmail.com>
On Wed, 27 Apr 2022 14:34:57 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Wed, Apr 20, 2022 at 11:11 PM Jagath Jog J <jagathjog1996@gmail.com> wrote:
> >
> > Added trigger buffer support to read continuous acceleration
> > data from device with data ready interrupt which is mapped
> > to INT1 pin.
>
> LGTM,
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Agreed. A couple of 'comments' inline but no actual need to change anything.
One is contingent on a fix I've not sent out yet for the rest of IIO.
The other is potentially a minor improvement for the future.
Thanks,
Jonathan
>
> > Signed-off-by: Jagath Jog J <jagathjog1996@gmail.com>
> > ---
> > drivers/iio/accel/Kconfig | 2 +
> > drivers/iio/accel/bma400.h | 10 +-
> > drivers/iio/accel/bma400_core.c | 162 +++++++++++++++++++++++++++++++-
> > drivers/iio/accel/bma400_i2c.c | 2 +-
> > drivers/iio/accel/bma400_spi.c | 2 +-
> > 5 files changed, 170 insertions(+), 8 deletions(-)
> >
> > #include "bma400.h"
> >
> > @@ -61,6 +66,14 @@ struct bma400_data {
> > struct bma400_sample_freq sample_freq;
> > int oversampling_ratio;
> > int scale;
> > + struct iio_trigger *trig;
> > + /* Correct time stamp alignment */
> > + struct {
> > + __le16 buff[3];
> > + u8 temperature;
> > + s64 ts __aligned(8);
> > + } buffer ____cacheline_aligned;
If you are rolling again, could you change this to
__aligned(IIO_ALIGN); See
https://lore.kernel.org/linux-iio/20220419121241.00002e42@Huawei.com/
for why.
Note that I'll be sending a fix patch out for IIO_ALIGN to define
it as ARCH_KMALLOC_ALIGN in next few days.
If you'd pref not to get caught up in that, send it as it stands
and I'll fix up once that fix is in place. What's one more driver
on top of the 80+ I have to do anyway :)
> > + __le16 status;
> > };
> >
> > +
> > +static const unsigned long bma400_avail_scan_masks[] = {
> > + GENMASK(3, 0),
> > + 0
> > +};
> > +
> > static const struct iio_info bma400_info = {
> > .read_raw = bma400_read_raw,
> > .read_avail = bma400_read_avail,
> > @@ -814,7 +869,72 @@ static const struct iio_info bma400_info = {
> > .write_raw_get_fmt = bma400_write_raw_get_fmt,
> > };
> >
> > -int bma400_probe(struct device *dev, struct regmap *regmap, const char *name)
> > +static const struct iio_trigger_ops bma400_trigger_ops = {
> > + .set_trigger_state = &bma400_data_rdy_trigger_set_state,
> > + .validate_device = &iio_trigger_validate_own_device,
> > +};
> > +
> > +static irqreturn_t bma400_trigger_handler(int irq, void *p)
> > +{
> > + struct iio_poll_func *pf = p;
> > + struct iio_dev *indio_dev = pf->indio_dev;
> > + struct bma400_data *data = iio_priv(indio_dev);
> > + int ret, temp;
> > +
> > + /* Lock to protect the data->buffer */
> > + mutex_lock(&data->mutex);
> > +
> > + /* bulk read six registers, with the base being the LSB register */
> > + ret = regmap_bulk_read(data->regmap, BMA400_X_AXIS_LSB_REG,
> > + &data->buffer.buff, sizeof(data->buffer.buff));
> > + if (ret)
> > + goto unlock_err;
> > +
> > + ret = regmap_read(data->regmap, BMA400_TEMP_DATA_REG, &temp);
Given the temperature read is a separate action, it seems like you could sensible
add another entry to bma400_avail_scan_masks() for just the accelerometer axis
and then only perform this read if the temperature is requested.
It would be a feature though, so no need to have it in this patch if you
prefer not to.
> > + if (ret)
> > + goto unlock_err;
> > +
> > + data->buffer.temperature = temp;
> > +
> > + iio_push_to_buffers_with_timestamp(indio_dev, &data->buffer,
> > + iio_get_time_ns(indio_dev));
> > +
> > + mutex_unlock(&data->mutex);
> > + iio_trigger_notify_done(indio_dev->trig);
> > + return IRQ_HANDLED;
> > +
> > +unlock_err:
> > + mutex_unlock(&data->mutex);
> > + return IRQ_NONE;
> > +}
next prev parent reply other threads:[~2022-05-01 16:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 21:10 [PATCH v4 0/9] iio: accel: bma400: Add buffer, step and activity/inactivity Jagath Jog J
2022-04-20 21:10 ` [PATCH v4 1/9] iio: accel: bma400: Fix the scale min and max macro values Jagath Jog J
2022-04-27 12:28 ` Andy Shevchenko
2022-04-20 21:10 ` [PATCH v4 2/9] iio: accel: bma400: Reordering of header files Jagath Jog J
2022-04-20 21:10 ` [PATCH v4 3/9] iio: accel: bma400: conversion to device-managed function Jagath Jog J
2022-04-20 21:11 ` [PATCH v4 4/9] iio: accel: bma400: Add triggered buffer support Jagath Jog J
2022-04-27 12:34 ` Andy Shevchenko
2022-05-01 16:20 ` Jonathan Cameron [this message]
2022-05-01 20:25 ` Jagath Jog J
2022-05-07 16:00 ` Jonathan Cameron
2022-04-20 21:11 ` [PATCH v4 5/9] iio: accel: bma400: Add separate channel for step counter Jagath Jog J
2022-04-27 12:34 ` Andy Shevchenko
2022-04-27 21:01 ` Jagath Jog J
2022-04-20 21:11 ` [PATCH v4 6/9] iio: accel: bma400: Add step change event Jagath Jog J
2022-05-01 16:31 ` Jonathan Cameron
2022-05-01 20:27 ` Jagath Jog J
2022-04-20 21:11 ` [PATCH v4 7/9] iio: accel: bma400: Add activity recognition support Jagath Jog J
2022-04-20 21:11 ` [PATCH v4 8/9] iio: accel: bma400: Add debugfs register access support Jagath Jog J
2022-05-01 16:34 ` Jonathan Cameron
2022-04-20 21:11 ` [PATCH v4 9/9] iio: accel: bma400: Add support for activity and inactivity events Jagath Jog J
2022-04-21 6:45 ` kernel test robot
2022-04-24 16:20 ` Jonathan Cameron
2022-04-27 3:01 ` Jagath Jog J
2022-04-27 13:45 ` Andy Shevchenko
2022-04-26 11:04 ` [PATCH v4 0/9] iio: accel: bma400: Add buffer, step and activity/inactivity Andy Shevchenko
2022-04-26 11:05 ` Andy Shevchenko
2022-04-26 12:28 ` Jagath Jog J
2022-05-01 16:36 ` 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=20220501172037.5f3d446f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=dan@dlrobertson.com \
--cc=jagathjog1996@gmail.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).