From: Jonathan Cameron <jic23@kernel.org>
To: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
Fawzi Khaber <fawzi.khaber@tdk.com>
Subject: Re: [PATCH] iio: imu: inv_icm42600: Fix I2C init possible nack
Date: Sat, 2 Apr 2022 17:25:15 +0100 [thread overview]
Message-ID: <20220402172515.1d1dcee5@jic23-huawei> (raw)
In-Reply-To: <20220331091121.2680-1-jmaneyrol@invensense.com>
On Thu, 31 Mar 2022 11:11:21 +0200
Jean-Baptiste Maneyrol <jmaneyrol@invensense.com> wrote:
> From: Fawzi Khaber <fawzi.khaber@tdk.com>
>
> This register write to REG_INTF_CONFIG6 enables a spike filter that
> is impacting the line and can prevent the I2C ACK to be seen by the
> controller. So we don't test the return value.
>
> Signed-off-by: Fawzi Khaber <fawzi.khaber@tdk.com>
Jean-Baptiste, this needs your sign-off as well as you were part of the
path the patch is taking to mainline (see the DCO stuff in submitting
patches).
Thanks,
Jonathan
> ---
> drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c b/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> index 33d9afb1ba91..9c1e373a5daf 100644
> --- a/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> +++ b/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> @@ -18,12 +18,16 @@ static int inv_icm42600_i2c_bus_setup(struct inv_icm42600_state *st)
> unsigned int mask, val;
> int ret;
>
> - /* setup interface registers */
> - ret = regmap_update_bits(st->map, INV_ICM42600_REG_INTF_CONFIG6,
> + /*
> + * setup interface registers
> + * This register write to REG_INTF_CONFIG6 enables a spike filter that
> + * is impacting the line and can prevent the I2C ACK to be seen by the
> + * controller. So we don't test the return value.
> + */
> + regmap_update_bits(st->map, INV_ICM42600_REG_INTF_CONFIG6,
> INV_ICM42600_INTF_CONFIG6_MASK,
> INV_ICM42600_INTF_CONFIG6_I3C_EN);
> - if (ret)
> - return ret;
> +
Drop this additional blank line. One is enough!
>
> ret = regmap_update_bits(st->map, INV_ICM42600_REG_INTF_CONFIG4,
> INV_ICM42600_INTF_CONFIG4_I3C_BUS_ONLY, 0);
> --
> 2.25.1
prev parent reply other threads:[~2022-04-02 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 9:11 [PATCH] iio: imu: inv_icm42600: Fix I2C init possible nack Jean-Baptiste Maneyrol
2022-04-02 16:25 ` 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=20220402172515.1d1dcee5@jic23-huawei \
--to=jic23@kernel.org \
--cc=fawzi.khaber@tdk.com \
--cc=jmaneyrol@invensense.com \
--cc=lars@metafoo.de \
--cc=linux-iio@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