linux-kernel - Re: [RFC] pinctrl: pinctrl-imx: implement suspend/resume

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <CACRpkdYoAZyP5AHeOjksdSVN9H+crOse2syDTSOb_Mh7NyMbhQ@mail.gmail.com>
Date:	Wed, 10 Jun 2015 09:48:21 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Stefan Agner <stefan@...er.ch>
Cc:	Zhi Li <lznuaa@...il.com>, Shawn Guo <shawn.guo@...escale.com>,
	Sascha Hauer <kernel@...gutronix.de>,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>,
	kernel list <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC] pinctrl: pinctrl-imx: implement suspend/resume

On Thu, Jun 4, 2015 at 10:24 PM, Stefan Agner <stefan@...er.ch> wrote:

> I actually tried to experiment with pinctrl_pm_select_default_state and
> pinctrl_pm_select_sleep_state. I think, one solution would be to create
> sleep states for all drivers. However, it's not necessary to change to a
> sleep state, since the controller looses the state anyway. What would be
> required is having a function which allows to force the default state
> for all pinctrl settings... As far as I can tell, there is no such
> functionality currently...? Linus?

You could do it that way, but it requires that the driver depends
on CONFIG_PM as the states are not cached in the driver
core otherwise (drivers/base/pinctrl.c).

I have no strong opinion on the subject really... either way works.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/