From: Joshua Crofts <crofts@kernel.org>
To: Xiangwu Lai <laixiangwu@cmss.chinamobile.com>
Cc: jic23@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, andy@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com
Subject: Re: [PATCH v4 1/2] iio: gyro: mpu3050: Split data ready trigger enable/disable into helpers
Date: Thu, 5 Nov 2026 16:31:18 +0100 [thread overview]
Message-ID: <20261105163118.00001538@kernel.org> (raw)
In-Reply-To: <20261104040008.1458-2-laixiangwu@cmss.chinamobile.com>
On Wed, 4 Nov 2026 12:00:06 +0800
Xiangwu Lai <laixiangwu@cmss.chinamobile.com> wrote:
> From: laixiangwu <laixiangwu@cmss.chinamobile.com>
>
> mpu3050_drdy_trigger_set_state() implements both the enable and the
> disable path of the data ready trigger in the two legs of a large
> if/else statement.
>
> Split the two legs out into separate mpu3050_drdy_trigger_enable()
> and mpu3050_drdy_trigger_disable() helpers and reduce
> mpu3050_drdy_trigger_set_state() to dispatching to the appropriate
> one. This is a pure code move with no functional change, done to make
> the error handling of the enable path easier to read.
>
> Signed-off-by: laixiangwu <laixiangwu@cmss.chinamobile.com>
> ---
>
> Changes in v4:
> - use an else for the either/or dispatch in
> mpu3050_drdy_trigger_set_state(), as suggested by the reviewer.
>
> Changes in v3:
> - none; reposted in a new top-level thread.
>
> Link: https://lore.kernel.org/r/20261103092002.1332-2-laixiangwu@cmss.chinamobile.com
> Link: https://lore.kernel.org/r/20261101092327.197-2-laixiangwu@cmss.chinamobile.com
> drivers/iio/gyro/mpu3050-core.c | 173 ++++++++++++++++++--------------
> 1 file changed, 99 insertions(+), 74 deletions(-)
>
> diff --git a/drivers/iio/gyro/mpu3050-core.c b/drivers/iio/gyro/mpu3050-core.c
> index 07c0f9011..62e416df3 100644
> --- a/drivers/iio/gyro/mpu3050-core.c
> +++ b/drivers/iio/gyro/mpu3050-core.c
> @@ -946,103 +946,128 @@ static irqreturn_t mpu3050_irq_thread(int irq, void *p)
> }
>
> /**
> - * mpu3050_drdy_trigger_set_state() - set data ready interrupt state
> - * @trig: trigger instance
> - * @enable: true if trigger should be enabled, false to disable
> + * mpu3050_drdy_trigger_enable() - enable the data ready trigger
> + * @mpu3050: device to configure
> + *
> + * Power up the device, enable the FIFO and configure the data ready
> + * interrupt.
> */
> -static int mpu3050_drdy_trigger_set_state(struct iio_trigger *trig,
> - bool enable)
> +static int mpu3050_drdy_trigger_enable(struct mpu3050 *mpu3050)
> {
> - struct iio_dev *indio_dev = iio_trigger_get_drvdata(trig);
> - struct mpu3050 *mpu3050 = iio_priv(indio_dev);
> unsigned int val;
> int ret;
>
> - /* Disabling trigger: disable interrupt and return */
> - if (!enable) {
> - /* Disable all interrupts */
> - ret = regmap_write(mpu3050->map,
> - MPU3050_INT_CFG,
> - 0);
> - if (ret)
> - dev_err(mpu3050->dev, "error disabling IRQ\n");
> + pm_runtime_get_sync(mpu3050->dev);
> + mpu3050->hw_irq_trigger = true;
>
> - /* Clear IRQ flag */
> - ret = regmap_read(mpu3050->map, MPU3050_INT_STATUS, &val);
> - if (ret)
> - dev_err(mpu3050->dev, "error clearing IRQ status\n");
> + /* Disable all things in the FIFO */
> + ret = regmap_write(mpu3050->map, MPU3050_FIFO_EN, 0);
> + if (ret)
> + return ret;
>
> - /* Disable all things in the FIFO and reset it */
> - ret = regmap_write(mpu3050->map, MPU3050_FIFO_EN, 0);
> - if (ret)
> - dev_err(mpu3050->dev, "error disabling FIFO\n");
> + /* Reset and enable the FIFO */
> + ret = regmap_set_bits(mpu3050->map, MPU3050_USR_CTRL,
> + MPU3050_USR_CTRL_FIFO_EN |
> + MPU3050_USR_CTRL_FIFO_RST);
> + if (ret)
> + return ret;
>
Not sure if it's just me, but reading this patch is pretty hard;
please use histogram as your default diff algorithm [1] when sending
a patch next time.
Otherwise LGTM (after viewing with the histogram option :)).
Reviewed-by: Joshua Crofts <crofts@kernel.org>
[1] https://git-scm.com/docs/diff-algorithm-option.html
--
Kind regards,
Joshua Crofts
next prev parent reply other threads:[~2026-11-05 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 4:00 [PATCH v4 0/2] iio: gyro: mpu3050: Fix runtime PM refcount leak in trigger enable path Xiangwu Lai
2026-11-04 4:00 ` [PATCH v4 1/2] iio: gyro: mpu3050: Split data ready trigger enable/disable into helpers Xiangwu Lai
2026-11-05 15:31 ` Joshua Crofts [this message]
2026-11-04 4:00 ` [PATCH v4 2/2] iio: gyro: mpu3050: Fix runtime PM refcount leak in trigger enable path Xiangwu Lai
2026-11-04 11:58 ` Andy Shevchenko
2026-11-05 8:18 ` Xiangwu Lai
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=20261105163118.00001538@kernel.org \
--to=crofts@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=laixiangwu@cmss.chinamobile.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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