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 1/3] iio: hid-sensors: Add proximity and attention IDs
Date: Sun, 27 Oct 2024 11:35:03 +0000 [thread overview]
Message-ID: <20241027113503.46113bcc@jic23-huawei> (raw)
In-Reply-To: <20241024-hpd-v1-1-2a125882f1f8@chromium.org>
On Thu, 24 Oct 2024 13:29:05 +0000
Ricardo Ribalda <ribalda@chromium.org> wrote:
> The HID Usage Table at https://usb.org/sites/default/files/hut1_5.pdf
>
> - 0x4b2 for Human Proximity Range
Add more here from the references the above has.
https://www.usb.org/sites/default/files/hutrr39b_0.pdf
Distance between a human and the computer. Default unit of
measure is meters;
> - 0x4bd for Human Attention Detected
>
Human-Presence sensors detect the presence of humans in the sensor’s field-of-view using
diverse and evolving technologies. Some presence sensors are implemented with low
resolution video cameras, which can additionally track a subject’s attention (i.e. if the
user is ‘looking’ at the system with the integrated sensor).
A Human-Presence sensor, providing a Host with the user’s attention state, allows the
Host to optimize its behavior. For example, to brighten/dim the system display, based on
the user’s attention to the system (potentially prolonging battery life).
This one is a 0/1 signal if I read the schema right. Which is also true for
the existing HUMAN_PRESENCE. Not a problem but worth mentioning in this description.
https://www.usb.org/sites/default/files/hutrr107-humanpresenceattention_1.pdf
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> ---
> include/linux/hid-sensor-ids.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/hid-sensor-ids.h b/include/linux/hid-sensor-ids.h
> index 6730ee900ee1..8a03d9696b1c 100644
> --- a/include/linux/hid-sensor-ids.h
> +++ b/include/linux/hid-sensor-ids.h
> @@ -30,6 +30,8 @@
> #define HID_USAGE_SENSOR_PROX 0x200011
> #define HID_USAGE_SENSOR_DATA_PRESENCE 0x2004b0
> #define HID_USAGE_SENSOR_HUMAN_PRESENCE 0x2004b1
> +#define HID_USAGE_SENSOR_HUMAN_PROXIMITY 0x2004b2
> +#define HID_USAGE_SENSOR_HUMAN_ATTENTION 0x2004bd
>
> /* Pressure (200031) */
> #define HID_USAGE_SENSOR_PRESSURE 0x200031
>
next prev parent reply other threads:[~2024-10-27 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 13:29 [PATCH 0/3] iio: hid-sensors-prox: Add support for more channels Ricardo Ribalda
2024-10-24 13:29 ` [PATCH 1/3] iio: hid-sensors: Add proximity and attention IDs Ricardo Ribalda
2024-10-27 11:35 ` Jonathan Cameron [this message]
2024-10-24 13:29 ` [PATCH 2/3] iio: hid-sensors-prox: Factor-in hid_sensor_push_data Ricardo Ribalda
2024-10-24 13:29 ` [PATCH 3/3] iio: hid-sensor-prox: Add support for more channels Ricardo Ribalda
2024-10-27 11:30 ` 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=20241027113503.46113bcc@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).