From: Jonathan Cameron <jic23@kernel.org>
To: Abhash Jha <abhashkumarjha123@gmail.com>
Cc: linux-iio@vger.kernel.org, songqiang1304521@gmail.com,
lars@metafoo.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] iio: proximity: vl53l0x-i2c: Added sensor ID check
Date: Sat, 7 Sep 2024 17:40:28 +0100 [thread overview]
Message-ID: <20240907174028.75840886@jic23-huawei> (raw)
In-Reply-To: <20240903035636.9559-2-abhashkumarjha123@gmail.com>
On Tue, 3 Sep 2024 09:26:35 +0530
Abhash Jha <abhashkumarjha123@gmail.com> wrote:
> The commit adds a check for the sensor's model ID. We read the model
> identification register (0xC0) and expect a value of 0xEE.
>
> Signed-off-by: Abhash Jha <abhashkumarjha123@gmail.com>
Hi Abhash,
Small comment on the message below
> ---
> drivers/iio/proximity/vl53l0x-i2c.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/proximity/vl53l0x-i2c.c b/drivers/iio/proximity/vl53l0x-i2c.c
> index 8d4f3f849..31d6aeb95 100644
> --- a/drivers/iio/proximity/vl53l0x-i2c.c
> +++ b/drivers/iio/proximity/vl53l0x-i2c.c
> @@ -39,8 +39,11 @@
>
> #define VL_REG_RESULT_INT_STATUS 0x13
> #define VL_REG_RESULT_RANGE_STATUS 0x14
> +#define VL_REG_IDENTIFICATION_MODEL_ID 0xC0
> #define VL_REG_RESULT_RANGE_STATUS_COMPLETE BIT(0)
>
> +#define VL53L0X_MODEL_ID_VAL 0xEE
> +
> struct vl53l0x_data {
> struct i2c_client *client;
> struct completion completion;
> @@ -223,6 +226,7 @@ static int vl53l0x_probe(struct i2c_client *client)
> struct vl53l0x_data *data;
> struct iio_dev *indio_dev;
> int error;
> + int ret;
>
> indio_dev = devm_iio_device_alloc(&client->dev, sizeof(*data));
> if (!indio_dev)
> @@ -237,6 +241,13 @@ static int vl53l0x_probe(struct i2c_client *client)
> I2C_FUNC_SMBUS_BYTE_DATA))
> return -EOPNOTSUPP;
>
> + ret = i2c_smbus_read_byte_data(data->client, VL_REG_IDENTIFICATION_MODEL_ID);
> + if (ret < 0)
> + return -EINVAL;
> +
> + if (ret != VL53L0X_MODEL_ID_VAL)
> + dev_info(&client->dev, "Received invalid model id: 0x%x", ret);
Unknown model id:
It's probably valid, we just don't know what it means!
> +
> data->vdd_supply = devm_regulator_get(&client->dev, "vdd");
> if (IS_ERR(data->vdd_supply))
> return dev_err_probe(&client->dev, PTR_ERR(data->vdd_supply),
> @@ -265,8 +276,6 @@ static int vl53l0x_probe(struct i2c_client *client)
>
> /* usage of interrupt is optional */
> if (client->irq) {
> - int ret;
> -
> init_completion(&data->completion);
>
> ret = vl53l0x_configure_irq(client, indio_dev);
next prev parent reply other threads:[~2024-09-07 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 3:56 [PATCH v3 0/2] Continuous mode support for VL53l0x Abhash Jha
2024-09-03 3:56 ` [PATCH v3 1/2] iio: proximity: vl53l0x-i2c: Added sensor ID check Abhash Jha
2024-09-07 16:40 ` Jonathan Cameron [this message]
2024-09-03 3:56 ` [PATCH v3 2/2] iio: proximity: vl53l0x-i2c: Added continuous mode support Abhash Jha
2024-09-07 16:51 ` 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=20240907174028.75840886@jic23-huawei \
--to=jic23@kernel.org \
--cc=abhashkumarjha123@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songqiang1304521@gmail.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