Linux IIO development
 help / color / mirror / Atom feed
From: Francesco Lavra <flavra@baylibre.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/9] iio: imu: st_lsm6dsx: make event_settings more generic
Date: Fri, 31 Oct 2025 09:08:14 +0100	[thread overview]
Message-ID: <a1e678aec0d978408704970faa16fccef4ea214d.camel@baylibre.com> (raw)
In-Reply-To: <aQOV6cDVTJ-5uyCz@lore-desk>

On Thu, 2025-10-30 at 17:44 +0100, Lorenzo Bianconi wrote:
> On Oct 30, Francesco Lavra wrote:
> > The st_lsm6dsx_event_settings structure contains fields specific
> > for one event type (wakeup). In preparation for adding support for
> > more event types, introduce an event id enum and a generic event
> > source structure, and replace wakeup-specific data in struct
> > st_lsm6dsx_event_settings with an array of event source structures.
> > 
> > Signed-off-by: Francesco Lavra <flavra@baylibre.com>
> > ---
> >  drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h      |  21 ++-
> >  drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 136 +++++++++++--------
> >  2 files changed, 96 insertions(+), 61 deletions(-)
> > 
> > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > index db863bd1898d..05689887f7ec 100644
> > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > @@ -221,14 +221,23 @@ struct st_lsm6dsx_shub_settings {
> >         u8 pause;
> >  };
> >  
> > +enum st_lsm6dsx_event_id {
> > +       ST_LSM6DSX_EVENT_WAKEUP,
> > +       ST_LSM6DSX_EVENT_MAX
> > +};
> > +
> > +struct st_lsm6dsx_event_src {
> > +       struct st_lsm6dsx_reg value;
> > +       u8 status_reg;
> > +       u8 status_mask;
> > +       u8 status_x_mask;
> > +       u8 status_y_mask;
> > +       u8 status_z_mask;
> 
> you can use st_lsm6dsx_reg here.

Do you mean replacing the status_* fields with 4 struct st_lsm6dsx_reg
fields (one for the global status flag, and one for each axis)?

  reply	other threads:[~2025-10-31  8:08 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30  7:27 [PATCH 0/9] st_lsm6dsx: add tap event detection Francesco Lavra
2025-10-30  7:27 ` [PATCH 1/9] iio: imu: st_lsm6dsx: dynamically initialize iio_chan_spec data Francesco Lavra
2025-10-30  7:57   ` Andy Shevchenko
2025-10-30 11:03     ` Francesco Lavra
2025-10-30 16:42   ` Lorenzo Bianconi
2025-10-31  8:04     ` Francesco Lavra
2025-10-31  8:09       ` Andy Shevchenko
2025-10-31  8:26     ` Francesco Lavra
2025-10-31  8:32       ` Andy Shevchenko
2025-10-31 11:43         ` Francesco Lavra
2025-11-02 11:16   ` Jonathan Cameron
2025-11-03  9:24     ` Francesco Lavra
2025-11-09 13:32       ` Jonathan Cameron
2025-10-30  7:27 ` [PATCH 2/9] iio: imu: st_lsm6dsx: make event_settings more generic Francesco Lavra
2025-10-30 16:44   ` Lorenzo Bianconi
2025-10-31  8:08     ` Francesco Lavra [this message]
2025-10-30  7:27 ` [PATCH 3/9] iio: imu: st_lsm6dsx: move wakeup event enable mask to event_src Francesco Lavra
2025-10-30  7:59   ` Andy Shevchenko
2025-10-30  7:27 ` [PATCH 4/9] iio: imu: st_lsm6dsx: dynamically allocate iio_event_spec structs Francesco Lavra
2025-11-02 11:22   ` Jonathan Cameron
2025-10-30  7:27 ` [PATCH 5/9] iio: imu: st_lsm6dsx: rework code to check for enabled events Francesco Lavra
2025-10-30  7:27 ` [PATCH 6/9] iio: imu: st_lsm6dsx: remove event_threshold field from hw struct Francesco Lavra
2025-10-30  8:01   ` Andy Shevchenko
2025-10-30 11:10     ` Francesco Lavra
2025-10-30 13:49       ` Andy Shevchenko
2025-11-02 11:29         ` Jonathan Cameron
2025-11-02 13:45           ` Andy Shevchenko
2025-11-03  9:34             ` Francesco Lavra
2025-11-03  9:40               ` Andy Shevchenko
2025-11-03 14:53               ` David Lechner
2025-11-09 13:31                 ` Jonathan Cameron
2025-10-30  7:27 ` [PATCH 7/9] iio: imu: st_lsm6dsx: make event management functions generic Francesco Lavra
2025-10-30  8:15   ` Andy Shevchenko
2025-10-30 11:17     ` Francesco Lavra
2025-10-30 13:36       ` Andy Shevchenko
2025-11-02 11:33   ` Jonathan Cameron
2025-10-30  7:27 ` [PATCH 8/9] iio: imu: st_lsm6dsx: add event configurability on a per axis basis Francesco Lavra
2025-10-30  8:24   ` Andy Shevchenko
2025-10-30 11:23     ` Francesco Lavra
2025-10-30 13:56       ` Andy Shevchenko
2025-11-17 19:23         ` Francesco Lavra
2025-11-18 10:44           ` Andy Shevchenko
2025-11-18 11:01             ` Francesco Lavra
2025-11-20  9:05               ` Andy Shevchenko
2025-11-20 11:43                 ` Francesco Lavra
2025-11-20 13:59                   ` Andy Shevchenko
2025-11-20 18:31                     ` Andy Shevchenko
2025-11-21  9:14                       ` Francesco Lavra
2025-11-21  9:31                         ` Andy Shevchenko
2025-11-21 14:57                           ` Francesco Lavra
2025-12-07 15:11                             ` Jonathan Cameron
2025-10-30  7:27 ` [PATCH 9/9] iio: imu: st_lsm6dsx: add tap event detection Francesco Lavra

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=a1e678aec0d978408704970faa16fccef4ea214d.camel@baylibre.com \
    --to=flavra@baylibre.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nuno.sa@analog.com \
    /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