From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756399Ab2CWJ7o (ORCPT ); Fri, 23 Mar 2012 05:59:44 -0400 Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:35159 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753493Ab2CWJ7m (ORCPT ); Fri, 23 Mar 2012 05:59:42 -0400 Date: Fri, 23 Mar 2012 10:01:49 +0000 From: Alan Cox To: Tai-hwa Liang Cc: Oskari Saarenmaa , Dmitry Torokhov , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/5] Input: sentelic - enabling absolute coordinates output for newer hardware Message-ID: <20120323100149.338deb94@pyramind.ukuu.org.uk> In-Reply-To: <1332474741-19426-3-git-send-email-avatar@sentelic.com> References: <1332474741-19426-1-git-send-email-avatar@sentelic.com> <1332474741-19426-3-git-send-email-avatar@sentelic.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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