linux-kernel - input: Device Tree Properties for Captouch Button Device Registers

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]

Message-ID: <BL0PR07MB4115574AA13B8F8C2E036644ADE50@BL0PR07MB4115.namprd07.prod.outlook.com>
Date:   Wed, 19 Jun 2019 12:55:03 +0000
From:   Ken Sloat <KSloat@...pglobal.com>
To:     "dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>
CC:     Kasun Beddewela <KBeddewela@...pglobal.com>,
        "linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Ken Sloat <KSloat@...pglobal.com>
Subject: input: Device Tree Properties for Captouch Button Device Registers

Hello Dmitry,

We have a new input driver we are currently working on and would like to submit
to the Linux kernel when we finish it. Specifically, this is a cap touch IC which
implements potentially multiple individual proximity and cap touch buttons (which
would be reported like key events as seems to be the standard). A couple of questions:

1. What is the preferred/proper method to expose the many registers that
these devices have via device tree?

These devices have dozens of registers, many of which might be needed depending
on the individual application. It wouldn't be useful in the majority of cases to provide
default values in the driver as the registers are custom tuned to the individual application.

2. Where should this device live? I am guessing in input/misc?

Thanks,
Ken Sloat