lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 7 Oct 2014 13:30:58 -0700
From:	Doug Anderson <>
To:	Linus Walleij <>
Cc:	Thierry Reding <>,
	Mark Brown <>,
	Lee Jones <>,
	Chris Zhong <>,
	Heiko Stuebner <>,
	Sonny Rao <>,
	"" <>,
	"" <>
Subject: Re: [RFC PATCH] pwm: Add the concept of an "active" pinctrl


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 you: "default", "sleep", "idle".
>> Except it will handle only one state unless "CONFIG_PM" is defined,
>> right?  In other words "sleep" and "idle" totally don't exist in the
>> "!CONFIG_PM" case.
> Yes. Because the intent of these settings is usually to save power.
> So by disabling the PM config, you can test if the system works
> without PM. Even hairy stuff like power-related pin control. It has
> this nice orthogonal debug feature to it...
>> Normally it should be considered "safe" (though high power)
>> to disable CONFIG_PM, right?
> Yeah. If your usecase makes it unsafe to have just "default",
> you should not rely on these state names but invent new ones.

I thought about it a bit more and I decided that a new state made the
most sense.  I put another RFC up there at
<>.  Feel free to have a
look at it.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists