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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
