linux-kernel - Re: [PATCHv4 1/4] MFD: TPS65910: Add new mfd device for TPS65910

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]

Date:	Tue, 26 Apr 2011 16:28:11 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Liam Girdwood <lrg@...com>
Cc:	Jorge Eduardo Candelaria <jedu@...mlogic.co.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"broonie@...nsource.wolfsonmicro.com" 
	<broonie@...nsource.wolfsonmicro.com>,
	Graeme Gregory <gg@...mlogic.co.uk>
Subject: Re: [PATCHv4 1/4] MFD: TPS65910: Add new mfd device for TPS65910

Hi Liam,

On Tue, Apr 26, 2011 at 03:02:45PM +0100, Liam Girdwood wrote:
> On 26/04/11 15:00, Samuel Ortiz wrote:
> > Hi Jorge,
> > 
> > On Thu, Apr 21, 2011 at 09:35:43AM -0500, Jorge Eduardo Candelaria wrote:
> >> From: Graeme Gregory <gg@...mlogic.co.uk>
> >>
> >> The TPS65910 chip is a power management IC for multimedia and handheld
> >> devices. It contains the following components:
> > The patch looks mostly good to me.
> > You may want to add a locked tps65910_set|clear_bits() API, since it seems
> > you're doing many read(reg), write(reg) sequences in the GPIO driver. That
> > could also be directly used by the regulator one.
> > 
> 
> Samuel, I could all take this series via regulator after the fixes if that's OK with you ?
> 
That's fine, no problem.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/