All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Lin <axel.lin@gmail.com>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Shreshtha Kumar Sahu <shreshthakumar.sahu@stericsson.com>,
	Richard Purdie <rpurdie@rpsys.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Girdwood, Liam" <lrg@ti.com>
Subject: Re: [PATCH] leds: lm3530: fix handling of already enabled regulators
Date: Tue, 24 Apr 2012 20:35:09 +0800	[thread overview]
Message-ID: <CAF+7xWnf6QMg5QeXyoRJH76xjprGW7B3pMXeS-f=uiwPdsMoLQ@mail.gmail.com> (raw)
In-Reply-To: <DD6B9D658496A2488636C8C75B9C0CB601DA3AF6@EXMAIL04.scwf.nsc.com>

> Could you explain what 'enabled on boot' means ?
> 1) The regulator_enable() is called in initial time
> or
> 2) boot_on = 1 in regulator_init_data ?
>
> If you mean 'boot_on = 1' in regulator_init_data, then no use_count increase.

I mean boot_on = 1 in regulator_init_data.

I just checked the regulator core, and you are right that
no use_count increase if boot_on = 1 in this case.

use_count will be increased if boot_on = 1 && using regulator_get_exclusive.

Regards,
Axel

      reply	other threads:[~2012-04-24 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 15:11 [PATCH] leds: lm3530: fix handling of already enabled regulators Axel Lin
2012-04-23 11:09 ` Mark Brown
2012-04-24  2:09   ` Axel Lin
2012-04-24  6:27     ` Kim, Milo
2012-04-24  8:48       ` Axel Lin
2012-04-24 10:15         ` Kim, Milo
2012-04-24 12:35           ` Axel Lin [this message]

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='CAF+7xWnf6QMg5QeXyoRJH76xjprGW7B3pMXeS-f=uiwPdsMoLQ@mail.gmail.com' \
    --to=axel.lin@gmail.com \
    --cc=Milo.Kim@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=rpurdie@rpsys.net \
    --cc=shreshthakumar.sahu@stericsson.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.