LKML Archive on
help / color / mirror / Atom feed
From: David Brownell <>
To: Andrew Morton <>
Cc: lkml <>, Russell King <>
Subject: Re: [patch 2.6.25-rc5] kerneldoc for <linux/clk.h>
Date: Wed, 12 Mar 2008 14:58:37 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Proof-reading doesn't always cut it ... an editor could help!

Signed-off-by: David Brownell <>
Just editorial fixes to the $SUBJECT patch.

 Documentation/DocBook/kernel-api.tmpl |   13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

--- g26.orig/Documentation/DocBook/kernel-api.tmpl	2008-03-12 00:43:43.000000000 -0700
+++ g26/Documentation/DocBook/kernel-api.tmpl	2008-03-12 15:41:48.000000000 -0700
@@ -671,16 +671,15 @@ X!Idrivers/video/console/fonts.c
 	Power management is supported by explicit software clock gating:
 	unused clocks are disabled, so the system doesn't waste power
 	changing the state of transistors that aren't in active use.
-	On some systems this may be backed by hardware clock gating.
-	Circuits will still have leakage current to be managed, which
-	costs more with finer cicuit geometries, but for CMOS circuits
-	power is mostly spent by clocked state changes.
+	On some systems this may be backed by hardware clock gating,
+	where clocks are gated without being disabled in software.
 	Sections of chips that are powered but not clocked may be able
 	to retain their last state.
 	This low power state is often called a <emphasis>retention
-	mode</emphasis>, in contrast to <emphasis>off</emphasis> where
-	power is cut and no state is retained but where leakage currents
-	may have a significant impact on battery life.
+	mode</emphasis>.
+	This mode still incurs leakage currents, especially with finer
+	circuit geometries, but for CMOS circuits power is mostly used
+	by clocked state changes.

      reply	other threads:[~2008-03-12 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11  2:02 David Brownell
2008-03-12 22:58 ` David Brownell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [patch 2.6.25-rc5] kerneldoc for <linux/clk.h>' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).