From: Hans de Goede <hdegoede@redhat.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
Jeff LaBundy <jeff@labundy.com>
Cc: Bastien Nocera <hadess@hadess.net>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Mark Pearson <markpearson@lenovo.com>,
linux-iio@vger.kernel.org, Nitin Joshi1 <njoshi1@lenovo.com>,
linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [External] Using IIO to export laptop palm-sensor and lap-mode info to userspace?
Date: Tue, 13 Oct 2020 10:38:14 +0200 [thread overview]
Message-ID: <152411c5-da14-c685-5252-5a4fa6fdbcb4@redhat.com> (raw)
In-Reply-To: <f4f00263-3beb-d941-eb3a-2be95684db66@metux.net>
Hi,
Enrico, thank you for your input.
See Mark's excellent email for answers to most of your questions,
I just have one little thing to add.
On 10/12/20 2:36 PM, Enrico Weigelt, metux IT consult wrote:
> On 08.10.20 09:10, Hans de Goede wrote:
<snip>
> Back to the technical side: IMHO we should first work out what the
> actual purpose of these sensors could be - are they useful for
> anything else than just these specific cases ? If not, I'm not
> sure whether it makes sense to put them into IIO at all, but using
> a specific board driver instead.
Right, also note that although there are doubtlessly sensors involved
we don't actually get any meaningful / direct access to these sensors.
We only get to talk to firmware which basically gives us:
Laptop is on someone's lap: yes/no
Someone is resting on the palmrest: yes/no
The lack of direct sensor access also makes this a less then
ideal case for using iio. So I believe that the suggestion
to extend the existing evdev/input SW_FRONT_PROXIMITY support
with 2 new SW_LAP_PROXIMITY and SW_PALMREST_PROXIMITY suggestion
makes a ton of sense. Switches are binary and given that this
really is a derived value and not raw sensor access using the
input system seems a better match.
Regards,
Hans
next prev parent reply other threads:[~2020-10-13 8:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f9b0ff6-3bf1-63c4-eb36-901cecd7c4d9@redhat.com>
[not found] ` <5a646527-7a1f-2fb9-7c09-8becdbff417b@lenovo.com>
2020-10-07 8:36 ` [External] Using IIO to export laptop palm-sensor and lap-mode info to userspace? Jonathan Cameron
2020-10-07 9:51 ` Hans de Goede
2020-10-07 11:35 ` Bastien Nocera
2020-10-07 13:08 ` Hans de Goede
2020-10-07 13:29 ` Bastien Nocera
2020-10-07 13:32 ` Hans de Goede
2020-10-08 0:14 ` Jeff LaBundy
2020-10-08 7:10 ` Hans de Goede
2020-10-09 2:19 ` Jeff LaBundy
2020-10-12 12:13 ` Hans de Goede
2020-10-13 21:59 ` Mark Pearson
2020-10-14 4:47 ` Jeff LaBundy
2020-10-14 8:16 ` Hans de Goede
2020-10-14 14:26 ` Mark Pearson
2020-10-12 12:36 ` Enrico Weigelt, metux IT consult
2020-10-13 1:12 ` Mark Pearson
2020-10-13 8:38 ` Hans de Goede [this message]
2020-11-12 6:23 ` Dmitry Torokhov
2020-11-12 9:50 ` Hans de Goede
2020-11-13 6:58 ` Dmitry Torokhov
2020-11-19 15:39 ` Hans de Goede
2020-11-19 16:11 ` Bastien Nocera
2020-11-20 9:59 ` Jonathan Cameron
2020-11-23 12:16 ` Hans de Goede
2020-11-23 16:07 ` Jonathan Cameron
2020-11-19 15:16 ` Bastien Nocera
2020-11-19 15:24 ` Hans de Goede
2020-11-19 15:58 ` Bastien Nocera
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=152411c5-da14-c685-5252-5a4fa6fdbcb4@redhat.com \
--to=hdegoede@redhat.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=jeff@labundy.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=lkml@metux.net \
--cc=markpearson@lenovo.com \
--cc=njoshi1@lenovo.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).