Linus,
On Tue, Oct 7, 2014 at 6:15 AM, Linus Walleij wrote:
> On Thu, Sep 25, 2014 at 10:26 PM, Doug Anderson wrote:
>> On Thu, Sep 25, 2014 at 12:31 AM, Linus Walleij
>> wrote:
>>> On Wed, Sep 24, 2014 at 1:17 AM, Doug Anderson
>>> wrote:
>
>>> The device core will handle three states for yo
On Thu, Sep 25, 2014 at 10:26 PM, Doug Anderson wrote:
> On Thu, Sep 25, 2014 at 12:31 AM, Linus Walleij
> wrote:
>> On Wed, Sep 24, 2014 at 1:17 AM, Doug Anderson wrote:
>> The device core will handle three states for you: "default", "sleep", "idle".
>
> Except it will handle only one state un
Linus,
On Thu, Sep 25, 2014 at 12:31 AM, Linus Walleij
wrote:
> On Wed, Sep 24, 2014 at 1:17 AM, Doug Anderson wrote:
>
>> There are cases where you really don't want a PWM's pinctrl to take
>> effect until you know that the PWM is driving at the proper rate. A
>> good example of this is a PWM-
On Wed, Sep 24, 2014 at 1:17 AM, Doug Anderson wrote:
> There are cases where you really don't want a PWM's pinctrl to take
> effect until you know that the PWM is driving at the proper rate. A
> good example of this is a PWM-controlled regulator, where the boot
> state of the pin (maybe a pulle
There are cases where you really don't want a PWM's pinctrl to take
effect until you know that the PWM is driving at the proper rate. A
good example of this is a PWM-controlled regulator, where the boot
state of the pin (maybe a pulled down input) could cause a vastly
different voltage to take eff
5 matches
Mail list logo