From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Philipp Jungkamp <p.jungkamp@gmx.net>,
Jiri Kosina <jikos@kernel.org>,
Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, "Xu, Even" <even.xu@intel.com>
Subject: Re: [PATCH v2 2/4] HID: hid-sensor-custom: Add LISS custom sensors
Date: Fri, 18 Nov 2022 12:16:19 -0800 [thread overview]
Message-ID: <566e22568be0a8f231d6acedeece1bc4972ecd82.camel@linux.intel.com> (raw)
In-Reply-To: <20221117234302.3875-2-p.jungkamp@gmx.net>
On Fri, 2022-11-18 at 00:43 +0100, Philipp Jungkamp wrote:
> Add the Lenovo Intelligent Sensing Solution (LISS) custom sensors to
> the
> known custom sensors.
> ---
Generally you need write a version history:
v2
..
if no change just write
- No change.
> Here is the requested noop commit that changes the device ids for the
> known
> LISS sensors.
>
> drivers/hid/hid-sensor-custom.c | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/drivers/hid/hid-sensor-custom.c b/drivers/hid/hid-
> sensor-custom.c
> index 89e56913c92e..85db14406b23 100644
> --- a/drivers/hid/hid-sensor-custom.c
> +++ b/drivers/hid/hid-sensor-custom.c
> @@ -782,6 +782,29 @@ static const struct hid_sensor_custom_match
> hid_sensor_custom_known_table[] = {
> .luid = "020B000000000000",
> .manufacturer = "INTEL",
> },
> + /*
> + * Lenovo Intelligent Sensing Solution (LISS)
> + */
> + { /* ambient light */
> + .tag = "LISS",
> + .luid = "0041010200000082",
> + .model = "STK3X3X Sensor",
> + .manufacturer = "Vendor 258",
> + .check_dmi = true,
> + .dmi.matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + }
> + },
> + { /* human presence */
> + .tag = "LISS",
> + .luid = "0226000171AC0081",
> + .model = "VL53L1_HOD Sensor",
> + .manufacturer = "ST_MICRO",
> + .check_dmi = true,
> + .dmi.matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + }
> + },
> {}
> };
>
> --
> 2.38.1
>
next prev parent reply other threads:[~2022-11-18 20:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 12:11 PROBLEM: Lenovo ALS sensor disguised under custom usage Philipp Jungkamp
2022-11-16 23:19 ` [PATCH 1/3] HID: hid-sensor-custom: More custom iio sensors Philipp Jungkamp
2022-11-16 23:19 ` [PATCH 2/3] IIO: hid-sensor-als: Use generic usage Philipp Jungkamp
2022-11-17 15:09 ` Jonathan Cameron
2022-11-16 23:19 ` [PATCH 3/3] IIO: hid-sensor-prox: " Philipp Jungkamp
2022-11-17 15:14 ` Jonathan Cameron
2022-11-17 15:05 ` [PATCH 1/3] HID: hid-sensor-custom: More custom iio sensors Jonathan Cameron
2022-11-17 23:42 ` [PATCH v2 1/4] HID: hid-sensor-custom: Allow more " Philipp Jungkamp
2022-11-17 23:43 ` [PATCH v2 2/4] HID: hid-sensor-custom: Add LISS custom sensors Philipp Jungkamp
2022-11-18 20:16 ` srinivas pandruvada [this message]
2022-11-17 23:43 ` [PATCH v2 3/4] IIO: hid-sensor-als: Use generic usage Philipp Jungkamp
2022-11-17 23:43 ` [PATCH v2 4/4] IIO: hid-sensor-prox: " Philipp Jungkamp
2022-11-18 20:11 ` [PATCH v2 1/4] HID: hid-sensor-custom: Allow more custom iio sensors srinivas pandruvada
2022-11-17 23:48 ` [PATCH v3 " Philipp Jungkamp
2022-11-17 23:48 ` [PATCH v3 2/4] HID: hid-sensor-custom: Add LISS custom sensors Philipp Jungkamp
2022-11-17 23:48 ` [PATCH v3 3/4] IIO: hid-sensor-als: Use generic usage Philipp Jungkamp
2022-11-18 20:23 ` srinivas pandruvada
2022-11-21 17:59 ` Jiri Kosina
2022-11-21 19:55 ` srinivas pandruvada
2022-11-23 17:16 ` Jonathan Cameron
2022-11-17 23:48 ` [PATCH v3 4/4] IIO: hid-sensor-prox: " Philipp Jungkamp
2022-11-18 20:26 ` srinivas pandruvada
2022-11-23 17:17 ` Jonathan Cameron
2022-11-23 17:08 ` [PATCH v3 1/4] HID: hid-sensor-custom: Allow more custom iio sensors Jonathan Cameron
2022-11-23 17:10 ` 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=566e22568be0a8f231d6acedeece1bc4972ecd82.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=even.xu@intel.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=p.jungkamp@gmx.net \
/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).