devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Rishi Gupta <gupt21@gmail.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 5/7] iio: light: veml6030: update sensor resolution
Date: Sun, 15 Sep 2024 10:31:11 +0200	[thread overview]
Message-ID: <5199bc7c-c3fe-49e8-9122-78b476c4aa90@gmail.com> (raw)
In-Reply-To: <20240914155716.09496630@jic23-huawei>

On 14/09/2024 16:57, Jonathan Cameron wrote:
> On Fri, 13 Sep 2024 15:19:00 +0200
> Javier Carrasco <javier.carrasco.cruz@gmail.com> wrote:
> 
>> The driver still uses the sensor resolution provided in the datasheet
>> until Rev. 1.6, 28-Apr-2022, which was updated with Rev 1.7,
>> 28-Nov-2023. The original ambient light resolution has been updated from
>> 0.0036 lx/ct to 0.0042 lx/ct, which is the value that can be found in
>> the current device datasheet.
>>
>> Update the default resolution for IT = 100 ms and GAIN = 1/8 from the
>> original 4608 mlux/cnt to the current value from the "Resolution and
>> maximum detection range" table (Application Note 84367, page 5), 5376
>> mlux/cnt.
>>
>> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> Interesting.  So does the datasheet say this was fixing an error, or
> is there any chance there are different versions of the chip out there?
> 
> Also, should we treat this as a fix?  I think we probably should given
> we don't really want stable kernels to have wrong data being reported.
> If so, please reply with a fixes tag.
> 
> Jonathan
>

According to the Product Information Notification (link in the cover
letter):

"Reason for Change: Adjusted resolution as this was wrongly stated in
the current datasheet."

"If resolution is defined in the particular application by the customer,
no changes in the system should be made. In the case resolution was
taken from the datasheet or app note, this has to be adjusted accordingly."

Which means that stable kernels are using the wrong resolution. I don't
know what IIO usually does in such cases, because a fix could
potentially make existing applications return "wrong data". If that is
alright, and applications are meant to be adjusted after the kernel
update, I have no problems to make this patch as a fix and add the
stable tag.

Best regards,
Javier Carrasco

>> ---
>>  drivers/iio/light/veml6030.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/iio/light/veml6030.c b/drivers/iio/light/veml6030.c
>> index 5d4c2e35b987..d5add040d0b3 100644
>> --- a/drivers/iio/light/veml6030.c
>> +++ b/drivers/iio/light/veml6030.c
>> @@ -779,7 +779,7 @@ static int veml6030_hw_init(struct iio_dev *indio_dev)
>>  
>>  	/* Cache currently active measurement parameters */
>>  	data->cur_gain = 3;
>> -	data->cur_resolution = 4608;
>> +	data->cur_resolution = 5376;
>>  	data->cur_integration_time = 3;
>>  
>>  	return ret;
>>
> 


  reply	other threads:[~2024-09-15  8:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 13:18 [PATCH 0/7] iio: light: veml6030: fix issues and add support for veml6035 Javier Carrasco
2024-09-13 13:18 ` [PATCH 1/7] dt-bindings: iio: light: veml6030: rename to add manufacturer Javier Carrasco
2024-09-13 16:53   ` Conor Dooley
2024-09-14 14:52     ` Jonathan Cameron
2024-09-13 13:18 ` [PATCH 2/7] dt-bindings: iio: light: veml6030: add veml6035 Javier Carrasco
2024-09-13 16:55   ` Conor Dooley
2024-09-13 13:18 ` [PATCH 3/7] iio: light: veml6030: fix IIO device retrieval from embedded device Javier Carrasco
2024-09-14 14:51   ` Jonathan Cameron
2024-09-13 13:18 ` [PATCH 4/7] iio: light: veml6030: make use of regmap_set_bits() Javier Carrasco
2024-09-14 14:54   ` Jonathan Cameron
2024-09-13 13:19 ` [PATCH 5/7] iio: light: veml6030: update sensor resolution Javier Carrasco
2024-09-14 14:57   ` Jonathan Cameron
2024-09-15  8:31     ` Javier Carrasco [this message]
2024-09-28 14:38       ` Jonathan Cameron
2024-09-13 13:19 ` [PATCH 6/7] iio: light: veml6030: add set up delay after any power on sequence Javier Carrasco
2024-09-14 14:59   ` Jonathan Cameron
2024-09-13 13:19 ` [PATCH 7/7] iio: light: veml6030: add support for veml6035 Javier Carrasco
2024-09-14 16:03   ` Jonathan Cameron
2024-09-16  6:19     ` Javier Carrasco
2024-09-28 14:40       ` 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=5199bc7c-c3fe-49e8-9122-78b476c4aa90@gmail.com \
    --to=javier.carrasco.cruz@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gupt21@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).