From: Jiri Kosina <jikos@kernel.org>
To: Ye Xiang <xiang.ye@intel.com>
Cc: jic23@kernel.org, srinivas.pandruvada@linux.intel.com,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] HID: hid-sensor-custom: Add custom sensor iio support
Date: Mon, 4 Jan 2021 10:45:54 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2101041045320.25826@cbobk.fhfr.pm> (raw)
In-Reply-To: <20201215054444.9324-2-xiang.ye@intel.com>
On Tue, 15 Dec 2020, Ye Xiang wrote:
> Currently custom sensors properties are not decoded and it is up to
> user space to interpret.
>
> Some manufacturers already standardized the meaning of some custom sensors.
> They can be presented as a proper IIO sensor. We can identify these sensors
> based on manufacturer and serial number property in the report.
>
> This change is identifying hinge sensor when the manufacturer is "INTEL".
> This creates a platform device so that a sensor driver can be loaded to
> process these sensors.
>
> Signed-off-by: Ye Xiang <xiang.ye@intel.com>
Acked-by: Jiri Kosina <jkosina@suse.cz>
Jonathan, feel free to take this with the rest through your tree. Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2021-01-04 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 5:44 [PATCH v4 0/3] add custom hinge sensor support Ye Xiang
2020-12-15 5:44 ` [PATCH v4 1/3] HID: hid-sensor-custom: Add custom sensor iio support Ye Xiang
2021-01-04 9:45 ` Jiri Kosina [this message]
2020-12-15 5:44 ` [PATCH v4 2/3] iio: hid-sensors: Add hinge sensor driver Ye Xiang
2020-12-30 12:03 ` Jonathan Cameron
2020-12-15 5:44 ` [PATCH v4 3/3] iio:Documentation: Add documentation for hinge sensor channels Ye Xiang
2020-12-30 12:05 ` [PATCH v4 0/3] add custom hinge sensor support Jonathan Cameron
2020-12-31 2:46 ` Ye, Xiang
2021-01-09 18:41 ` 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=nycvar.YFH.7.76.2101041045320.25826@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=xiang.ye@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).