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: [PATCH 0/1] input: keyboard: add qci keyboard driver
Date: Fri, 27 Aug 2010 18:14:53 -0400 [thread overview]
Message-ID: <4C7838DD.1020004@codeaurora.org> (raw)
This is an update of the keyboard driver which Quanta previously posted
to linux-input. Like the touchpad driver, I'm taking over maintenance
for code aurora forum.
The keyboard is attached to an embedded controller which is accessed
through I2C. It has a dedicated I2C address and its own interrupt line,
so it is not treated as an mfd. Although a PS/2 command, 0xF4, is used
to initialize the keyboard, the EC does not respond to other PS/2
commands. I have tried a serio driver on the port and attempted to use
keyboard drivers like xtkbd to communicate with it. These fail for
similar reasons to those discussed in the qci touchpad thread. This is
the reason for having this as a stand-alone driver.
--
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 reply other threads:[~2010-08-27 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 22:14 Neil Leeder [this message]
2010-08-27 22:18 ` [PATCH 1/1] input: keyboard: add qci keyboard driver 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
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=4C7838DD.1020004@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).