public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Gregor Riepl <onitake@gmail.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH resend] Input: silead - Add support for capactive home button found on some x86 tablets
Date: Sat, 14 Oct 2017 10:08:32 -0700	[thread overview]
Message-ID: <20171014170832.eykxrf4eaxlah75e@dtor-ws> (raw)
In-Reply-To: <a2efc457-5c23-2327-948a-e85e780b7e03@redhat.com>

On Sat, Oct 14, 2017 at 10:34:23AM +0200, Hans de Goede wrote:
> Hi,
> 
> On 14-10-17 01:48, Dmitry Torokhov wrote:
> > On Wed, Oct 11, 2017 at 11:46:06AM +0200, Hans de Goede wrote:
> > > On some x86 tablets with a silead touchscreen the windows logo on the
> > > front is a capacitive home button. Touching this button results in a touch
> > > with bits 12-15 of the Y coordinates set, while normally only the lower 12
> > > are used.
> > 
> > Do we know which ones?
> 
> Not really, but since we need to pass resolution info, etc. through
> device-properties (set in drivers/platform/x86/silead_dmi.c) we
> could add a device-property for this, this should also work for
> devicetree based models (although I've only seen the capacitive
> home button as the Windows logo on X86 hardware so far).
> 
> > Can we only set it in capabilities for devices
> > that actually have it?
> 
> If we add a device property for it, yes. I guess that is how
> you want me to handle this, so you will want a v2 which
> keys the enabling of the home button from a device-prop ?

Yes, please.

-- 
Dmitry

      reply	other threads:[~2017-10-14 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  9:46 [PATCH resend] Input: silead - Add support for capactive home button found on some x86 tablets Hans de Goede
2017-10-13 23:48 ` Dmitry Torokhov
2017-10-14  8:34   ` Hans de Goede
2017-10-14 17:08     ` Dmitry Torokhov [this message]

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=20171014170832.eykxrf4eaxlah75e@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=onitake@gmail.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