From: "Javier Carrasco" <javier.carrasco.cruz@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Rishi Gupta" <gupt21@gmail.com>,
"Matti Vaittinen" <mazziesaccount@gmail.com>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v2 0/4] iio: light: fix scale in veml6030
Date: Sat, 25 Jan 2025 21:12:57 +0100 [thread overview]
Message-ID: <D7BFFUH97D61.25C1T8JHA8WES@gmail.com> (raw)
In-Reply-To: <20250125123331.646e8cf8@jic23-huawei>
On Sat Jan 25, 2025 at 1:33 PM CET, Jonathan Cameron wrote:
> On Sun, 19 Jan 2025 18:31:57 +0100
> Javier Carrasco <javier.carrasco.cruz@gmail.com> wrote:
>
> > This series follows a similar approach as recently used for the veml3235
> > by using iio-gts to manage the scale as stated in the ABI. In its
> > current form, the driver exposes the hardware gain instead of the
> > multiplier for the raw value to obtain a value in lux.
> >
> > Although this driver and the veml3235 have many similarities, there are
> > two main differences in this series compared to the one used to fix the
> > other driver:
> >
> > - The veml6030 has fractional gains, which are not supported by the
> > iio-gts helpers. My first attempt was adding support for them, but
> > that made the whole iio-gts implementation more complex, cumbersome,
> > and the risk of affecting existing clients was not negligible.
> > Instead, a x8 factor has been used for the hardware gain to present
> > the minimum value (x0.125) as x1, keeping linearity. The scales
> > iio-gts generates are therefore right without any extra conversion,
> > and they match the values provided in the different datasheets.
> >
> > - This driver included a processed value for the ambient light, maybe
> > because the scale did not follow the ABI and the conversion was not
> > direct. To avoid breaking userspace, the functionality has been kept,
> > but of course using the fixed scales. In order to ease the
> > calculations, iio_gts_get_total_gain() has been exported to avoid
> > working directly with the scale in NANO, that would require 64-bit
> > operations.
> >
> > To ease the usage of the iio-gts selectors, patches to support regfields
> > and caching has been included.
> >
> > This issue has been present since the original implementation, and it
> > affects all devices it supports.
> >
> > This series has been tested with a veml7700 (same gains as veml6030) and
> > a veml6035 with positive results.
> >
> > Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> Whilst we might consider a backport eventually. This is a huge patch
> to do that with. Hence I'll take this the slow way for next merge window.
>
> For now I've applied patches 1 and 2 in the interest of nibbling away
> at what we will need to see again ;)
>
> Jonathan
>
Thanks, Jonathan.
Could you please tell me where you applied them, so I
can rebase onto that branch? I did not find them in linux-next/master,
iio/testing or iio/togreg. Or should they show up in one of those
within the next hours/days?
Best regards,
Javier Carrasco.
prev parent reply other threads:[~2025-01-25 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 17:31 [PATCH v2 0/4] iio: light: fix scale in veml6030 Javier Carrasco
2025-01-19 17:31 ` [PATCH v2 1/4] iio: light: veml6030: extend regmap to support regfields Javier Carrasco
2025-01-19 17:31 ` [PATCH v2 2/4] iio: light: veml6030: extend regmap to support caching Javier Carrasco
2025-01-19 17:32 ` [PATCH v2 3/4] iio: gts-helper: export iio_gts_get_total_gain() Javier Carrasco
2025-01-24 8:12 ` Matti Vaittinen
2025-01-25 20:08 ` Javier Carrasco
2025-01-19 17:32 ` [PATCH v2 4/4] iio: light: veml6030: fix scale to conform to ABI Javier Carrasco
2025-01-24 8:24 ` Matti Vaittinen
2025-01-25 12:33 ` [PATCH v2 0/4] iio: light: fix scale in veml6030 Jonathan Cameron
2025-01-25 20:12 ` Javier Carrasco [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=D7BFFUH97D61.25C1T8JHA8WES@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=gupt21@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@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