devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Huang <bilhuang@nvidia.com>
To: Nishanth Menon <nm@ti.com>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"pawel.moll@arm.com" <pawel.moll@arm.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
	"rob@landley.net" <rob@landley.net>,
	"lee.jones@linaro.org" <lee.jones@linaro.org>,
	"broonie@linaro.org" <broonie@linaro.org>,
	"j-keerthy@ti.com" <j-keerthy@ti.com>,
	"grant.likely@linaro.org" <grant.likely@linaro.org>,
	"ian@slimlogic.co.uk" <ian@slimlogic.co.uk>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mallikarjun Kasoju <mkasoju@nvidia.com>
Subject: Re: [PATCH 1/1] mfd: palmas: Add power off control
Date: Tue, 30 Jul 2013 23:22:47 -0700	[thread overview]
Message-ID: <1375251767.32701.5.camel@bilhuang-vm1> (raw)
In-Reply-To: <51F7BCEC.9080803@ti.com>

On Tue, 2013-07-30 at 21:17 +0800, Nishanth Menon wrote:
> On 07/30/2013 07:05 AM, Bill Huang wrote:
> > Hook up "pm_power_off" to palmas power off routine if there is DT
> > property "ti,system-power-controller" defined, so platform which is
> > powered by this regulator can be powered off properly.
> >
> > Based on work by:
> > Mallikarjun Kasoju <mkasoju@nvidia.com>
> >
> > Signed-off-by: Bill Huang <bilhuang@nvidia.com>
> > cc: Mallikarjun Kasoju <mkasoju@nvidia.com>
> > ---
> >   .../devicetree/bindings/regulator/palmas-pmic.txt  |    5 +++++
> >   drivers/mfd/palmas.c                               |   23 ++++++++++++++++++--
> >   include/linux/mfd/palmas.h                         |    1 +
> any reason why it wont fit in drivers/power/reset/ is'nt it the right 
> place to add this?
> >   3 files changed, 27 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/regulator/palmas-pmic.txt b/Documentation/devicetree/bindings/regulator/palmas-pmic.txt
> > index 30b0581..4adca2a 100644
> > --- a/Documentation/devicetree/bindings/regulator/palmas-pmic.txt
> > +++ b/Documentation/devicetree/bindings/regulator/palmas-pmic.txt
> > @@ -36,6 +36,9 @@ Optional nodes:
> >   	       ti,smps-range - OTP has the wrong range set for the hardware so override
> >   	       0 - low range, 1 - high range.
> >
> > +- ti,system-power-controller: Telling whether or not this pmic is controlling
> controller or master?

We name it controller since it controls the system power of the
platform, I'm not sure will it make more sense to be master? Or does it
makes sense to other pmic which also control the system power (the same
property are already used in pmic TPS6586x and TPS65910).

> > +			      the system power.
> > +
> >   Example:
> >
> >   #include <dt-bindings/interrupt-controller/irq.h>
> > @@ -48,6 +51,8 @@ pmic {
> >
> >   	ti,ldo6-vibrator;
> >
> > +	ti,system-power-controller;
> > +
> >   	regulators {
> >   		smps12_reg : smps12 {
> >   			regulator-name = "smps12";
> > diff --git a/drivers/mfd/palmas.c b/drivers/mfd/palmas.c
> > index e4d1c70..0662b21 100644
> > --- a/drivers/mfd/palmas.c
> > +++ b/drivers/mfd/palmas.c
> > @@ -229,6 +229,22 @@ static void palmas_dt_to_pdata(struct i2c_client *i2c,
> >   					PALMAS_POWER_CTRL_ENABLE2_MASK;
> >   	if (i2c->irq)
> >   		palmas_set_pdata_irq_flag(i2c, pdata);
> > +
> > +	pdata->pm_off = of_property_read_bool(node,
> > +			"ti,system-power-controller");
> > +}
> > +
> > +static struct palmas *palmas_dev;
> > +static void palmas_power_off(void)
> > +{
> > +	unsigned int addr;
> > +
> > +	if (!palmas_dev)
> > +		return;
> > +
> > +	addr = PALMAS_BASE_TO_REG(PALMAS_PMU_CONTROL_BASE, PALMAS_DEV_CTRL);
> > +
> > +	regmap_update_bits(palmas_dev->regmap[0], addr, 1, 0);
> slave = PALMAS_BASE_TO_SLAVE(base);
> addr = PALMAS_BASE_TO_REG(base, reg);
> 
> r = regmap_update_bits(palmas->regmap[slave], addr, mask, val);
> instead?
> 
> just for reference, an old implementation I had done is available at [1]
> 
Thanks, I'll send out v2.
> 
> [1] 
> http://git.omapzoom.org/?p=kernel/omap.git;a=blob;f=drivers/mfd/palmas-poweroff.c;hb=p-linux-omap-3.4
> 



  reply	other threads:[~2013-07-31  6:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 12:05 [PATCH 1/1] mfd: palmas: Add power off control Bill Huang
2013-07-30 13:17 ` Nishanth Menon
2013-07-31  6:22   ` Bill Huang [this message]
2013-07-31 11:58     ` Nishanth Menon
2013-07-31 17:16     ` Stephen Warren
2013-07-31  9:56 ` Lee Jones
2013-07-31 10:49   ` Bill Huang
2013-07-31 17:17   ` Stephen Warren
2013-08-01  8:47     ` Lee Jones
2013-08-01 16:13       ` Stephen Warren

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=1375251767.32701.5.camel@bilhuang-vm1 \
    --to=bilhuang@nvidia.com \
    --cc=broonie@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=ian@slimlogic.co.uk \
    --cc=j-keerthy@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mkasoju@nvidia.com \
    --cc=nm@ti.com \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=sameo@linux.intel.com \
    --cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).