linux-kernel - Re: [PATCH] Input: cap1106

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <53EB1EFA-3BFF-4818-A524-B3ED3CF62D56@theobroma-systems.com>
Date:	Tue, 2 Sep 2014 13:01:11 +0200
From:	Klaus Goger <klaus.goger@...obroma-systems.com>
To:	Daniel Mack <zonque@...il.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Input: cap1106 - fix register definition

On Sep 2, 2014, at 9:43 AM, Daniel Mack <zonque@...il.com> wrote:
> On 09/02/2014 08:32 AM, Klaus Goger wrote:
>> Use the correct register address for Calibration Active and Interrupt
>> Enable
>> 
>> Signed-off-by: Klaus Goger <klaus.goger@...obroma-systems.com>
> 
> These register definitions are currently unused, but your fix is
> correct. Just curious - are you planning to send patches that make use
> of them?

I want to use CAP1106_REG_SENSITIVITY_CONTROL but I have yet to
decide how to expose it to the user. Probably adding another device tree
option. But somehow it feels like cluttering up the dts.
Once I have settled about that I will send patches.
--
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/