From: Jonathan Cameron <jic23@kernel.org>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: linux-iio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Denis Ciocca <denis.ciocca@st.com>
Subject: Re: [PATCH] iio: st_sensors: relax WhoAmI check in st_sensors_verify_id()
Date: Sat, 29 Jun 2024 19:44:16 +0100 [thread overview]
Message-ID: <20240629194416.535953ff@jic23-huawei> (raw)
In-Reply-To: <20240625082800.62305-1-kauschluss@disroot.org>
On Tue, 25 Jun 2024 13:57:55 +0530
Kaustabh Chakraborty <kauschluss@disroot.org> wrote:
> Hard matching against the WhoAmI values isn't ideal for using devices
> which are compatible with existing ones. Instead of raising an error,
> issue a warning instead, thus allowing the driver to continue probing.
>
> Suggested-by: Jonathan Cameron <jic23@kernel.org>
> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
LGTM. I've +CC'd a few more people who might take a look.
In meantime I'll queue it up.
Applied to the togreg branch of iio.git and pushed out as testing for
0-day to take a look and see what we missed.
Thanks,
Jonathan
> ---
> drivers/iio/common/st_sensors/st_sensors_core.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/iio/common/st_sensors/st_sensors_core.c b/drivers/iio/common/st_sensors/st_sensors_core.c
> index c77d7bdcc121..c69399ac6657 100644
> --- a/drivers/iio/common/st_sensors/st_sensors_core.c
> +++ b/drivers/iio/common/st_sensors/st_sensors_core.c
> @@ -606,10 +606,9 @@ int st_sensors_verify_id(struct iio_dev *indio_dev)
> }
>
> if (sdata->sensor_settings->wai != wai) {
> - dev_err(&indio_dev->dev,
> + dev_warn(&indio_dev->dev,
> "%s: WhoAmI mismatch (0x%x).\n",
> indio_dev->name, wai);
> - return -EINVAL;
> }
> }
>
prev parent reply other threads:[~2024-06-29 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 8:27 [PATCH] iio: st_sensors: relax WhoAmI check in st_sensors_verify_id() Kaustabh Chakraborty
2024-06-29 18:44 ` 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=20240629194416.535953ff@jic23-huawei \
--to=jic23@kernel.org \
--cc=denis.ciocca@st.com \
--cc=kauschluss@disroot.org \
--cc=linus.walleij@linaro.org \
--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