linux-kernel - Re: [UPDATED v4] WM97xx touchscreen drivers

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 for Android: free password hash cracker in your pocket

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

Message-ID: <3713.69.30.58.166.1202151624.squirrel@architechnical.net>
Date:	Mon, 4 Feb 2008 14:00:24 -0500 (EST)
From:	linux01@...hitechnical.net
To:	linux-kernel@...r.kernel.org
Subject: Re: [UPDATED v4] WM97xx touchscreen drivers

Mark Brown wrote:

> This patch series adds support for the touchscreen controllers provided
> by Wolfson Microelectronics WM97xx series chips in both polled and
> streaming modes.
>

I integrated this patch with our 2.6.24 kernel and it broke our APM-based
battery monitor, which uses an ADC channel on the 9712.  Support for this
multi-function chip series seems to be in a few places; would it make
sense to have one generic WM97xx driver in drivers/mfd and stack the
codec, touchscreen, etc, drivers logically above (in their respective
areas)?  In my experience with the Wolfson series a change to the sound
driver breaks touchscreen, a change to the touchscreen driver changes ADC
readings, etc, so I wanted to open dialog on what the right direction may
be as various Wolfson code starts making its way into the mainline.

Thanks,
Pete MacKay

--
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/