Linux Input/HID development
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: dhs@frame.work, "Jiri Kosina" <jikos@kernel.org>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>
Cc: linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Sven Vainküla" <sven@xn--vainkla-r2a.ee>,
	linux@frame.work
Subject: Re: [PATCH] iio: hid-sensor: als: scale each channel individually
Date: Mon, 27 Jul 2026 08:18:47 -0700	[thread overview]
Message-ID: <b6e684365758146193421ac3a36b58d55af77691.camel@linux.intel.com> (raw)
In-Reply-To: <20260723-chromaticity-v1-1-5ef5746ace2a@frame.work>

On Thu, 2026-07-23 at 01:18 +0800, Daniel Schaefer via B4 Relay wrote:
> From: Daniel Schaefer <dhs@frame.work>
> 
> Some sensors have multiple channels (not just brightness but color
> ALS
> sensors) with different scaling factors.
> 
> Tested on Asus ProArt PX13 laptop by Sven.
> 
> Signed-off-by: Daniel Schaefer <dhs@frame.work>
> Link:
> https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/413
> Cc: Sven Vainküla <sven@xn--vainkla-r2a.ee>
> Cc: Jiri Kosina <jikos@kernel.org>
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> Cc: David Lechner <dlechner@baylibre.com>
> Cc: Nuno Sá <nuno.sa@analog.com>
> Cc: Andy Shevchenko <andy@kernel.org>
> Cc: linux-input@vger.kernel.org
> Cc: linux-iio@vger.kernel.org
> Cc: linux@frame.work

Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>

> ---
>  drivers/iio/light/hid-sensor-als.c | 22 ++++++++++++----------
>  1 file changed, 12 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/iio/light/hid-sensor-als.c
> b/drivers/iio/light/hid-sensor-als.c
> index 384572844162..232cb58e0a9f 100644
> --- a/drivers/iio/light/hid-sensor-als.c
> +++ b/drivers/iio/light/hid-sensor-als.c
> @@ -33,9 +33,9 @@ struct als_state {
>  		u32 illum[CHANNEL_SCAN_INDEX_MAX];
>  		aligned_s64 timestamp;
>  	} scan;
> -	int scale_pre_decml;
> -	int scale_post_decml;
> -	int scale_precision;
> +	int scale_pre_decml[CHANNEL_SCAN_INDEX_MAX];
> +	int scale_post_decml[CHANNEL_SCAN_INDEX_MAX];
> +	int scale_precision[CHANNEL_SCAN_INDEX_MAX];
>  	int value_offset;
>  	int num_channels;
>  	s64 timestamp;
> @@ -186,9 +186,11 @@ static int als_read_raw(struct iio_dev
> *indio_dev,
>  		ret_type = IIO_VAL_INT;
>  		break;
>  	case IIO_CHAN_INFO_SCALE:
> -		*val = als_state->scale_pre_decml;
> -		*val2 = als_state->scale_post_decml;
> -		ret_type = als_state->scale_precision;
> +		if (chan->scan_index >= CHANNEL_SCAN_INDEX_MAX)
> +			return -EINVAL;
> +		*val = als_state->scale_pre_decml[chan->scan_index];
> +		*val2 = als_state->scale_post_decml[chan-
> >scan_index];
> +		ret_type = als_state->scale_precision[chan-
> >scan_index];
>  		break;
>  	case IIO_CHAN_INFO_OFFSET:
>  		*val = als_state->value_offset;
> @@ -338,6 +340,10 @@ static int als_parse_report(struct
> platform_device *pdev,
>  		als_adjust_channel_bit_mask(channels, index, st-
> >als[i].size);
>  		++index;
>  
> +		st->scale_precision[i] =
> hid_sensor_format_scale(usage_id,
> +					&st->als[i], &st-
> >scale_pre_decml[i],
> +					&st->scale_post_decml[i]);
> +
>  		dev_dbg(&pdev->dev, "als %x:%x\n", st->als[i].index,
>  			st->als[i].report_id);
>  	}
> @@ -347,10 +353,6 @@ static int als_parse_report(struct
> platform_device *pdev,
>  	if (index)
>  		ret = 0;
>  
> -	st->scale_precision = hid_sensor_format_scale(usage_id,
> -				&st-
> >als[CHANNEL_SCAN_INDEX_INTENSITY],
> -				&st->scale_pre_decml, &st-
> >scale_post_decml);
> -
>  	return ret;
>  }
>  
> 
> ---
> base-commit: 194a48576843858afcd9c00ed4f105ec2b398e6c
> change-id: 20260723-chromaticity-88fec417f00c
> 
> Best regards,

  parent reply	other threads:[~2026-07-27 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 17:18 [PATCH] iio: hid-sensor: als: scale each channel individually Daniel Schaefer via B4 Relay
2026-07-22 17:35 ` sashiko-bot
2026-07-25 23:18 ` Jonathan Cameron
2026-07-27 15:18 ` srinivas pandruvada [this message]
2026-07-27 21:13   ` Jonathan Cameron
2026-07-28  0:38     ` Daniel Schaefer

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=b6e684365758146193421ac3a36b58d55af77691.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=dhs@frame.work \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@frame.work \
    --cc=nuno.sa@analog.com \
    --cc=sven@xn--vainkla-r2a.ee \
    /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