From: Jonathan Cameron <jic23@kernel.org>
To: Philipp Jungkamp <p.jungkamp@gmx.net>
Cc: Jiri Kosina <jikos@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 1/4] HID: hid-sensor-custom: Allow more custom iio sensors
Date: Sat, 26 Nov 2022 19:11:03 +0000 [thread overview]
Message-ID: <20221126191103.6ef517a1@jic23-huawei> (raw)
In-Reply-To: <20221124233841.3103-2-p.jungkamp@gmx.net>
On Fri, 25 Nov 2022 00:38:38 +0100
Philipp Jungkamp <p.jungkamp@gmx.net> wrote:
> The known LUID table for established/known custom HID sensors was
> limited to sensors with "INTEL" as manufacturer. But some vendors such
> as Lenovo also include fairly standard iio sensors (e.g. ambient light)
> in their custom sensors.
>
> Expand the known custom sensors table by a tag used for the platform
> device name and match sensors based on the LUID as well as optionally
> on model and manufacturer properties.
>
> Signed-off-by: Philipp Jungkamp <p.jungkamp@gmx.net>
LGTM
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
next prev parent reply other threads:[~2022-11-26 18:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 23:38 [PATCH v4 0/4] IIO: More HID custom sensors Philipp Jungkamp
2022-11-24 23:38 ` [PATCH v4 1/4] HID: hid-sensor-custom: Allow more custom iio sensors Philipp Jungkamp
2022-11-26 19:11 ` Jonathan Cameron [this message]
2022-11-24 23:38 ` [PATCH v4 2/4] HID: hid-sensor-custom: Add LISS custom sensors Philipp Jungkamp
2022-11-26 19:11 ` Jonathan Cameron
2022-11-24 23:38 ` [PATCH v4 3/4] IIO: hid-sensor-als: Use generic usage Philipp Jungkamp
2022-11-26 19:05 ` Jonathan Cameron
2022-11-24 23:38 ` [PATCH v4 4/4] IIO: hid-sensor-prox: " Philipp Jungkamp
2022-11-26 19:04 ` Jonathan Cameron
2022-11-27 17:33 ` [PATCH v4 0/4] IIO: More HID custom sensors srinivas pandruvada
2022-12-13 22:51 ` Philipp Jungkamp
2022-12-14 9:27 ` Jonathan Cameron
2022-12-14 17:20 ` Jiri Kosina
2022-12-15 16:21 ` Jonathan Cameron
2022-12-20 14:26 ` Jiri Kosina
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=20221126191103.6ef517a1@jic23-huawei \
--to=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=p.jungkamp@gmx.net \
--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