mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Rabin Vincent <rabin@rab.in>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"lrg@ti.com" <lrg@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: disable supply regulator if it is enabled for boot-on
Date: Tue, 28 Aug 2012 17:50:56 +0530	[thread overview]
Message-ID: <503CB7A8.4050600@nvidia.com> (raw)
In-Reply-To: <20120824233835.GA29178@ubuntu>

On Saturday 25 August 2012 05:10 AM, Rabin Vincent wrote:
> On Fri, Aug 24, 2012 at 11:22:05PM +0530, Laxman Dewangan wrote:
>> I tried to reproduce the issue but could not able to do this.
>> Can you please send me your board/dt files where you are porviding
>> platform data for regulator?
>> This will help me to reproduce the issue.
> Here's a dts patch:
>
Hi Rabin,

I tried to reproduce the lockup issue with the following change but not 
seeing any lockup issue.
I implement enable/disable for fixed regulator and printed the string as 
enable/disable
During registration I got the log as
[    0.349955] Registering the regulator vbat
[    0.354352] vbat: 3300 mV
[    0.357260] Registering the regulator vtest1
[    0.361810] fixed_enable(): Enabling vtest1
[    0.366144] vtest1: 3300 mV
[    0.369177] vtest1: supplied by vbat
::::::::::::::::

and when init_complete() get called then it happened as

[    1.509855] vtest1: disabling
[    1.512813] fixed_disable(): Disabling vtest1
[    1.517158] fixed_disable(): Disabling vbat
[    1.521342] vbat: disabling
[    1.524124] fixed_disable(): Disabling vbat


Also reviewing the change, I am not seeing any call trace where the 
recursive locking happening.

Please help to reproduce/understand the issue.



  reply	other threads:[~2012-08-28 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 10:07 Laxman Dewangan
2012-08-14 11:08 ` Rabin Vincent
2012-08-22  9:45 ` Laxman Dewangan
2012-08-23 14:53   ` Mark Brown
2012-08-23 14:43     ` Laxman Dewangan
2012-08-24 17:52       ` Laxman Dewangan
2012-08-24 23:40         ` Rabin Vincent
2012-08-28 12:20           ` Laxman Dewangan [this message]
2012-08-28 15:52             ` Rabin Vincent
2012-08-24 17:53       ` Laxman Dewangan

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=503CB7A8.4050600@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=rabin@rab.in \
    /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

Powered by JetHome