mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tai-hwa Liang <avatar@sentelic.com>
Cc: Oskari Saarenmaa <os@ohmu.fi>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] Input: sentelic - enabling absolute coordinates output for newer hardware
Date: Fri, 23 Mar 2012 10:01:49 +0000	[thread overview]
Message-ID: <20120323100149.338deb94@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1332474741-19426-3-git-send-email-avatar@sentelic.com>

> On the other hand, the FSP found on UX21/31 doesn't have hardware capability
> register other than PnP ID, which means that we'll have to figure out an
> alternative approach to identify such pad correctly; otherwise, blindly
> adding INPUT_PROP_BUTTONPAD property may compatability issues amongst
> existing FSPs.

If its tied to specific boards then the DMI data from the BIOS may be
what you need for that. It'll let you identify boards/vendors.

Alan

  reply	other threads:[~2012-03-23  9:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  3:52 [PATCH v2 0/5] Input: sentelic - multiple finger output support Tai-hwa Liang
2012-03-23  3:52 ` [PATCH v2 1/5] Input: sentelic - code refactorying for upcoming new hardware support Tai-hwa Liang
2012-03-23  3:52 ` [PATCH v2 2/5] Input: sentelic - enabling absolute coordinates output for newer hardware Tai-hwa Liang
2012-03-23 10:01   ` Alan Cox [this message]
2012-03-23  3:52 ` [PATCH v2 3/5] Input: sentelic - enabling hardware supported gesture ID output Tai-hwa Liang
2012-03-23  3:52 ` [PATCH v2 4/5] Input: sentelic - minor code cleaning up Tai-hwa Liang
2012-03-23  3:52 ` [PATCH v2 5/5] Input: sentelic - improving packet debugging information Tai-hwa Liang

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=20120323100149.338deb94@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=avatar@sentelic.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=os@ohmu.fi \
    /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

all inboxes | Powered by JetHome®