| 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
| ||
|
Message-ID: <CACRpkdYLSVkfAxVBMBnkyePujaoQQqB27UiG+-r2APkEDrfLrA@mail.gmail.com> Date: Wed, 3 Apr 2013 16:09:09 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Stephen Warren <swarren@...dotorg.org> Cc: Bibek Basu <bbasu@...dia.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Pritesh Raithatha <praithatha@...dia.com> Subject: Re: [PATCH] pinctrl: tegra: add suspend-resume support On Thu, Mar 28, 2013 at 6:48 PM, Stephen Warren <swarren@...dotorg.org> wrote: > Why can't we just use the device suspend/resume functions rather than > global (syscore) suspend/resume functions? Presumably this is to ensure > that all other drivers suspend first, then the pinctrl driver does, and > the reverse for resume. Can't we rely on deferred probe to ensure that > instead? > > To make that work, we might need every affected driver to define a dummy > pinmux state in DT that references the pinctrl driver, to make sure they > all get probed after the pinctrl driver. Hm that reminds me of that policy change I suggested a while back to do this instead of using hogs where possible. It has the nice side-effect that when we inspect the debugfs info all pins will be properly owned by respective consuming device. 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/
Powered by blists - more mailing lists