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: <20100812204811.GA31315@huya.qualcomm.com>
Date:	Thu, 12 Aug 2010 13:48:11 -0700
From:	David Brown <davidb@...eaurora.org>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Gregory Bean <gbean@...eaurora.org>, linux-arm-msm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	tsoni@...lcomm.com
Subject: Re: [RFC] the right way to use gpiolib hooks to automate power
 management?

On Thu, Aug 12, 2010 at 07:27:44PM +0100, Russell King - ARM Linux wrote:
> On Thu, Aug 12, 2010 at 09:39:29AM -0700, Gregory Bean wrote:
> > We have a written a software driver which reference-counts these gpio
> > lines (via a put()/get() api), putting them in their "high-power" active
> > configurations when they're in use, and dropping them down into a
> > high-impedance low-power setting when they're not.
> 
> Beware.  What you're suggesting can lead to an increase in power
> consumption rather than the reduction you're looking for.

That probably just got a little obscured, since I think Greg is more
concerned with the mechanism in software.  Our gpio's are generally
configured in "low power" to be high-impedance with a pull-up or
pull-down, depending on what it is hooked to.  They can be configured
in most of the ways that would make sense to do so.

It may be the case, though, that what this "low power" mode is might
need to also be configurable, since it likely depends on how the pin
is connected.

David
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ