linux-kernel - [PATCH 0/1] input: keyboard: add qci keyboard driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Aug 2010 18:14:53 -0400
From:	Neil Leeder <nleeder@...eaurora.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
	"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Horace Fu <horace.fu@...ntatw.com>, Hsin.Wu@...ntatw.com
Subject: [PATCH 0/1] input: keyboard: add qci keyboard driver

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/