From: Neil Leeder <nleeder@codeaurora.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Horace Fu <horace.fu@quantatw.com>,
Hsin.Wu@quantatw.com
Subject: Re: [PATCH 0/1] input: keyboard: add qci keyboard driver
Date: Mon, 30 Aug 2010 14:22:10 -0400 [thread overview]
Message-ID: <4C7BF6D2.5080501@codeaurora.org> (raw)
In-Reply-To: <201008271533.01542.dmitry.torokhov@gmail.com>
On 8/27/2010 6:33 PM, Dmitry Torokhov wrote:
> No, this is crazy... This is a twin-brother of the touchpad driver and
> I really do not understand why chip claiming to have PS/2 interface
> (3 ports if I were to believe the diagram) would not allow us talk to
> the devices...
I didn't provide a key bit of information, sorry. The keyboard is not
attached to the EC's PS/2 port. It is on a matrix of GPIOs.
I was trying to explain that even though the firmware on the EC uses
0xF4 written over i2c to initialize it, it doesn't appear to support
other PS/2 commands directed to the keyboard on the GPIO matrix.
--
Neil
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-08-30 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 22:14 [PATCH 0/1] input: keyboard: add qci keyboard driver Neil Leeder
2010-08-27 22:18 ` [PATCH 1/1] " Neil Leeder
2010-09-02 8:51 ` Trilok Soni
2010-08-27 22:33 ` [PATCH 0/1] " Dmitry Torokhov
2010-08-30 18:22 ` Neil Leeder [this message]
2010-08-30 21:55 ` Dmitry Torokhov
2010-08-31 20:54 ` Neil Leeder
2010-09-01 6:34 ` Dmitry Torokhov
2010-09-03 19:13 ` Neil Leeder
2010-09-03 20:37 ` Dmitry Torokhov
2010-09-07 21:57 ` Neil Leeder
2010-09-07 22:14 ` Dmitry Torokhov
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=4C7BF6D2.5080501@codeaurora.org \
--to=nleeder@codeaurora.org \
--cc=Hsin.Wu@quantatw.com \
--cc=dmitry.torokhov@gmail.com \
--cc=horace.fu@quantatw.com \
--cc=linux-arm-msm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).