public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: eduardo.valentin@nokia.com
Cc: ext Anuj Aggarwal <anuj.aggarwal@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCHv2 1/4] Regulator: OMAP: Creating TWL4030 file having supplies & init data
Date: Fri, 05 Feb 2010 10:09:28 +0000	[thread overview]
Message-ID: <1265364568.3177.3.camel@odin> (raw)
In-Reply-To: <20100205084501.GA30421@esdhcp037198.research.nokia.com>

On Fri, 2010-02-05 at 10:45 +0200, Eduardo Valentin wrote:
> Hello Anuj,
> 
> First of all, I liked the idea of unifying the regulator definitions
> for boards that use twl regulators.
> 
> But I guess we need to improve a little bit.
> 
> See following comments.
> 
> On Tue, Jan 12, 2010 at 10:13:52AM +0100, ext Anuj Aggarwal wrote:
> > A new file for TWL4030/TPS65950 is created which has common supplies
> > and regulator init data structures. They will be referenced from the
> > various board-evm files depending upon the EVM requirements, using
> > the twl4030-pmic.h header file.
> > 
> > Signed-off-by: Anuj Aggarwal <anuj.aggarwal@ti.com>
> > ---
> >  arch/arm/mach-omap2/twl4030-pmic.c |  175 ++++++++++++++++++++++++++++++++++++
> >  arch/arm/mach-omap2/twl4030-pmic.h |   34 +++++++
> >  2 files changed, 209 insertions(+), 0 deletions(-)
> >  create mode 100644 arch/arm/mach-omap2/twl4030-pmic.c
> >  create mode 100644 arch/arm/mach-omap2/twl4030-pmic.h
> > 
> > diff --git a/arch/arm/mach-omap2/twl4030-pmic.c b/arch/arm/mach-omap2/twl4030-pmic.c
> > new file mode 100644
> > index 0000000..0c0a860
> > --- /dev/null
> > +++ b/arch/arm/mach-omap2/twl4030-pmic.c
> > @@ -0,0 +1,175 @@
> > +/*
> > + * twl4030-pmic.c
> > + *
> > + * Common regulator supplies and init data structs for TWL4030/TPS65950
> > + * PMIC for OMAP3 based EVMs. They can be used in various board-evm
> > + * files for OMAP3 based platforms using TWL4030.
> > + *
> > + * Copyright (C) 2010 Texas Instrument Incorporated - http://www.ti.com/
> > + *
> > + * This program is free software; you can redistribute it and/or
> > + * modify it under the terms of the GNU General Public License as
> > + * published by the Free Software Foundation version 2.
> > + *
> > + * This program is distributed "as is" WITHOUT ANY WARRANTY of any kind,
> > + * whether express or implied; without even the implied warranty of
> > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
> > + * General Public License for more details.
> > + */
> > +
> > +#include <linux/regulator/machine.h>
> > +
> > +/* VDAC */
> > +struct regulator_consumer_supply twl4030_vdac_supply = {
> > +	.supply	= "vdac",
> > +};
> > +
> > +/* VMMC1 */
> > +struct regulator_consumer_supply twl4030_vmmc1_supply = {
> > +	.supply	= "vmmc",
> > +};
> > +
> > +/* VMMC2 */
> > +struct regulator_consumer_supply twl4030_vmmc2_supply = {
> > +	.supply	= "vmmc",
> > +};
> > +
> > +/* VSIM */
> > +struct regulator_consumer_supply twl4030_vsim_supply = {
> > +	.supply	= "vmmc_aux",
> > +};
> > +
> > +/* VPLL2 for digital video outputs */
> > +struct regulator_consumer_supply twl4030_vpll2_supply = {
> > +	.supply	= "vdvi",
> > +};
> 
> 
> Ohh no! This is not good! Defining here the supply list would make things harder.
> Because from board to board the supply list will change! That's the
> whole point of having the supply list. We can't share them for all boards
> definitions.

OK, my understanding here was that this change was only to support a set
of similar OMAP + TWL4030 boards and not *all* OMAP + TWL4030 boards.

Anuj, what were your intentions here ?

Thanks

Liam

-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk


  reply	other threads:[~2010-02-05 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12  9:13 [PATCHv2 1/4] Regulator: OMAP: Creating TWL4030 file having supplies & init data Anuj Aggarwal
2010-02-05  1:39 ` Tony Lindgren
2010-03-02 10:49   ` Aggarwal, Anuj
2010-02-05  8:45 ` Eduardo Valentin
2010-02-05 10:09   ` Liam Girdwood [this message]
2010-02-05 10:23     ` Eduardo Valentin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1265364568.3177.3.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=anuj.aggarwal@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=eduardo.valentin@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox