* [PATCH v3 0/4] Add support of color temperature and chromaticity
@ 2024-01-09 18:00 Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically Srinivas Pandruvada
` (3 more replies)
0 siblings, 4 replies; 11+ messages in thread
From: Srinivas Pandruvada @ 2024-01-09 18:00 UTC (permalink / raw)
To: jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel, Srinivas Pandruvada
The original series submitted to 6.7 (before revert) is modified to
solve regression issues on several platforms. There are two changes
introduced before adding support for new features to allow dynamic
addition of channels.
v3:
Addressed comments for v2, details in each patch.
v2:
New change to add channels dynamically
Modified color temperature and chromaticity to skip in case
of failures
Basavaraj Natikar (2):
iio: hid-sensor-als: Add light color temperature support
iio: hid-sensor-als: Add light chromaticity support
Srinivas Pandruvada (2):
iio: hid-sensor-als: Assign channels dynamically
iio: hid-sensor-als: Remove hardcoding of values for enums
drivers/iio/light/hid-sensor-als.c | 130 ++++++++++++++++++++++++-----
include/linux/hid-sensor-ids.h | 4 +
2 files changed, 115 insertions(+), 19 deletions(-)
--
2.43.0
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically
2024-01-09 18:00 [PATCH v3 0/4] Add support of color temperature and chromaticity Srinivas Pandruvada
@ 2024-01-09 18:00 ` Srinivas Pandruvada
2024-01-13 16:03 ` Jonathan Cameron
2024-01-25 5:51 ` Basavaraj Natikar
2024-01-09 18:00 ` [PATCH v3 2/4] iio: hid-sensor-als: Remove hardcoding of values for enums Srinivas Pandruvada
` (2 subsequent siblings)
3 siblings, 2 replies; 11+ messages in thread
From: Srinivas Pandruvada @ 2024-01-09 18:00 UTC (permalink / raw)
To: jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel, Srinivas Pandruvada
Instead of assuming that every channel defined statically by
als_channels[] is present, assign dynamically based on presence of the
respective usage id in the descriptor. This will allow to register ALS
with limited channel support. Append the timestamp as the last channel.
When not all usage ids are present, the scan index is adjusted to
exclude unsupported channels.
There is no intentional function changes done.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
v3:
Addressed comments from Jonthan:
- Remove channel allocation and move to iio_priv()
- Parse all usage IDs in a single loop and continue
for failure. This way the temperature and chromaticity
will not need any special processing to parse usage ids.
- Don't leave empty channel indexes
v2:
New change
drivers/iio/light/hid-sensor-als.c | 56 +++++++++++++++++++++---------
1 file changed, 39 insertions(+), 17 deletions(-)
diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
index 5cd27f04b45e..72a7c01c97f8 100644
--- a/drivers/iio/light/hid-sensor-als.c
+++ b/drivers/iio/light/hid-sensor-als.c
@@ -25,17 +25,26 @@ struct als_state {
struct hid_sensor_hub_callbacks callbacks;
struct hid_sensor_common common_attributes;
struct hid_sensor_hub_attribute_info als[CHANNEL_SCAN_INDEX_MAX];
+ struct iio_chan_spec channels[CHANNEL_SCAN_INDEX_MAX + 1];
struct {
u32 illum[CHANNEL_SCAN_INDEX_MAX];
+ u32 scan_index[CHANNEL_SCAN_INDEX_MAX];
u64 timestamp __aligned(8);
} scan;
int scale_pre_decml;
int scale_post_decml;
int scale_precision;
int value_offset;
+ int num_channels;
s64 timestamp;
};
+/* The order of usage ids must match scan index starting from CHANNEL_SCAN_INDEX_INTENSITY */
+static const u32 als_usage_ids[] = {
+ HID_USAGE_SENSOR_LIGHT_ILLUM,
+ HID_USAGE_SENSOR_LIGHT_ILLUM,
+};
+
static const u32 als_sensitivity_addresses[] = {
HID_USAGE_SENSOR_DATA_LIGHT,
HID_USAGE_SENSOR_LIGHT_ILLUM,
@@ -216,11 +225,14 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
struct als_state *als_state = iio_priv(indio_dev);
int ret = -EINVAL;
u32 sample_data = *(u32 *)raw_data;
+ int scan_index;
switch (usage_id) {
case HID_USAGE_SENSOR_LIGHT_ILLUM:
- als_state->scan.illum[CHANNEL_SCAN_INDEX_INTENSITY] = sample_data;
- als_state->scan.illum[CHANNEL_SCAN_INDEX_ILLUM] = sample_data;
+ scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_INTENSITY];
+ als_state->scan.illum[scan_index] = sample_data;
+ scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_ILLUM];
+ als_state->scan.illum[scan_index] = sample_data;
ret = 0;
break;
case HID_USAGE_SENSOR_TIME_TIMESTAMP:
@@ -237,27 +249,39 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
/* Parse report which is specific to an usage id*/
static int als_parse_report(struct platform_device *pdev,
struct hid_sensor_hub_device *hsdev,
- struct iio_chan_spec *channels,
unsigned usage_id,
struct als_state *st)
{
- int ret;
+ struct iio_chan_spec *channels;
+ int ret, index = 0;
int i;
+ channels = st->channels;
+
for (i = 0; i <= CHANNEL_SCAN_INDEX_ILLUM; ++i) {
ret = sensor_hub_input_get_attribute_info(hsdev,
HID_INPUT_REPORT,
usage_id,
- HID_USAGE_SENSOR_LIGHT_ILLUM,
+ als_usage_ids[i],
&st->als[i]);
if (ret < 0)
- return ret;
- als_adjust_channel_bit_mask(channels, i, st->als[i].size);
+ continue;
+
+ channels[index] = als_channels[i];
+ st->scan.scan_index[i] = index;
+
+ als_adjust_channel_bit_mask(channels, index, st->als[i].size);
+ ++index;
dev_dbg(&pdev->dev, "als %x:%x\n", st->als[i].index,
st->als[i].report_id);
}
+ st->num_channels = index;
+ /* Return success even if one usage id is present */
+ 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);
@@ -293,15 +317,7 @@ static int hid_als_probe(struct platform_device *pdev)
return ret;
}
- indio_dev->channels = devm_kmemdup(&pdev->dev, als_channels,
- sizeof(als_channels), GFP_KERNEL);
- if (!indio_dev->channels) {
- dev_err(&pdev->dev, "failed to duplicate channels\n");
- return -ENOMEM;
- }
-
ret = als_parse_report(pdev, hsdev,
- (struct iio_chan_spec *)indio_dev->channels,
hsdev->usage,
als_state);
if (ret) {
@@ -309,8 +325,14 @@ static int hid_als_probe(struct platform_device *pdev)
return ret;
}
- indio_dev->num_channels =
- ARRAY_SIZE(als_channels);
+ /* Add timestamp channel */
+ als_state->channels[als_state->num_channels] = als_channels[CHANNEL_SCAN_INDEX_TIMESTAMP];
+ als_state->channels[als_state->num_channels].scan_index = als_state->num_channels;
+
+ /* +1 for adding timestamp channel */
+ indio_dev->num_channels = als_state->num_channels + 1;
+
+ indio_dev->channels = als_state->channels;
indio_dev->info = &als_info;
indio_dev->name = name;
indio_dev->modes = INDIO_DIRECT_MODE;
--
2.43.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 2/4] iio: hid-sensor-als: Remove hardcoding of values for enums
2024-01-09 18:00 [PATCH v3 0/4] Add support of color temperature and chromaticity Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically Srinivas Pandruvada
@ 2024-01-09 18:00 ` Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 3/4] iio: hid-sensor-als: Add light color temperature support Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 4/4] iio: hid-sensor-als: Add light chromaticity support Srinivas Pandruvada
3 siblings, 0 replies; 11+ messages in thread
From: Srinivas Pandruvada @ 2024-01-09 18:00 UTC (permalink / raw)
To: jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel, Srinivas Pandruvada
Remove hardcoding of values for enum CHANNEL_SCAN_INDEX_INTENSITY and
CHANNEL_SCAN_INDEX_ILLUM.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
v3:
New patch. Added as the next patch removed the hardcoding of enum values
when submitted. To remove unrelated changes, created a patch to just
remove hardcoding of values.
drivers/iio/light/hid-sensor-als.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
index 72a7c01c97f8..a7bde6b68102 100644
--- a/drivers/iio/light/hid-sensor-als.c
+++ b/drivers/iio/light/hid-sensor-als.c
@@ -14,8 +14,8 @@
#include "../common/hid-sensors/hid-sensor-trigger.h"
enum {
- CHANNEL_SCAN_INDEX_INTENSITY = 0,
- CHANNEL_SCAN_INDEX_ILLUM = 1,
+ CHANNEL_SCAN_INDEX_INTENSITY,
+ CHANNEL_SCAN_INDEX_ILLUM,
CHANNEL_SCAN_INDEX_MAX
};
--
2.43.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 3/4] iio: hid-sensor-als: Add light color temperature support
2024-01-09 18:00 [PATCH v3 0/4] Add support of color temperature and chromaticity Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 2/4] iio: hid-sensor-als: Remove hardcoding of values for enums Srinivas Pandruvada
@ 2024-01-09 18:00 ` Srinivas Pandruvada
2024-01-25 5:55 ` Basavaraj Natikar
2024-01-09 18:00 ` [PATCH v3 4/4] iio: hid-sensor-als: Add light chromaticity support Srinivas Pandruvada
3 siblings, 1 reply; 11+ messages in thread
From: Srinivas Pandruvada @ 2024-01-09 18:00 UTC (permalink / raw)
To: jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel, Srinivas Pandruvada
From: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
On some platforms, ambient color sensors also support light color
temperature. Add support of light color temperature.
Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
I don't have a system to test this patch.
Hi Basavraj,
Please test.
v3:
Simplilified as no special processing is required in als_parse_report()
v2:
Original patch from Basavaraj Natikar <Basavaraj.Natikar@amd.com> is
modified to prevent failure when the new usage id is not found in the
descriptor.
drivers/iio/light/hid-sensor-als.c | 22 ++++++++++++++++++++++
include/linux/hid-sensor-ids.h | 1 +
2 files changed, 23 insertions(+)
diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
index a7bde6b68102..0d54eb59e47d 100644
--- a/drivers/iio/light/hid-sensor-als.c
+++ b/drivers/iio/light/hid-sensor-als.c
@@ -16,6 +16,7 @@
enum {
CHANNEL_SCAN_INDEX_INTENSITY,
CHANNEL_SCAN_INDEX_ILLUM,
+ CHANNEL_SCAN_INDEX_COLOR_TEMP,
CHANNEL_SCAN_INDEX_MAX
};
@@ -43,6 +44,7 @@ struct als_state {
static const u32 als_usage_ids[] = {
HID_USAGE_SENSOR_LIGHT_ILLUM,
HID_USAGE_SENSOR_LIGHT_ILLUM,
+ HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE,
};
static const u32 als_sensitivity_addresses[] = {
@@ -74,6 +76,16 @@ static const struct iio_chan_spec als_channels[] = {
BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
.scan_index = CHANNEL_SCAN_INDEX_ILLUM,
},
+ {
+ .type = IIO_COLORTEMP,
+ .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
+ .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_OFFSET) |
+ BIT(IIO_CHAN_INFO_SCALE) |
+ BIT(IIO_CHAN_INFO_SAMP_FREQ) |
+ BIT(IIO_CHAN_INFO_HYSTERESIS) |
+ BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
+ .scan_index = CHANNEL_SCAN_INDEX_COLOR_TEMP,
+ },
IIO_CHAN_SOFT_TIMESTAMP(CHANNEL_SCAN_INDEX_TIMESTAMP)
};
@@ -112,6 +124,11 @@ static int als_read_raw(struct iio_dev *indio_dev,
min = als_state->als[chan->scan_index].logical_minimum;
address = HID_USAGE_SENSOR_LIGHT_ILLUM;
break;
+ case CHANNEL_SCAN_INDEX_COLOR_TEMP:
+ report_id = als_state->als[chan->scan_index].report_id;
+ min = als_state->als[chan->scan_index].logical_minimum;
+ address = HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE;
+ break;
default:
report_id = -1;
break;
@@ -235,6 +252,11 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
als_state->scan.illum[scan_index] = sample_data;
ret = 0;
break;
+ case HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE:
+ scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_COLOR_TEMP];
+ als_state->scan.illum[scan_index] = sample_data;
+ ret = 0;
+ break;
case HID_USAGE_SENSOR_TIME_TIMESTAMP:
als_state->timestamp = hid_sensor_convert_timestamp(&als_state->common_attributes,
*(s64 *)raw_data);
diff --git a/include/linux/hid-sensor-ids.h b/include/linux/hid-sensor-ids.h
index 13b1e65fbdcc..8af4fb3e0254 100644
--- a/include/linux/hid-sensor-ids.h
+++ b/include/linux/hid-sensor-ids.h
@@ -21,6 +21,7 @@
#define HID_USAGE_SENSOR_ALS 0x200041
#define HID_USAGE_SENSOR_DATA_LIGHT 0x2004d0
#define HID_USAGE_SENSOR_LIGHT_ILLUM 0x2004d1
+#define HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE 0x2004d2
/* PROX (200011) */
#define HID_USAGE_SENSOR_PROX 0x200011
--
2.43.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v3 4/4] iio: hid-sensor-als: Add light chromaticity support
2024-01-09 18:00 [PATCH v3 0/4] Add support of color temperature and chromaticity Srinivas Pandruvada
` (2 preceding siblings ...)
2024-01-09 18:00 ` [PATCH v3 3/4] iio: hid-sensor-als: Add light color temperature support Srinivas Pandruvada
@ 2024-01-09 18:00 ` Srinivas Pandruvada
2024-01-25 5:56 ` Basavaraj Natikar
3 siblings, 1 reply; 11+ messages in thread
From: Srinivas Pandruvada @ 2024-01-09 18:00 UTC (permalink / raw)
To: jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel, Srinivas Pandruvada
From: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
On some platforms, ambient color sensors also support the x and y light
colors, which represent the coordinates on the CIE 1931 chromaticity
diagram. Add light chromaticity x and y.
Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
I don't have a system to test this patch.
Hi Basavraj,
Please test.
v3:
Simplilified as no special processing is required in als_parse_report()
v2:
Original patch from Basavaraj Natikar <Basavaraj.Natikar@amd.com> is
modified to prevent failure when the new usage id is not found in the
descriptor.
drivers/iio/light/hid-sensor-als.c | 48 ++++++++++++++++++++++++++++++
include/linux/hid-sensor-ids.h | 3 ++
2 files changed, 51 insertions(+)
diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
index 0d54eb59e47d..9c31febc84b8 100644
--- a/drivers/iio/light/hid-sensor-als.c
+++ b/drivers/iio/light/hid-sensor-als.c
@@ -17,6 +17,8 @@ enum {
CHANNEL_SCAN_INDEX_INTENSITY,
CHANNEL_SCAN_INDEX_ILLUM,
CHANNEL_SCAN_INDEX_COLOR_TEMP,
+ CHANNEL_SCAN_INDEX_CHROMATICITY_X,
+ CHANNEL_SCAN_INDEX_CHROMATICITY_Y,
CHANNEL_SCAN_INDEX_MAX
};
@@ -45,6 +47,8 @@ static const u32 als_usage_ids[] = {
HID_USAGE_SENSOR_LIGHT_ILLUM,
HID_USAGE_SENSOR_LIGHT_ILLUM,
HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE,
+ HID_USAGE_SENSOR_LIGHT_CHROMATICITY_X,
+ HID_USAGE_SENSOR_LIGHT_CHROMATICITY_Y,
};
static const u32 als_sensitivity_addresses[] = {
@@ -86,6 +90,30 @@ static const struct iio_chan_spec als_channels[] = {
BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
.scan_index = CHANNEL_SCAN_INDEX_COLOR_TEMP,
},
+ {
+ .type = IIO_CHROMATICITY,
+ .modified = 1,
+ .channel2 = IIO_MOD_X,
+ .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
+ .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_OFFSET) |
+ BIT(IIO_CHAN_INFO_SCALE) |
+ BIT(IIO_CHAN_INFO_SAMP_FREQ) |
+ BIT(IIO_CHAN_INFO_HYSTERESIS) |
+ BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
+ .scan_index = CHANNEL_SCAN_INDEX_CHROMATICITY_X,
+ },
+ {
+ .type = IIO_CHROMATICITY,
+ .modified = 1,
+ .channel2 = IIO_MOD_Y,
+ .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
+ .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_OFFSET) |
+ BIT(IIO_CHAN_INFO_SCALE) |
+ BIT(IIO_CHAN_INFO_SAMP_FREQ) |
+ BIT(IIO_CHAN_INFO_HYSTERESIS) |
+ BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
+ .scan_index = CHANNEL_SCAN_INDEX_CHROMATICITY_Y,
+ },
IIO_CHAN_SOFT_TIMESTAMP(CHANNEL_SCAN_INDEX_TIMESTAMP)
};
@@ -129,6 +157,16 @@ static int als_read_raw(struct iio_dev *indio_dev,
min = als_state->als[chan->scan_index].logical_minimum;
address = HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE;
break;
+ case CHANNEL_SCAN_INDEX_CHROMATICITY_X:
+ report_id = als_state->als[chan->scan_index].report_id;
+ min = als_state->als[chan->scan_index].logical_minimum;
+ address = HID_USAGE_SENSOR_LIGHT_CHROMATICITY_X;
+ break;
+ case CHANNEL_SCAN_INDEX_CHROMATICITY_Y:
+ report_id = als_state->als[chan->scan_index].report_id;
+ min = als_state->als[chan->scan_index].logical_minimum;
+ address = HID_USAGE_SENSOR_LIGHT_CHROMATICITY_Y;
+ break;
default:
report_id = -1;
break;
@@ -257,6 +295,16 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
als_state->scan.illum[scan_index] = sample_data;
ret = 0;
break;
+ case HID_USAGE_SENSOR_LIGHT_CHROMATICITY_X:
+ scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_CHROMATICITY_X];
+ als_state->scan.illum[scan_index] = sample_data;
+ ret = 0;
+ break;
+ case HID_USAGE_SENSOR_LIGHT_CHROMATICITY_Y:
+ scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_CHROMATICITY_Y];
+ als_state->scan.illum[scan_index] = sample_data;
+ ret = 0;
+ break;
case HID_USAGE_SENSOR_TIME_TIMESTAMP:
als_state->timestamp = hid_sensor_convert_timestamp(&als_state->common_attributes,
*(s64 *)raw_data);
diff --git a/include/linux/hid-sensor-ids.h b/include/linux/hid-sensor-ids.h
index 8af4fb3e0254..6730ee900ee1 100644
--- a/include/linux/hid-sensor-ids.h
+++ b/include/linux/hid-sensor-ids.h
@@ -22,6 +22,9 @@
#define HID_USAGE_SENSOR_DATA_LIGHT 0x2004d0
#define HID_USAGE_SENSOR_LIGHT_ILLUM 0x2004d1
#define HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE 0x2004d2
+#define HID_USAGE_SENSOR_LIGHT_CHROMATICITY 0x2004d3
+#define HID_USAGE_SENSOR_LIGHT_CHROMATICITY_X 0x2004d4
+#define HID_USAGE_SENSOR_LIGHT_CHROMATICITY_Y 0x2004d5
/* PROX (200011) */
#define HID_USAGE_SENSOR_PROX 0x200011
--
2.43.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically
2024-01-09 18:00 ` [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically Srinivas Pandruvada
@ 2024-01-13 16:03 ` Jonathan Cameron
2024-02-04 13:06 ` Srinivas Pandruvada
2024-01-25 5:51 ` Basavaraj Natikar
1 sibling, 1 reply; 11+ messages in thread
From: Jonathan Cameron @ 2024-01-13 16:03 UTC (permalink / raw)
To: Srinivas Pandruvada
Cc: jikos, lars, Basavaraj.Natikar, linux-input, linux-iio,
linux-kernel
On Tue, 9 Jan 2024 10:00:04 -0800
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
> Instead of assuming that every channel defined statically by
> als_channels[] is present, assign dynamically based on presence of the
> respective usage id in the descriptor. This will allow to register ALS
> with limited channel support. Append the timestamp as the last channel.
>
> When not all usage ids are present, the scan index is adjusted to
> exclude unsupported channels.
>
> There is no intentional function changes done.
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> v3:
> Addressed comments from Jonthan:
> - Remove channel allocation and move to iio_priv()
> - Parse all usage IDs in a single loop and continue
> for failure. This way the temperature and chromaticity
> will not need any special processing to parse usage ids.
> - Don't leave empty channel indexes
There isn't really a problem if you did want to leave them.
There are a number of other devices that do leave gaps and userspace
code shouldn't mind that. I don't mind them being more tightly packed
though so this is also fine.
I was just looking at the driver and noticed one other oddity.
In als_capture_sample, it always returns -EINVAL if the timestamp channel
is being queried.
>
> v2:
> New change
>
> drivers/iio/light/hid-sensor-als.c | 56 +++++++++++++++++++++---------
> 1 file changed, 39 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
> index 5cd27f04b45e..72a7c01c97f8 100644
> --- a/drivers/iio/light/hid-sensor-als.c
> +++ b/drivers/iio/light/hid-sensor-als.c
> @@ -25,17 +25,26 @@ struct als_state {
> struct hid_sensor_hub_callbacks callbacks;
> struct hid_sensor_common common_attributes;
> struct hid_sensor_hub_attribute_info als[CHANNEL_SCAN_INDEX_MAX];
> + struct iio_chan_spec channels[CHANNEL_SCAN_INDEX_MAX + 1];
> struct {
> u32 illum[CHANNEL_SCAN_INDEX_MAX];
> + u32 scan_index[CHANNEL_SCAN_INDEX_MAX];
This looks unlikely to end up right with a varying number of channels.
I'm assuming the device always captures all available channels.
As such, if there are 2 channels the timestamp will end up at byte 8 onwards.
If there are 3 channels, byte 16 onwards etc.
Usually when we have a floating timestamp like this we just rely on expanding
the channel array to leave space and force the alignment of that to be suitable
for taking a timestamp.
I'm a bit confused not to see available_scan_mask being set though.
If userspace previously requested illumination only would the data
have ended up in the right location (offset 0?)
If you set available_scan_masks to specify all channels then the
IIO core will move things around for you. If it's not provided then
it is up to the driver to figure out where to put the data.
Otherwise the patch looks fine to me.
Jonathan
> u64 timestamp __aligned(8);
> } scan;
> int scale_pre_decml;
> int scale_post_decml;
> int scale_precision;
> int value_offset;
> + int num_channels;
> s64 timestamp;
> };
>
> +/* The order of usage ids must match scan index starting from CHANNEL_SCAN_INDEX_INTENSITY */
> +static const u32 als_usage_ids[] = {
> + HID_USAGE_SENSOR_LIGHT_ILLUM,
> + HID_USAGE_SENSOR_LIGHT_ILLUM,
> +};
> +
> static const u32 als_sensitivity_addresses[] = {
> HID_USAGE_SENSOR_DATA_LIGHT,
> HID_USAGE_SENSOR_LIGHT_ILLUM,
> @@ -216,11 +225,14 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
> struct als_state *als_state = iio_priv(indio_dev);
> int ret = -EINVAL;
> u32 sample_data = *(u32 *)raw_data;
> + int scan_index;
>
> switch (usage_id) {
> case HID_USAGE_SENSOR_LIGHT_ILLUM:
> - als_state->scan.illum[CHANNEL_SCAN_INDEX_INTENSITY] = sample_data;
> - als_state->scan.illum[CHANNEL_SCAN_INDEX_ILLUM] = sample_data;
> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_INTENSITY];
> + als_state->scan.illum[scan_index] = sample_data;
> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_ILLUM];
> + als_state->scan.illum[scan_index] = sample_data;
> ret = 0;
> break;
> case HID_USAGE_SENSOR_TIME_TIMESTAMP:
> @@ -237,27 +249,39 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
> /* Parse report which is specific to an usage id*/
> static int als_parse_report(struct platform_device *pdev,
> struct hid_sensor_hub_device *hsdev,
> - struct iio_chan_spec *channels,
> unsigned usage_id,
> struct als_state *st)
> {
> - int ret;
> + struct iio_chan_spec *channels;
> + int ret, index = 0;
> int i;
>
> + channels = st->channels;
> +
> for (i = 0; i <= CHANNEL_SCAN_INDEX_ILLUM; ++i) {
> ret = sensor_hub_input_get_attribute_info(hsdev,
> HID_INPUT_REPORT,
> usage_id,
> - HID_USAGE_SENSOR_LIGHT_ILLUM,
> + als_usage_ids[i],
> &st->als[i]);
> if (ret < 0)
> - return ret;
> - als_adjust_channel_bit_mask(channels, i, st->als[i].size);
> + continue;
> +
> + channels[index] = als_channels[i];
> + st->scan.scan_index[i] = index;
> +
> + als_adjust_channel_bit_mask(channels, index, st->als[i].size);
> + ++index;
>
> dev_dbg(&pdev->dev, "als %x:%x\n", st->als[i].index,
> st->als[i].report_id);
> }
>
> + st->num_channels = index;
> + /* Return success even if one usage id is present */
> + 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);
> @@ -293,15 +317,7 @@ static int hid_als_probe(struct platform_device *pdev)
> return ret;
> }
>
> - indio_dev->channels = devm_kmemdup(&pdev->dev, als_channels,
> - sizeof(als_channels), GFP_KERNEL);
> - if (!indio_dev->channels) {
> - dev_err(&pdev->dev, "failed to duplicate channels\n");
> - return -ENOMEM;
> - }
> -
> ret = als_parse_report(pdev, hsdev,
> - (struct iio_chan_spec *)indio_dev->channels,
> hsdev->usage,
> als_state);
> if (ret) {
> @@ -309,8 +325,14 @@ static int hid_als_probe(struct platform_device *pdev)
> return ret;
> }
>
> - indio_dev->num_channels =
> - ARRAY_SIZE(als_channels);
> + /* Add timestamp channel */
> + als_state->channels[als_state->num_channels] = als_channels[CHANNEL_SCAN_INDEX_TIMESTAMP];
> + als_state->channels[als_state->num_channels].scan_index = als_state->num_channels;
> +
> + /* +1 for adding timestamp channel */
> + indio_dev->num_channels = als_state->num_channels + 1;
> +
> + indio_dev->channels = als_state->channels;
> indio_dev->info = &als_info;
> indio_dev->name = name;
> indio_dev->modes = INDIO_DIRECT_MODE;
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically
2024-01-09 18:00 ` [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically Srinivas Pandruvada
2024-01-13 16:03 ` Jonathan Cameron
@ 2024-01-25 5:51 ` Basavaraj Natikar
2024-01-25 6:01 ` Srinivas Pandruvada
1 sibling, 1 reply; 11+ messages in thread
From: Basavaraj Natikar @ 2024-01-25 5:51 UTC (permalink / raw)
To: Srinivas Pandruvada, jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel
Hi Srinivas,
On 1/9/2024 11:30 PM, Srinivas Pandruvada wrote:
> Instead of assuming that every channel defined statically by
> als_channels[] is present, assign dynamically based on presence of the
> respective usage id in the descriptor. This will allow to register ALS
> with limited channel support. Append the timestamp as the last channel.
>
> When not all usage ids are present, the scan index is adjusted to
> exclude unsupported channels.
>
> There is no intentional function changes done.
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> v3:
> Addressed comments from Jonthan:
> - Remove channel allocation and move to iio_priv()
> - Parse all usage IDs in a single loop and continue
> for failure. This way the temperature and chromaticity
> will not need any special processing to parse usage ids.
> - Don't leave empty channel indexes
>
> v2:
> New change
>
> drivers/iio/light/hid-sensor-als.c | 56 +++++++++++++++++++++---------
> 1 file changed, 39 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
> index 5cd27f04b45e..72a7c01c97f8 100644
> --- a/drivers/iio/light/hid-sensor-als.c
> +++ b/drivers/iio/light/hid-sensor-als.c
> @@ -25,17 +25,26 @@ struct als_state {
> struct hid_sensor_hub_callbacks callbacks;
> struct hid_sensor_common common_attributes;
> struct hid_sensor_hub_attribute_info als[CHANNEL_SCAN_INDEX_MAX];
> + struct iio_chan_spec channels[CHANNEL_SCAN_INDEX_MAX + 1];
> struct {
> u32 illum[CHANNEL_SCAN_INDEX_MAX];
> + u32 scan_index[CHANNEL_SCAN_INDEX_MAX];
> u64 timestamp __aligned(8);
> } scan;
> int scale_pre_decml;
> int scale_post_decml;
> int scale_precision;
> int value_offset;
> + int num_channels;
> s64 timestamp;
> };
>
> +/* The order of usage ids must match scan index starting from CHANNEL_SCAN_INDEX_INTENSITY */
> +static const u32 als_usage_ids[] = {
> + HID_USAGE_SENSOR_LIGHT_ILLUM,
> + HID_USAGE_SENSOR_LIGHT_ILLUM,
> +};
> +
> static const u32 als_sensitivity_addresses[] = {
> HID_USAGE_SENSOR_DATA_LIGHT,
> HID_USAGE_SENSOR_LIGHT_ILLUM,
> @@ -216,11 +225,14 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
> struct als_state *als_state = iio_priv(indio_dev);
> int ret = -EINVAL;
> u32 sample_data = *(u32 *)raw_data;
> + int scan_index;
>
> switch (usage_id) {
> case HID_USAGE_SENSOR_LIGHT_ILLUM:
> - als_state->scan.illum[CHANNEL_SCAN_INDEX_INTENSITY] = sample_data;
> - als_state->scan.illum[CHANNEL_SCAN_INDEX_ILLUM] = sample_data;
> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_INTENSITY];
> + als_state->scan.illum[scan_index] = sample_data;
> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_ILLUM];
> + als_state->scan.illum[scan_index] = sample_data;
Could you please use original above change which works fine for some reason if
we use this change als_state->scan.scan_index we are getting garbage value.
> ret = 0;
> break;
> case HID_USAGE_SENSOR_TIME_TIMESTAMP:
> @@ -237,27 +249,39 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
> /* Parse report which is specific to an usage id*/
> static int als_parse_report(struct platform_device *pdev,
> struct hid_sensor_hub_device *hsdev,
> - struct iio_chan_spec *channels,
> unsigned usage_id,
> struct als_state *st)
> {
> - int ret;
> + struct iio_chan_spec *channels;
> + int ret, index = 0;
> int i;
>
> + channels = st->channels;
> +
> for (i = 0; i <= CHANNEL_SCAN_INDEX_ILLUM; ++i) {
Could you please change CHANNEL_SCAN_INDEX_ILLUM to CHANNEL_SCAN_INDEX_MAX
which helps remaining 2 patches in the series.
> ret = sensor_hub_input_get_attribute_info(hsdev,
> HID_INPUT_REPORT,
> usage_id,
> - HID_USAGE_SENSOR_LIGHT_ILLUM,
> + als_usage_ids[i],
> &st->als[i]);
> if (ret < 0)
> - return ret;
> - als_adjust_channel_bit_mask(channels, i, st->als[i].size);
> + continue;
> +
> + channels[index] = als_channels[i];
> + st->scan.scan_index[i] = index;
> +
> + als_adjust_channel_bit_mask(channels, index, st->als[i].size);
> + ++index;
>
> dev_dbg(&pdev->dev, "als %x:%x\n", st->als[i].index,
> st->als[i].report_id);
> }
>
> + st->num_channels = index;
> + /* Return success even if one usage id is present */
> + 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);
> @@ -293,15 +317,7 @@ static int hid_als_probe(struct platform_device *pdev)
> return ret;
> }
>
> - indio_dev->channels = devm_kmemdup(&pdev->dev, als_channels,
> - sizeof(als_channels), GFP_KERNEL);
> - if (!indio_dev->channels) {
> - dev_err(&pdev->dev, "failed to duplicate channels\n");
> - return -ENOMEM;
> - }
> -
> ret = als_parse_report(pdev, hsdev,
> - (struct iio_chan_spec *)indio_dev->channels,
> hsdev->usage,
> als_state);
> if (ret) {
> @@ -309,8 +325,14 @@ static int hid_als_probe(struct platform_device *pdev)
> return ret;
> }
>
> - indio_dev->num_channels =
> - ARRAY_SIZE(als_channels);
> + /* Add timestamp channel */
> + als_state->channels[als_state->num_channels] = als_channels[CHANNEL_SCAN_INDEX_TIMESTAMP];
> + als_state->channels[als_state->num_channels].scan_index = als_state->num_channels;
> +
> + /* +1 for adding timestamp channel */
> + indio_dev->num_channels = als_state->num_channels + 1;
> +
> + indio_dev->channels = als_state->channels;
> indio_dev->info = &als_info;
> indio_dev->name = name;
> indio_dev->modes = INDIO_DIRECT_MODE;
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3 3/4] iio: hid-sensor-als: Add light color temperature support
2024-01-09 18:00 ` [PATCH v3 3/4] iio: hid-sensor-als: Add light color temperature support Srinivas Pandruvada
@ 2024-01-25 5:55 ` Basavaraj Natikar
0 siblings, 0 replies; 11+ messages in thread
From: Basavaraj Natikar @ 2024-01-25 5:55 UTC (permalink / raw)
To: Srinivas Pandruvada, jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel
Hi Srinivas,
On 1/9/2024 11:30 PM, Srinivas Pandruvada wrote:
> From: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
>
> On some platforms, ambient color sensors also support light color
> temperature. Add support of light color temperature.
>
> Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
>
> I don't have a system to test this patch.
> Hi Basavraj,
> Please test.
After fixing both comments in patch 1 all works fine.
Thanks,
--
Basavaraj
>
> v3:
> Simplilified as no special processing is required in als_parse_report()
> v2:
> Original patch from Basavaraj Natikar <Basavaraj.Natikar@amd.com> is
> modified to prevent failure when the new usage id is not found in the
> descriptor.
>
> drivers/iio/light/hid-sensor-als.c | 22 ++++++++++++++++++++++
> include/linux/hid-sensor-ids.h | 1 +
> 2 files changed, 23 insertions(+)
>
> diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
> index a7bde6b68102..0d54eb59e47d 100644
> --- a/drivers/iio/light/hid-sensor-als.c
> +++ b/drivers/iio/light/hid-sensor-als.c
> @@ -16,6 +16,7 @@
> enum {
> CHANNEL_SCAN_INDEX_INTENSITY,
> CHANNEL_SCAN_INDEX_ILLUM,
> + CHANNEL_SCAN_INDEX_COLOR_TEMP,
> CHANNEL_SCAN_INDEX_MAX
> };
>
> @@ -43,6 +44,7 @@ struct als_state {
> static const u32 als_usage_ids[] = {
> HID_USAGE_SENSOR_LIGHT_ILLUM,
> HID_USAGE_SENSOR_LIGHT_ILLUM,
> + HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE,
> };
>
> static const u32 als_sensitivity_addresses[] = {
> @@ -74,6 +76,16 @@ static const struct iio_chan_spec als_channels[] = {
> BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
> .scan_index = CHANNEL_SCAN_INDEX_ILLUM,
> },
> + {
> + .type = IIO_COLORTEMP,
> + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
> + .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_OFFSET) |
> + BIT(IIO_CHAN_INFO_SCALE) |
> + BIT(IIO_CHAN_INFO_SAMP_FREQ) |
> + BIT(IIO_CHAN_INFO_HYSTERESIS) |
> + BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
> + .scan_index = CHANNEL_SCAN_INDEX_COLOR_TEMP,
> + },
> IIO_CHAN_SOFT_TIMESTAMP(CHANNEL_SCAN_INDEX_TIMESTAMP)
> };
>
> @@ -112,6 +124,11 @@ static int als_read_raw(struct iio_dev *indio_dev,
> min = als_state->als[chan->scan_index].logical_minimum;
> address = HID_USAGE_SENSOR_LIGHT_ILLUM;
> break;
> + case CHANNEL_SCAN_INDEX_COLOR_TEMP:
> + report_id = als_state->als[chan->scan_index].report_id;
> + min = als_state->als[chan->scan_index].logical_minimum;
> + address = HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE;
> + break;
> default:
> report_id = -1;
> break;
> @@ -235,6 +252,11 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
> als_state->scan.illum[scan_index] = sample_data;
> ret = 0;
> break;
> + case HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE:
> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_COLOR_TEMP];
> + als_state->scan.illum[scan_index] = sample_data;
> + ret = 0;
> + break;
> case HID_USAGE_SENSOR_TIME_TIMESTAMP:
> als_state->timestamp = hid_sensor_convert_timestamp(&als_state->common_attributes,
> *(s64 *)raw_data);
> diff --git a/include/linux/hid-sensor-ids.h b/include/linux/hid-sensor-ids.h
> index 13b1e65fbdcc..8af4fb3e0254 100644
> --- a/include/linux/hid-sensor-ids.h
> +++ b/include/linux/hid-sensor-ids.h
> @@ -21,6 +21,7 @@
> #define HID_USAGE_SENSOR_ALS 0x200041
> #define HID_USAGE_SENSOR_DATA_LIGHT 0x2004d0
> #define HID_USAGE_SENSOR_LIGHT_ILLUM 0x2004d1
> +#define HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE 0x2004d2
>
> /* PROX (200011) */
> #define HID_USAGE_SENSOR_PROX 0x200011
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3 4/4] iio: hid-sensor-als: Add light chromaticity support
2024-01-09 18:00 ` [PATCH v3 4/4] iio: hid-sensor-als: Add light chromaticity support Srinivas Pandruvada
@ 2024-01-25 5:56 ` Basavaraj Natikar
0 siblings, 0 replies; 11+ messages in thread
From: Basavaraj Natikar @ 2024-01-25 5:56 UTC (permalink / raw)
To: Srinivas Pandruvada, jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel
Hi Srinivas,
On 1/9/2024 11:30 PM, Srinivas Pandruvada wrote:
> From: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
>
> On some platforms, ambient color sensors also support the x and y light
> colors, which represent the coordinates on the CIE 1931 chromaticity
> diagram. Add light chromaticity x and y.
>
> Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> I don't have a system to test this patch.
> Hi Basavraj,
> Please test.
After fixing both comments in patch 1 all works fine.
Thanks,
--
Basavaraj
>
> v3:
> Simplilified as no special processing is required in als_parse_report()
>
> v2:
> Original patch from Basavaraj Natikar <Basavaraj.Natikar@amd.com> is
> modified to prevent failure when the new usage id is not found in the
> descriptor.
>
> drivers/iio/light/hid-sensor-als.c | 48 ++++++++++++++++++++++++++++++
> include/linux/hid-sensor-ids.h | 3 ++
> 2 files changed, 51 insertions(+)
>
> diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
> index 0d54eb59e47d..9c31febc84b8 100644
> --- a/drivers/iio/light/hid-sensor-als.c
> +++ b/drivers/iio/light/hid-sensor-als.c
> @@ -17,6 +17,8 @@ enum {
> CHANNEL_SCAN_INDEX_INTENSITY,
> CHANNEL_SCAN_INDEX_ILLUM,
> CHANNEL_SCAN_INDEX_COLOR_TEMP,
> + CHANNEL_SCAN_INDEX_CHROMATICITY_X,
> + CHANNEL_SCAN_INDEX_CHROMATICITY_Y,
> CHANNEL_SCAN_INDEX_MAX
> };
>
> @@ -45,6 +47,8 @@ static const u32 als_usage_ids[] = {
> HID_USAGE_SENSOR_LIGHT_ILLUM,
> HID_USAGE_SENSOR_LIGHT_ILLUM,
> HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE,
> + HID_USAGE_SENSOR_LIGHT_CHROMATICITY_X,
> + HID_USAGE_SENSOR_LIGHT_CHROMATICITY_Y,
> };
>
> static const u32 als_sensitivity_addresses[] = {
> @@ -86,6 +90,30 @@ static const struct iio_chan_spec als_channels[] = {
> BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
> .scan_index = CHANNEL_SCAN_INDEX_COLOR_TEMP,
> },
> + {
> + .type = IIO_CHROMATICITY,
> + .modified = 1,
> + .channel2 = IIO_MOD_X,
> + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
> + .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_OFFSET) |
> + BIT(IIO_CHAN_INFO_SCALE) |
> + BIT(IIO_CHAN_INFO_SAMP_FREQ) |
> + BIT(IIO_CHAN_INFO_HYSTERESIS) |
> + BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
> + .scan_index = CHANNEL_SCAN_INDEX_CHROMATICITY_X,
> + },
> + {
> + .type = IIO_CHROMATICITY,
> + .modified = 1,
> + .channel2 = IIO_MOD_Y,
> + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
> + .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_OFFSET) |
> + BIT(IIO_CHAN_INFO_SCALE) |
> + BIT(IIO_CHAN_INFO_SAMP_FREQ) |
> + BIT(IIO_CHAN_INFO_HYSTERESIS) |
> + BIT(IIO_CHAN_INFO_HYSTERESIS_RELATIVE),
> + .scan_index = CHANNEL_SCAN_INDEX_CHROMATICITY_Y,
> + },
> IIO_CHAN_SOFT_TIMESTAMP(CHANNEL_SCAN_INDEX_TIMESTAMP)
> };
>
> @@ -129,6 +157,16 @@ static int als_read_raw(struct iio_dev *indio_dev,
> min = als_state->als[chan->scan_index].logical_minimum;
> address = HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE;
> break;
> + case CHANNEL_SCAN_INDEX_CHROMATICITY_X:
> + report_id = als_state->als[chan->scan_index].report_id;
> + min = als_state->als[chan->scan_index].logical_minimum;
> + address = HID_USAGE_SENSOR_LIGHT_CHROMATICITY_X;
> + break;
> + case CHANNEL_SCAN_INDEX_CHROMATICITY_Y:
> + report_id = als_state->als[chan->scan_index].report_id;
> + min = als_state->als[chan->scan_index].logical_minimum;
> + address = HID_USAGE_SENSOR_LIGHT_CHROMATICITY_Y;
> + break;
> default:
> report_id = -1;
> break;
> @@ -257,6 +295,16 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
> als_state->scan.illum[scan_index] = sample_data;
> ret = 0;
> break;
> + case HID_USAGE_SENSOR_LIGHT_CHROMATICITY_X:
> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_CHROMATICITY_X];
> + als_state->scan.illum[scan_index] = sample_data;
> + ret = 0;
> + break;
> + case HID_USAGE_SENSOR_LIGHT_CHROMATICITY_Y:
> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_CHROMATICITY_Y];
> + als_state->scan.illum[scan_index] = sample_data;
> + ret = 0;
> + break;
> case HID_USAGE_SENSOR_TIME_TIMESTAMP:
> als_state->timestamp = hid_sensor_convert_timestamp(&als_state->common_attributes,
> *(s64 *)raw_data);
> diff --git a/include/linux/hid-sensor-ids.h b/include/linux/hid-sensor-ids.h
> index 8af4fb3e0254..6730ee900ee1 100644
> --- a/include/linux/hid-sensor-ids.h
> +++ b/include/linux/hid-sensor-ids.h
> @@ -22,6 +22,9 @@
> #define HID_USAGE_SENSOR_DATA_LIGHT 0x2004d0
> #define HID_USAGE_SENSOR_LIGHT_ILLUM 0x2004d1
> #define HID_USAGE_SENSOR_LIGHT_COLOR_TEMPERATURE 0x2004d2
> +#define HID_USAGE_SENSOR_LIGHT_CHROMATICITY 0x2004d3
> +#define HID_USAGE_SENSOR_LIGHT_CHROMATICITY_X 0x2004d4
> +#define HID_USAGE_SENSOR_LIGHT_CHROMATICITY_Y 0x2004d5
>
> /* PROX (200011) */
> #define HID_USAGE_SENSOR_PROX 0x200011
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically
2024-01-25 5:51 ` Basavaraj Natikar
@ 2024-01-25 6:01 ` Srinivas Pandruvada
0 siblings, 0 replies; 11+ messages in thread
From: Srinivas Pandruvada @ 2024-01-25 6:01 UTC (permalink / raw)
To: Basavaraj Natikar, jikos, jic23, lars, Basavaraj.Natikar
Cc: linux-input, linux-iio, linux-kernel
Hi Basavraj,
On 1/24/24 21:51, Basavaraj Natikar wrote:
> Hi Srinivas,
>
>
> On 1/9/2024 11:30 PM, Srinivas Pandruvada wrote:
>> Instead of assuming that every channel defined statically by
>> als_channels[] is present, assign dynamically based on presence of the
>> respective usage id in the descriptor. This will allow to register ALS
>> with limited channel support. Append the timestamp as the last channel.
>>
>> When not all usage ids are present, the scan index is adjusted to
>> exclude unsupported channels.
>>
>> There is no intentional function changes done.
>>
>> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>> ---
>> v3:
>> Addressed comments from Jonthan:
>> - Remove channel allocation and move to iio_priv()
>> - Parse all usage IDs in a single loop and continue
>> for failure. This way the temperature and chromaticity
>> will not need any special processing to parse usage ids.
>> - Don't leave empty channel indexes
>>
>> v2:
>> New change
>>
>> drivers/iio/light/hid-sensor-als.c | 56 +++++++++++++++++++++---------
>> 1 file changed, 39 insertions(+), 17 deletions(-)
>>
>> diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
>> index 5cd27f04b45e..72a7c01c97f8 100644
>> --- a/drivers/iio/light/hid-sensor-als.c
>> +++ b/drivers/iio/light/hid-sensor-als.c
>> @@ -25,17 +25,26 @@ struct als_state {
>> struct hid_sensor_hub_callbacks callbacks;
>> struct hid_sensor_common common_attributes;
>> struct hid_sensor_hub_attribute_info als[CHANNEL_SCAN_INDEX_MAX];
>> + struct iio_chan_spec channels[CHANNEL_SCAN_INDEX_MAX + 1];
>> struct {
>> u32 illum[CHANNEL_SCAN_INDEX_MAX];
>> + u32 scan_index[CHANNEL_SCAN_INDEX_MAX];
>> u64 timestamp __aligned(8);
>> } scan;
>> int scale_pre_decml;
>> int scale_post_decml;
>> int scale_precision;
>> int value_offset;
>> + int num_channels;
>> s64 timestamp;
>> };
>>
>> +/* The order of usage ids must match scan index starting from CHANNEL_SCAN_INDEX_INTENSITY */
>> +static const u32 als_usage_ids[] = {
>> + HID_USAGE_SENSOR_LIGHT_ILLUM,
>> + HID_USAGE_SENSOR_LIGHT_ILLUM,
>> +};
>> +
>> static const u32 als_sensitivity_addresses[] = {
>> HID_USAGE_SENSOR_DATA_LIGHT,
>> HID_USAGE_SENSOR_LIGHT_ILLUM,
>> @@ -216,11 +225,14 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
>> struct als_state *als_state = iio_priv(indio_dev);
>> int ret = -EINVAL;
>> u32 sample_data = *(u32 *)raw_data;
>> + int scan_index;
>>
>> switch (usage_id) {
>> case HID_USAGE_SENSOR_LIGHT_ILLUM:
>> - als_state->scan.illum[CHANNEL_SCAN_INDEX_INTENSITY] = sample_data;
>> - als_state->scan.illum[CHANNEL_SCAN_INDEX_ILLUM] = sample_data;
>> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_INTENSITY];
>> + als_state->scan.illum[scan_index] = sample_data;
>> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_ILLUM];
>> + als_state->scan.illum[scan_index] = sample_data;
> Could you please use original above change which works fine for some reason if
> we use this change als_state->scan.scan_index we are getting garbage value.
I think this is because of the issue which you found later for this patch.
>> ret = 0;
>> break;
>> case HID_USAGE_SENSOR_TIME_TIMESTAMP:
>> @@ -237,27 +249,39 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
>> /* Parse report which is specific to an usage id*/
>> static int als_parse_report(struct platform_device *pdev,
>> struct hid_sensor_hub_device *hsdev,
>> - struct iio_chan_spec *channels,
>> unsigned usage_id,
>> struct als_state *st)
>> {
>> - int ret;
>> + struct iio_chan_spec *channels;
>> + int ret, index = 0;
>> int i;
>>
>> + channels = st->channels;
>> +
>> for (i = 0; i <= CHANNEL_SCAN_INDEX_ILLUM; ++i) {
> Could you please change CHANNEL_SCAN_INDEX_ILLUM to CHANNEL_SCAN_INDEX_MAX
> which helps remaining 2 patches in the series.
>
Makes sense.
Thanks,
Srinivas
>> ret = sensor_hub_input_get_attribute_info(hsdev,
>> HID_INPUT_REPORT,
>> usage_id,
>> - HID_USAGE_SENSOR_LIGHT_ILLUM,
>> + als_usage_ids[i],
>> &st->als[i]);
>> if (ret < 0)
>> - return ret;
>> - als_adjust_channel_bit_mask(channels, i, st->als[i].size);
>> + continue;
>> +
>> + channels[index] = als_channels[i];
>> + st->scan.scan_index[i] = index;
>> +
>> + als_adjust_channel_bit_mask(channels, index, st->als[i].size);
>> + ++index;
>>
>> dev_dbg(&pdev->dev, "als %x:%x\n", st->als[i].index,
>> st->als[i].report_id);
>> }
>>
>> + st->num_channels = index;
>> + /* Return success even if one usage id is present */
>> + 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);
>> @@ -293,15 +317,7 @@ static int hid_als_probe(struct platform_device *pdev)
>> return ret;
>> }
>>
>> - indio_dev->channels = devm_kmemdup(&pdev->dev, als_channels,
>> - sizeof(als_channels), GFP_KERNEL);
>> - if (!indio_dev->channels) {
>> - dev_err(&pdev->dev, "failed to duplicate channels\n");
>> - return -ENOMEM;
>> - }
>> -
>> ret = als_parse_report(pdev, hsdev,
>> - (struct iio_chan_spec *)indio_dev->channels,
>> hsdev->usage,
>> als_state);
>> if (ret) {
>> @@ -309,8 +325,14 @@ static int hid_als_probe(struct platform_device *pdev)
>> return ret;
>> }
>>
>> - indio_dev->num_channels =
>> - ARRAY_SIZE(als_channels);
>> + /* Add timestamp channel */
>> + als_state->channels[als_state->num_channels] = als_channels[CHANNEL_SCAN_INDEX_TIMESTAMP];
>> + als_state->channels[als_state->num_channels].scan_index = als_state->num_channels;
>> +
>> + /* +1 for adding timestamp channel */
>> + indio_dev->num_channels = als_state->num_channels + 1;
>> +
>> + indio_dev->channels = als_state->channels;
>> indio_dev->info = &als_info;
>> indio_dev->name = name;
>> indio_dev->modes = INDIO_DIRECT_MODE;
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically
2024-01-13 16:03 ` Jonathan Cameron
@ 2024-02-04 13:06 ` Srinivas Pandruvada
0 siblings, 0 replies; 11+ messages in thread
From: Srinivas Pandruvada @ 2024-02-04 13:06 UTC (permalink / raw)
To: Jonathan Cameron
Cc: jikos, lars, Basavaraj.Natikar, linux-input, linux-iio,
linux-kernel
Hi Jonathan,
On 1/13/24 08:03, Jonathan Cameron wrote:
> On Tue, 9 Jan 2024 10:00:04 -0800
> Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
>
>> Instead of assuming that every channel defined statically by
>> als_channels[] is present, assign dynamically based on presence of the
>> respective usage id in the descriptor. This will allow to register ALS
>> with limited channel support. Append the timestamp as the last channel.
>>
>> When not all usage ids are present, the scan index is adjusted to
>> exclude unsupported channels.
>>
>> There is no intentional function changes done.
>>
>> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>> ---
>> v3:
>> Addressed comments from Jonthan:
>> - Remove channel allocation and move to iio_priv()
>> - Parse all usage IDs in a single loop and continue
>> for failure. This way the temperature and chromaticity
>> will not need any special processing to parse usage ids.
>> - Don't leave empty channel indexes
> There isn't really a problem if you did want to leave them.
> There are a number of other devices that do leave gaps and userspace
> code shouldn't mind that. I don't mind them being more tightly packed
> though so this is also fine.
Submitted v4 leaving gaps.
>
>
> I was just looking at the driver and noticed one other oddity.
> In als_capture_sample, it always returns -EINVAL if the timestamp channel
> is being queried.
Correct. But hid-sensor-hub core ignores return value, so it doesn't
cause any issue.
But I sent a separate patch to fix this.
>
>> v2:
>> New change
>>
>> drivers/iio/light/hid-sensor-als.c | 56 +++++++++++++++++++++---------
>> 1 file changed, 39 insertions(+), 17 deletions(-)
>>
>> diff --git a/drivers/iio/light/hid-sensor-als.c b/drivers/iio/light/hid-sensor-als.c
>> index 5cd27f04b45e..72a7c01c97f8 100644
>> --- a/drivers/iio/light/hid-sensor-als.c
>> +++ b/drivers/iio/light/hid-sensor-als.c
>> @@ -25,17 +25,26 @@ struct als_state {
>> struct hid_sensor_hub_callbacks callbacks;
>> struct hid_sensor_common common_attributes;
>> struct hid_sensor_hub_attribute_info als[CHANNEL_SCAN_INDEX_MAX];
>> + struct iio_chan_spec channels[CHANNEL_SCAN_INDEX_MAX + 1];
>> struct {
>> u32 illum[CHANNEL_SCAN_INDEX_MAX];
>> + u32 scan_index[CHANNEL_SCAN_INDEX_MAX];
> This looks unlikely to end up right with a varying number of channels.
> I'm assuming the device always captures all available channels.
> As such, if there are 2 channels the timestamp will end up at byte 8 onwards.
> If there are 3 channels, byte 16 onwards etc.
>
> Usually when we have a floating timestamp like this we just rely on expanding
> the channel array to leave space and force the alignment of that to be suitable
> for taking a timestamp.
>
> I'm a bit confused not to see available_scan_mask being set though.
> If userspace previously requested illumination only would the data
> have ended up in the right location (offset 0?)
Add this.
> If you set available_scan_masks to specify all channels then the
> IIO core will move things around for you. If it's not provided then
> it is up to the driver to figure out where to put the data.
>
> Otherwise the patch looks fine to me.
Please check v4, if it solve the above issues.
Thanks,
Srinivas
> Jonathan
>
>
>
>> u64 timestamp __aligned(8);
>> } scan;
>> int scale_pre_decml;
>> int scale_post_decml;
>> int scale_precision;
>> int value_offset;
>> + int num_channels;
>> s64 timestamp;
>> };
>>
>> +/* The order of usage ids must match scan index starting from CHANNEL_SCAN_INDEX_INTENSITY */
>> +static const u32 als_usage_ids[] = {
>> + HID_USAGE_SENSOR_LIGHT_ILLUM,
>> + HID_USAGE_SENSOR_LIGHT_ILLUM,
>> +};
>> +
>> static const u32 als_sensitivity_addresses[] = {
>> HID_USAGE_SENSOR_DATA_LIGHT,
>> HID_USAGE_SENSOR_LIGHT_ILLUM,
>> @@ -216,11 +225,14 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
>> struct als_state *als_state = iio_priv(indio_dev);
>> int ret = -EINVAL;
>> u32 sample_data = *(u32 *)raw_data;
>> + int scan_index;
>>
>> switch (usage_id) {
>> case HID_USAGE_SENSOR_LIGHT_ILLUM:
>> - als_state->scan.illum[CHANNEL_SCAN_INDEX_INTENSITY] = sample_data;
>> - als_state->scan.illum[CHANNEL_SCAN_INDEX_ILLUM] = sample_data;
>> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_INTENSITY];
>> + als_state->scan.illum[scan_index] = sample_data;
>> + scan_index = als_state->scan.scan_index[CHANNEL_SCAN_INDEX_ILLUM];
>> + als_state->scan.illum[scan_index] = sample_data;
>> ret = 0;
>> break;
>> case HID_USAGE_SENSOR_TIME_TIMESTAMP:
>> @@ -237,27 +249,39 @@ static int als_capture_sample(struct hid_sensor_hub_device *hsdev,
>> /* Parse report which is specific to an usage id*/
>> static int als_parse_report(struct platform_device *pdev,
>> struct hid_sensor_hub_device *hsdev,
>> - struct iio_chan_spec *channels,
>> unsigned usage_id,
>> struct als_state *st)
>> {
>> - int ret;
>> + struct iio_chan_spec *channels;
>> + int ret, index = 0;
>> int i;
>>
>> + channels = st->channels;
>> +
>> for (i = 0; i <= CHANNEL_SCAN_INDEX_ILLUM; ++i) {
>> ret = sensor_hub_input_get_attribute_info(hsdev,
>> HID_INPUT_REPORT,
>> usage_id,
>> - HID_USAGE_SENSOR_LIGHT_ILLUM,
>> + als_usage_ids[i],
>> &st->als[i]);
>> if (ret < 0)
>> - return ret;
>> - als_adjust_channel_bit_mask(channels, i, st->als[i].size);
>> + continue;
>> +
>> + channels[index] = als_channels[i];
>> + st->scan.scan_index[i] = index;
>> +
>> + als_adjust_channel_bit_mask(channels, index, st->als[i].size);
>> + ++index;
>>
>> dev_dbg(&pdev->dev, "als %x:%x\n", st->als[i].index,
>> st->als[i].report_id);
>> }
>>
>> + st->num_channels = index;
>> + /* Return success even if one usage id is present */
>> + 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);
>> @@ -293,15 +317,7 @@ static int hid_als_probe(struct platform_device *pdev)
>> return ret;
>> }
>>
>> - indio_dev->channels = devm_kmemdup(&pdev->dev, als_channels,
>> - sizeof(als_channels), GFP_KERNEL);
>> - if (!indio_dev->channels) {
>> - dev_err(&pdev->dev, "failed to duplicate channels\n");
>> - return -ENOMEM;
>> - }
>> -
>> ret = als_parse_report(pdev, hsdev,
>> - (struct iio_chan_spec *)indio_dev->channels,
>> hsdev->usage,
>> als_state);
>> if (ret) {
>> @@ -309,8 +325,14 @@ static int hid_als_probe(struct platform_device *pdev)
>> return ret;
>> }
>>
>> - indio_dev->num_channels =
>> - ARRAY_SIZE(als_channels);
>> + /* Add timestamp channel */
>> + als_state->channels[als_state->num_channels] = als_channels[CHANNEL_SCAN_INDEX_TIMESTAMP];
>> + als_state->channels[als_state->num_channels].scan_index = als_state->num_channels;
>> +
>> + /* +1 for adding timestamp channel */
>> + indio_dev->num_channels = als_state->num_channels + 1;
>> +
>> + indio_dev->channels = als_state->channels;
>> indio_dev->info = &als_info;
>> indio_dev->name = name;
>> indio_dev->modes = INDIO_DIRECT_MODE;
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2024-02-04 13:06 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-01-09 18:00 [PATCH v3 0/4] Add support of color temperature and chromaticity Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 1/4] iio: hid-sensor-als: Assign channels dynamically Srinivas Pandruvada
2024-01-13 16:03 ` Jonathan Cameron
2024-02-04 13:06 ` Srinivas Pandruvada
2024-01-25 5:51 ` Basavaraj Natikar
2024-01-25 6:01 ` Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 2/4] iio: hid-sensor-als: Remove hardcoding of values for enums Srinivas Pandruvada
2024-01-09 18:00 ` [PATCH v3 3/4] iio: hid-sensor-als: Add light color temperature support Srinivas Pandruvada
2024-01-25 5:55 ` Basavaraj Natikar
2024-01-09 18:00 ` [PATCH v3 4/4] iio: hid-sensor-als: Add light chromaticity support Srinivas Pandruvada
2024-01-25 5:56 ` Basavaraj Natikar
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).