linux-kernel - Re: Re: [PATCH v5 5/5] Extcon: adc-jack driver to support 3.5 pi or simliar devices

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

Message-ID: <20120214171737.GA2321@opensource.wolfsonmicro.com>
Date:	Tue, 14 Feb 2012 17:17:39 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	MyungJoo Ham <myungjoo.ham@...sung.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	NeilBrown <neilb@...e.de>, Randy Dunlap <rdunlap@...otime.net>,
	Mike Lockwood <lockwood@...roid.com>,
	Arve Hj?nnevag <arve@...roid.com>,
	박경민 <kyungmin.park@...sung.com>,
	김동근 <dg77.kim@...sung.com>,
	Greg KH <gregkh@...e.de>, Arnd Bergmann <arnd@...db.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Morten CHRISTIANSEN <morten.christiansen@...ricsson.com>,
	John Stultz <john.stultz@...aro.org>,
	Joerg Roedel <joerg.roedel@....com>, myungjoo.ham@...il.com
Subject: Re: Re: [PATCH v5 5/5] Extcon: adc-jack driver to support 3.5 pi
	or simliar devices

On Tue, Feb 14, 2012 at 07:00:48AM +0000, MyungJoo Ham wrote:
> Mark Brown wrote:

> > No, that's not what I'm suggesting - what I'm suggesting is that rather
> > than having a callback for implementing the ADC read functionality this
> > should work as an in-kernel IIO driver so it'll just automatically work
> > with any ADC without needing code to hook things up.  Unless I've not
> > understood your comment fully.

> Ok. Do you mean that we should give struct iio_dev * and struct
> iio_chan_spec * instead of a callback?  I thought there was no
> standard framework for ADC (the reason why this is a simple callback);
> however, may I regard iio/adc as the standard for ADC? (I see some ADC
> device drivers in HWMON)

Yes, the idea is that IIO becomes the standard way of using general
purpose ADCs like this in the kernel rather than having lots of similar
custom APIs floating around with callbacks as we do now.

> Do I need to make this driver as an iio device driver in order to do this? I guess including iio.h would be enough anyway.

I'd not expect so, I'd expect it's just a user of IIO.
--
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/