| 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
| ||
|
Date: Tue, 20 Jan 2009 12:43:41 +0000 From: Mark Brown <broonie@...ena.org.uk> To: Jonathan Cameron <jic23@....ac.uk> Cc: LKML <linux-kernel@...r.kernel.org>, Liam Girdwood <lrg@...nel.org> Subject: Re: regulator: Add always off to constraints. On Tue, Jan 20, 2009 at 12:07:05PM +0000, Jonathan Cameron wrote: > 1) interaction between always on and always off. Obviously it's > a bit odd if both are set. Currently I'm giving always on preference. I'd just complain loudly and refuse to accept the constraints if they are clearly broken like that. One thing I would suggest is a slightly weaker version which marks the regulator to be turned off at boot rather than always off. That's slightly more flexible and would achieve the same effect if the constraints don't otherwise allow for turning the regulator on layer. > 2) Doesn't really make sense to have regulators that are always > disabled available under sysfs etc. Perhaps there is a lower > level way of doing this that I'm missing? There is not easy > way of permanently saving this stuff on the da9030 that I'm > using and moving it into the bootloader would be a pain. It doesn't do *that* much harm - if nothing else it makes it more discoverable what's happening. -- 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