Return-Path: <linux-kernel-owner+w=401wt.eu-S1754161AbYJ2NGP@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754161AbYJ2NGP (ORCPT <rfc822;w@1wt.eu>);
	Wed, 29 Oct 2008 09:06:15 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753612AbYJ2NF7
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 29 Oct 2008 09:05:59 -0400
Received: from cassiel.sirena.org.uk ([80.68.93.111]:3877 "EHLO
	cassiel.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753054AbYJ2NF7 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 29 Oct 2008 09:05:59 -0400
Date: Wed, 29 Oct 2008 13:05:51 +0000
From: Mark Brown <broonie@sirena.org.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Jonathan Cameron <Jonathan.Cameron@gmail.com>,
       Liam Girdwood <lrg@kernel.org>, felipe.balbi@nokia.com,
       eric miao <eric.y.miao@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Regulator RFC] da903x: Where should usb charge pump support go?
Message-ID: <20081029130551.GB14648@sirena.org.uk>
References: <4906F500.7080100@cam.ac.uk> <20081028112341.GF27144@gandalf.research.nokia.com> <1225195382.28382.168.camel@dell-desktop.example.com> <4908547C.4090907@gmail.com> <20081029122705.GA14648@sirena.org.uk> <49085BA9.8050306@cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49085BA9.8050306@cam.ac.uk>
X-Cookie: Who messed with my anti-paranoia shot?
User-Agent: Mutt/1.5.13 (2006-08-11)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: broonie@sirena.org.uk
X-SA-Exim-Scanned: No (on cassiel.sirena.org.uk); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1184
Lines: 29

On Wed, Oct 29, 2008 at 12:48:41PM +0000, Jonathan Cameron wrote:
> Mark Brown wrote:

> > For WM8350 this is implemented as a device-specific function in the
> > driver core which is then used by other drivers to export the
> > information to relevant subsystems.

> Seems a sensible option.  Can always put a hwmon driver on top of that
> if people want the nice userspace interfaces etc.

If it's anything like WM8350 you'll end up with multiple things sitting
on top of it.

> That's probably me anyway (industrialio), it's stalled whilst I switch
> my test platform to this driver and isn't really suitable for this 

Ah, yes - so it is.

> (unless someone wants to abuse the auxiliary adc inputs for general
> purpose stuff).

My experience suggests that at least some designs will want to do that
but if you go with the internal-only support with multiple clients they
can always write a driver on top of that if/when they need it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/