All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Doug Anderson <dianders@chromium.org>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Benson Leung <bleung@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	open list: HID CORE LAYER <linux-input@vger.kernel.org>,
	Guenter Roeck <groeck@chromium.org>, ;
Subject: Re: [PATCH] Input: cros_ec_keyb: Add support for a front proximity switch
Date: Fri, 15 Jan 2021 14:45:31 -0800	[thread overview]
Message-ID: <161075073197.3661239.6820430732230306799@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <X/dlKKeAHU/Ab+VD@google.com>

Quoting Dmitry Torokhov (2021-01-07 11:46:48)
> 
> Yes, I understand that on some devices the proximity sensors are not
> true sensors but rather on/off signals, potentially derived from a
> multitude of sources. However there is still a benefit in exposing them
> as IIO proximity devices with limited reporting representing
> [near, infinity] range/values. This will mean that userspace needs to
> monitor only one set of devices (IIO) instead of both IIO and input, and
> will not require constantly expanding EV_SW set to account for
> ever-growing number of proximity sensors (lap, palm, general presence,
> etc).

Ok, no problem. I think I'll have to spin up a small driver to handle
this as an IIO proximity device and then register the IIO child device
from the cros ec driver. Let me see how that goes.

  reply	other threads:[~2021-01-15 22:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05  0:47 [PATCH] Input: cros_ec_keyb: Add support for a front proximity switch Stephen Boyd
2021-01-07  1:16 ` Doug Anderson
2021-01-07  2:21   ` Dmitry Torokhov
2021-01-07 14:57     ` Doug Anderson
2021-01-07 19:46       ` Dmitry Torokhov
2021-01-15 22:45         ` Stephen Boyd [this message]
2021-02-02 13:43         ` Pavel Machek
     [not found]   ` <CABXOdTcT4f_mg=ukPd0sD90o-aKg3qgiuLDRNPU8SUuFnFbRxA@mail.gmail.com>
2021-01-15 22:43     ` Stephen Boyd

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=161075073197.3661239.6820430732230306799@swboyd.mtv.corp.google.com \
    --to=swboyd@chromium.org \
    --cc=bleung@chromium.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.