Re: [External] Using IIO to export laptop palm-sensor and lap-mode info to userspace?

From: Hans de Goede <hdegoede@redhat.com>
To: Bastien Nocera <hadess@hadess.net>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: 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
Subject: Re: [External] Using IIO to export laptop palm-sensor and lap-mode info to userspace?
Date: Thu, 19 Nov 2020 16:24:19 +0100	[thread overview]
Message-ID: <19622786-6aa9-483a-bbad-28112ea3609a@redhat.com> (raw)
In-Reply-To: <96e2c4ebd7e826b6ea52f72f301fb5e8c33479d5.camel@hadess.net>

Hi,

On 11/19/20 4:16 PM, Bastien Nocera wrote:
> On Wed, 2020-11-11 at 22:23 -0800, Dmitry Torokhov wrote:
>> <snip>
>> I am not sure if multiplexing all proximity switches into one evdev
>> node
>> is that great option, as I am sure we'll soon have devices with 2x
>> palmrest switches and being capable finely adjusting transmit power,
>> etc.
> 
> Hans, Mark, so is there a consensus to how we should export the "lap-
> mode"?

Given Dmitry's input itl ooks like we need to go back to using iio
for this. Probably with something like my initial proposal wherre we
add an in_proximity_location sysfs attribute to the iio-devices which
represent the lap-mode and palmrest sensors. But ChromeOS is doing
something different to figure out which sensor is which, so this needs
a bit more discussion.

I'll go and reply to Dmitry's latest mail on this now and then we will
see from there.

> I had nearly finished working on updated code and all the test suite
> changes needed to use an input device with switches when IIO started
> being discussed, so I stopped in my tracks.

Ouch, sorry about this.

Regards,

Hans