X-Git-Url: http://www.pilppa.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=Documentation%2Fgpio.txt;h=b1b9887012478f9b654edaa90bcdd13e72a9f20e;hb=35e8bb5175c1a6ff6253f1a2acb30bfe52a2f500;hp=8a7c45956d2412d69a26f8de991db19ed25a838f;hpb=93a22f8b95756c53e80308820892119c910d2739;p=linux-2.6-omap-h63xx.git

diff --git a/Documentation/gpio.txt b/Documentation/gpio.txt
index 8a7c45956d2..b1b98870124 100644
--- a/Documentation/gpio.txt
+++ b/Documentation/gpio.txt
@@ -240,6 +240,10 @@ signal, or (b) something wrongly believes it's safe to remove drivers
 needed to manage a signal that's in active use.  That is, requesting a
 GPIO can serve as a kind of lock.
 
+Some platforms may also use knowledge about what GPIOs are active for
+power management, such as by powering down unused chip sectors and, more
+easily, gating off unused clocks.
+
 These two calls are optional because not not all current Linux platforms
 offer such functionality in their GPIO support; a valid implementation
 could return success for all gpio_request() calls.  Unlike the other calls,