From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: bu27034: Add a read only HWARDWAREGAIN
Date: Sat, 15 Jun 2024 18:50:36 +0100 [thread overview]
Message-ID: <20240615185036.7d1934c2@jic23-huawei> (raw)
In-Reply-To: <5e88c7b7b0389c6c011f15e05e065791f7561cf5.1718013518.git.mazziesaccount@gmail.com>
On Mon, 10 Jun 2024 13:01:40 +0300
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> The ROHM BU27034 light sensor has two data channels for measuring
> different frequencies of light. The result from these channels is
> combined into Lux value while the raw channel values are reported via
> intensity channels.
>
> Both of the intensity channels have adjustable gain setting which
> impacts the scale of the raw channels. Eg, doubling the gain will double
> the values read from the raw channels, which halves the scale value. The
> integration time can also be set for the sensor. This does also have an
> impact to the scale of the intensity channels because increasing the
> integration time will also increase the values reported via the raw
> channels.
>
> Impact of integration time to the scale and the fact that the scale value
> does not start from '1', can make it hard for a human reader to compute the
> gain values based on the scale.
>
> Add read-only HARDWAREGAIN to help debugging.
>
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
Other than the thing the bot found with fallthrough on the switch statement
not being marked LGTM.
> ---
> drivers/iio/light/rohm-bu27034.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/light/rohm-bu27034.c b/drivers/iio/light/rohm-bu27034.c
> index 51acad2cafbd..b299ff2aacce 100644
> --- a/drivers/iio/light/rohm-bu27034.c
> +++ b/drivers/iio/light/rohm-bu27034.c
> @@ -149,7 +149,8 @@ static const struct iio_itime_sel_mul bu27034_itimes[] = {
> .channel = BU27034_CHAN_##_name, \
> .channel2 = IIO_MOD_LIGHT_CLEAR, \
> .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) | \
> - BIT(IIO_CHAN_INFO_SCALE), \
> + BIT(IIO_CHAN_INFO_SCALE) | \
> + BIT(IIO_CHAN_INFO_HARDWAREGAIN), \
> .info_mask_separate_available = BIT(IIO_CHAN_INFO_SCALE), \
> .info_mask_shared_by_all = BIT(IIO_CHAN_INFO_INT_TIME), \
> .info_mask_shared_by_all_available = \
> @@ -992,6 +993,13 @@ static int bu27034_read_raw(struct iio_dev *idev,
>
> return IIO_VAL_INT_PLUS_MICRO;
>
> + case IIO_CHAN_INFO_HARDWAREGAIN:
> + ret = bu27034_get_gain(data, chan->channel, val);
> + if (ret)
> + return ret;
> +
> + return IIO_VAL_INT;
> +
> case IIO_CHAN_INFO_SCALE:
> return bu27034_get_scale(data, chan->channel, val, val2);
>
> @@ -1036,12 +1044,16 @@ static int bu27034_write_raw_get_fmt(struct iio_dev *indio_dev,
> struct iio_chan_spec const *chan,
> long mask)
> {
> + struct bu27034_data *data = iio_priv(indio_dev);
>
> switch (mask) {
> case IIO_CHAN_INFO_SCALE:
> return IIO_VAL_INT_PLUS_NANO;
> case IIO_CHAN_INFO_INT_TIME:
> return IIO_VAL_INT_PLUS_MICRO;
> + case IIO_CHAN_INFO_HARDWAREGAIN:
> + dev_dbg(data->dev,
> + "HARDWAREGAIN is read-only, use scale to set\n");
return -EINVAL here. You could use a fall through marking but it gains
little so I wouldn't bother.
> default:
> return -EINVAL;
> }
next prev parent reply other threads:[~2024-06-15 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 10:00 [PATCH 0/2] ROHM BU27034NUC to ROHM BU27034ANUC Matti Vaittinen
2024-06-10 10:01 ` [PATCH 1/2] bu27034: ROHM BU27034NUC to BU27034ANUC Matti Vaittinen
2024-06-15 17:47 ` Jonathan Cameron
2024-06-17 6:07 ` Matti Vaittinen
2024-06-10 10:01 ` [PATCH 2/2] iio: bu27034: Add a read only HWARDWAREGAIN Matti Vaittinen
2024-06-10 12:55 ` kernel test robot
2024-06-10 13:28 ` kernel test robot
2024-06-15 17:50 ` Jonathan Cameron [this message]
2024-06-17 5:34 ` Matti Vaittinen
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=20240615185036.7d1934c2@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--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