linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Harvey Yang <chenghaoyang@google.com>,
	linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] iio: Add channel type for attention
Date: Mon, 28 Oct 2024 20:34:37 +0000	[thread overview]
Message-ID: <20241028203437.3eb5268d@jic23-huawei> (raw)
In-Reply-To: <20241028-hpd-v2-3-18f6e79154d7@chromium.org>

On Mon, 28 Oct 2024 10:12:23 +0000
Ricardo Ribalda <ribalda@chromium.org> wrote:

> Add a new channel type representing if the user's attention state to the
> the system. This usually means if the user is looking at the screen or
> not.
> 
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> ---
>  Documentation/ABI/testing/sysfs-bus-iio | 7 +++++++
>  drivers/iio/industrialio-core.c         | 1 +
>  include/uapi/linux/iio/types.h          | 1 +
>  tools/iio/iio_event_monitor.c           | 2 ++
>  4 files changed, 11 insertions(+)
> 
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index 89943c2d54e8..d5a2f93bd051 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -2339,3 +2339,10 @@ KernelVersion:	6.10
>  Contact:	linux-iio@vger.kernel.org
>  Description:
>  		The value of current sense resistor in Ohms.
> +
> +What:		/sys/.../iio:deviceX/in_attention_raw
> +KernelVersion:	6.13
> +Contact:	linux-iio@vger.kernel.org
> +Description:
> +		Boolean value representing the user's attention to the system.
> +		This usually means if the user is looking at the screen or not.

Hmm. I should have thought of this when I replied to suggest a new channel type.
The question is 'units' for a decision.

Last time we hit something like this where processing is used to make a decision
we decided to at least allow for the concept of 'certainty'.

The idea being that smarter sensors would tell us something about how sure they
are that the attention is on the device.
The analogy being with activity detection. See in_activity_walking_input
in Documentation/ABI/testing/sysfs-bus-iio

Do you think that would be appropriate here as well?  For this device
it would take the values 0 and 100 rather than 0 and 1.


> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index 6a6568d4a2cb..bdfb51275b68 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -95,6 +95,7 @@ static const char * const iio_chan_type_name_spec[] = {
>  	[IIO_DELTA_VELOCITY] = "deltavelocity",
>  	[IIO_COLORTEMP] = "colortemp",
>  	[IIO_CHROMATICITY] = "chromaticity",
> +	[IIO_ATTENTION] = "attention",
>  };
>  
>  static const char * const iio_modifier_names[] = {
> diff --git a/include/uapi/linux/iio/types.h b/include/uapi/linux/iio/types.h
> index f2e0b2d50e6b..12886d4465e4 100644
> --- a/include/uapi/linux/iio/types.h
> +++ b/include/uapi/linux/iio/types.h
> @@ -51,6 +51,7 @@ enum iio_chan_type {
>  	IIO_DELTA_VELOCITY,
>  	IIO_COLORTEMP,
>  	IIO_CHROMATICITY,
> +	IIO_ATTENTION,
>  };
>  
>  enum iio_modifier {
> diff --git a/tools/iio/iio_event_monitor.c b/tools/iio/iio_event_monitor.c
> index 8073c9e4fe46..ed9a677f1028 100644
> --- a/tools/iio/iio_event_monitor.c
> +++ b/tools/iio/iio_event_monitor.c
> @@ -63,6 +63,7 @@ static const char * const iio_chan_type_name_spec[] = {
>  	[IIO_DELTA_VELOCITY] = "deltavelocity",
>  	[IIO_COLORTEMP] = "colortemp",
>  	[IIO_CHROMATICITY] = "chromaticity",
> +	[IIO_ATTENTION] = "attention",
>  };
>  
>  static const char * const iio_ev_type_text[] = {
> @@ -183,6 +184,7 @@ static bool event_is_known(struct iio_event_data *event)
>  	case IIO_DELTA_VELOCITY:
>  	case IIO_COLORTEMP:
>  	case IIO_CHROMATICITY:
> +	case IIO_ATTENTION:
>  		break;
>  	default:
>  		return false;
> 


  reply	other threads:[~2024-10-28 20:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 10:12 [PATCH v2 0/5] iio: hid-sensors-prox: Add support for more channels Ricardo Ribalda
2024-10-28 10:12 ` [PATCH v2 1/5] iio: hid-sensors: Add proximity and attention IDs Ricardo Ribalda
2024-10-28 10:12 ` [PATCH v2 2/5] iio: hid-sensors-prox: Factor-in hid_sensor_push_data Ricardo Ribalda
2024-10-28 10:12 ` [PATCH v2 3/5] iio: Add channel type for attention Ricardo Ribalda
2024-10-28 20:34   ` Jonathan Cameron [this message]
2024-10-29 12:20     ` Ricardo Ribalda
2024-10-29 14:38       ` Jonathan Cameron
2024-10-29 22:26         ` David Lechner
2024-10-30 16:50           ` Jonathan Cameron
2024-10-28 10:12 ` [PATCH v2 4/5] iio: hid-sensors-prox: Make proximity channel indexed Ricardo Ribalda
2024-10-28 10:12 ` [PATCH v2 5/5] iio: hid-sensor-prox: Add support for more channels Ricardo Ribalda
2024-10-28 20:29   ` 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=20241028203437.3eb5268d@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=chenghaoyang@google.com \
    --cc=jikos@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ribalda@chromium.org \
    --cc=srinivas.pandruvada@linux.intel.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;
as well as URLs for NNTP newsgroup(s).