linux-kernel - Re: [PATCH RESEND] x86, intel

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: <20120411103827.GH3163@opensource.wolfsonmicro.com>
Date:	Wed, 11 Apr 2012 11:38:28 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org,
	Jonathan Cameron <jic23@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH RESEND] x86, intel_mid: ADC management

On Wed, Apr 11, 2012 at 11:24:11AM +0100, Alan Cox wrote:

> If that code gets pulled out of IIO dumped into drivers/adc and has a bit
> of a different API to the gpadc code then no problem, gpadc can follow it
> happily enough. IIO can use it from staging and IIO can migrate whenever.

> It does make sense to think hard about userspace APIs for IIO but for
> kernel APIs its really being too conservative - we break kernel APIs
> every release. They are not set into stone.

The way I keep thinking about this (which I'm sure I've suggested
before) is that we should be refactoring IIO such that the userspace ABI
is just another in-kernel consumer of the device driver bit of IIO and
that driver bit should be small enough to just use.  I think that winds
up being roughly equivalent to your suggestion but means that there's
just one place to put the drivers which seems like a win.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)