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: <20080521152009.0a227c3e@hyperion.delvare>
Date:	Wed, 21 May 2008 15:20:09 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Jonathan Cameron <Jonathan.Cameron@...il.com>
Cc:	"Hans J. Koch" <hjk@...utronix.de>, linux-kernel@...r.kernel.org,
	spi-devel-general@...ts.sourceforge.net,
	LM Sensors <lm-sensors@...sensors.org>,
	Dmitry Torokhov <dtor@...l.ru>
Subject: Re: Accelerometer, Gyros and ADC's etc within the kernel.

On Wed, 21 May 2008 11:04:38 +0100, Jonathan Cameron wrote:
> Definitely agreed that it makes sense to put DACs and ADCs in the same 
> general place and obviously there are plenty of devices out there that do
> both.

Note that hardware monitoring chips can include ADCs and DACs: the
former to monitor system voltages, and the later to control fans (most
chips use PWM for that but a few use DACs.) ADCs and DACs are, much
like GPIOs, usable for a variety of different purposes. I doubt that
there would be any benefit in abstracting DACs and ADCs the way we did
for GPIOs, but the important point here is that we really want to group
the drivers according to their functionality and not technical
implementation details.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ