Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] effects of powered-off chip sections on current leakage
Date: Sun, 14 Jun 2020 13:07:54 -0700
Message-ID: <CAC2bXD6bOLp5tS0=Q27RNkP9FpA4xFmrhqv1zJCwTaGd9h1qCQ@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDyOoEPF-bqBSAQug5Wgw1SSTbtSz7-crA1ccRtbM21QJw@mail.gmail.com>

On Sun, Jun 14, 2020, 04:31 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Sun, Jun 14, 2020 at 6:06 AM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > Please explain in more detail, perhaps with some supporting references --
> > it still makes close to zero sense to me how additional unused silicon
> area
> > could affect the rest of the chip, since that area itself couldn't be
> > drawing any power since all wires into it that are at 0V due to the power
> > rails and I/O signals being switched off.
>
> beyond the fact that it occurs, i do not know the details.  i had a
> mentor who explained it to me, and (in the case of the GPS
> correlators) a second person confirmed it.
>
> it is something to do with the fact that a transistor is not a perfect
> isolator, and that it is both a resistor and a capacitor.  the
> resistance, when there is zero power applied to the Drain, is
> extremely small but it is *not* zero, between the two planes that are
>

assuming you meant resistance is extremely large but not infinity.
extremely small means a very large current would flow.

directly above and below the transistor (one VDD - +ve voltage, one
> VSS - GND)
>

from what I understand, the leakage current is mostly caused by a
combination of gate and other insulator defects, quantum tunneling, and
minority carriers. Those basically act as a resistor between the source,
drain, and gate.

If the block is not switching, we can ignore any capacitive effects since
the capacitors won't be charging or discharging.

We will probably want a separate clock and reset domain for each power
domain.


> ok so if there's an actual MOSFET that cuts power to those planes,
> there's nothing to "resist", so the idea that you came up with of
> cutting power entirely has merit that needs a proper investigation.


After a little looking around, I didn't see anything that unambiguously
stated that turning off the power planes will reduce leakage power, however
basically everyone I found seemed to imply that.

https://en.wikipedia.org/wiki/Power_gating

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  reply index

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 13:30 [libre-riscv-dev] [Bug 376] New: Assess 40/45 nm 2022 target and interfaces bugzilla-daemon
2020-06-12 13:31 ` [libre-riscv-dev] [Bug 376] " bugzilla-daemon
2020-06-12 13:52 ` bugzilla-daemon
2020-06-12 15:14 ` bugzilla-daemon
2020-06-12 15:27 ` bugzilla-daemon
2020-06-12 16:17 ` bugzilla-daemon
2020-06-12 16:29 ` bugzilla-daemon
2020-06-12 17:26 ` bugzilla-daemon
2020-06-12 17:34 ` bugzilla-daemon
2020-06-12 17:44 ` bugzilla-daemon
2020-06-12 18:00 ` bugzilla-daemon
2020-06-12 18:01 ` bugzilla-daemon
2020-06-12 18:08 ` bugzilla-daemon
2020-06-12 18:13 ` bugzilla-daemon
2020-06-12 21:51 ` bugzilla-daemon
2020-06-12 21:52 ` bugzilla-daemon
2020-06-12 22:00 ` bugzilla-daemon
2020-06-12 22:05 ` bugzilla-daemon
2020-06-12 22:19 ` bugzilla-daemon
2020-06-12 22:32 ` bugzilla-daemon
2020-06-12 22:55 ` bugzilla-daemon
2020-06-12 23:02 ` bugzilla-daemon
2020-06-12 23:11 ` bugzilla-daemon
2020-06-12 23:14 ` bugzilla-daemon
2020-06-13  0:20 ` bugzilla-daemon
2020-06-14  5:06   ` [libre-riscv-dev] effects of powered-off chip sections on current leakage Jacob Lifshay
2020-06-14 11:30     ` Luke Kenneth Casson Leighton
2020-06-14 20:07       ` Jacob Lifshay [this message]
2020-06-14 22:08         ` Cesar Strauss
2020-06-13  3:37 ` [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces bugzilla-daemon
2020-06-14 17:27 ` bugzilla-daemon

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to='CAC2bXD6bOLp5tS0=Q27RNkP9FpA4xFmrhqv1zJCwTaGd9h1qCQ@mail.gmail.com' \
    --to=programmerjake@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git