* PMIC driver prevents gpio-leds to work
@ 2014-02-18 18:20 Fabio Estevam
2014-02-18 18:43 ` Alexander Shiyan
0 siblings, 1 reply; 5+ messages in thread
From: Fabio Estevam @ 2014-02-18 18:20 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
I am running into the following issue on imx6sl-evk.dts:
- I can only get the user GPIO LED to work if I unselect the PFUZE100
PMIC driver
- This happens on linux-next as well as in the internal FSL kernel based on 3.10
With CONFIG_REGULATOR_PFUZE100=y then the LED blinks only once and
stops instead of blinking at the heartbeat rate.
Changing to CONFIG_REGULATOR_PFUZE100=n then the LED blinks normally.
I am not sure how the PMIC driver could interact and make the
gpio-leds driver to fail.
Any suggestions?
Thanks,
Fabio Estevam
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: PMIC driver prevents gpio-leds to work
2014-02-18 18:20 PMIC driver prevents gpio-leds to work Fabio Estevam
@ 2014-02-18 18:43 ` Alexander Shiyan
2014-02-18 18:59 ` Fabio Estevam
0 siblings, 1 reply; 5+ messages in thread
From: Alexander Shiyan @ 2014-02-18 18:43 UTC (permalink / raw)
To: linux-arm-kernel
???????, 18 ??????? 2014, 15:20 -03:00 ?? Fabio Estevam <festevam@gmail.com>:
> Hi,
>
> I am running into the following issue on imx6sl-evk.dts:
>
> - I can only get the user GPIO LED to work if I unselect the PFUZE100
> PMIC driver
>
> - This happens on linux-next as well as in the internal FSL kernel based on 3.10
>
> With CONFIG_REGULATOR_PFUZE100=y then the LED blinks only once and
> stops instead of blinking at the heartbeat rate.
>
> Changing to CONFIG_REGULATOR_PFUZE100=n then the LED blinks normally.
>
> I am not sure how the PMIC driver could interact and make the
> gpio-leds driver to fail.
>
> Any suggestions?
Perhaps, one of regulators turn off the power for a pin-group where LED is connected.
---
^ permalink raw reply [flat|nested] 5+ messages in thread
* PMIC driver prevents gpio-leds to work
2014-02-18 18:43 ` Alexander Shiyan
@ 2014-02-18 18:59 ` Fabio Estevam
2014-02-19 3:38 ` Mark Brown
0 siblings, 1 reply; 5+ messages in thread
From: Fabio Estevam @ 2014-02-18 18:59 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Feb 18, 2014 at 3:43 PM, Alexander Shiyan <shc_work@mail.ru> wrote:
> ???????, 18 ??????? 2014, 15:20 -03:00 ?? Fabio Estevam <festevam@gmail.com>:
>> Hi,
>>
>> I am running into the following issue on imx6sl-evk.dts:
>>
>> - I can only get the user GPIO LED to work if I unselect the PFUZE100
>> PMIC driver
>>
>> - This happens on linux-next as well as in the internal FSL kernel based on 3.10
>>
>> With CONFIG_REGULATOR_PFUZE100=y then the LED blinks only once and
>> stops instead of blinking at the heartbeat rate.
>>
>> Changing to CONFIG_REGULATOR_PFUZE100=n then the LED blinks normally.
>>
>> I am not sure how the PMIC driver could interact and make the
>> gpio-leds driver to fail.
>>
>> Any suggestions?
>
> Perhaps, one of regulators turn off the power for a pin-group where LED is connected.
That did the trick, thanks.
I thought that 'regulator-always-on' was enough, but I also need
'regulator-boot-on' as well.
Will submit the patch later today.
Thanks,
Fabio Estevam
^ permalink raw reply [flat|nested] 5+ messages in thread
* PMIC driver prevents gpio-leds to work
2014-02-18 18:59 ` Fabio Estevam
@ 2014-02-19 3:38 ` Mark Brown
2014-02-19 11:15 ` Fabio Estevam
0 siblings, 1 reply; 5+ messages in thread
From: Mark Brown @ 2014-02-19 3:38 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Feb 18, 2014 at 03:59:27PM -0300, Fabio Estevam wrote:
> I thought that 'regulator-always-on' was enough, but I also need
> 'regulator-boot-on' as well.
That sounds wrong, like something is forgetting to do an enable at some
point or there's some problem with the enable operation. What's the
actual root cause here? boot-on should really only be needed for
regulators where you can't read the status.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140219/29c12895/attachment.sig>
^ permalink raw reply [flat|nested] 5+ messages in thread
* PMIC driver prevents gpio-leds to work
2014-02-19 3:38 ` Mark Brown
@ 2014-02-19 11:15 ` Fabio Estevam
0 siblings, 0 replies; 5+ messages in thread
From: Fabio Estevam @ 2014-02-19 11:15 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Feb 19, 2014 at 12:38 AM, Mark Brown <broonie@kernel.org> wrote:
> On Tue, Feb 18, 2014 at 03:59:27PM -0300, Fabio Estevam wrote:
>
>> I thought that 'regulator-always-on' was enough, but I also need
>> 'regulator-boot-on' as well.
>
> That sounds wrong, like something is forgetting to do an enable at some
> point or there's some problem with the enable operation. What's the
> actual root cause here? boot-on should really only be needed for
> regulators where you can't read the status.
Thanks for your explanation, Mark.
Sent v2 of the patch.
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-02-19 11:15 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-18 18:20 PMIC driver prevents gpio-leds to work Fabio Estevam
2014-02-18 18:43 ` Alexander Shiyan
2014-02-18 18:59 ` Fabio Estevam
2014-02-19 3:38 ` Mark Brown
2014-02-19 11:15 ` Fabio Estevam
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).