Power Gating

Until the Atom Z600 series, the only Intel CPUs to power gate were the Nehalem/Westmere derived chips. In Moorestown, everything is both power and clock gated.

The CPU itself has its usual power states; C0 implies full power, full performance, and C6 is a deep sleep state where power is shut off to the entire CPU and state is saved in a small amount of active SRAM. There’s finer grained clock and power gating in Lincroft than in Intel’s Core i7.

Moorestown is a SoC platform however, so we need some new power states. Intel calls them S0i1 and S0i3. As with CPU power states, the higher the number, the more that’s shut off.

Virtually all blocks in Lincroft and Langwell are clock and power gated. In S0i1, everything from the CPU and GPU to interconnects are power gated. From the sounds of it, S0i1 is where you’d find your smartphone if you just left it on the table for a few seconds. The display would shut off and all internal components would be power gated. Pick it back up, hit a button and you get pretty quick recovery.

S0i3 however completely powers down virtually all components and keeps a small amount of SRAM active with state data. This is the phone locked and in your pocket state.

Getting out of these power states is relatively quick. S0i3 takes around 3ms while S0i1 takes 1ms.

The impact of these idle states is huge. On a reference Moorestown platform (this includes the Moorestown chips, display, 3G radio, basically a fully functional phone), Intel measured total platform power in S0i3 at 21 - 23mW. That’s a ~50x reduction compared to Menlow, and that’s what makes Moorestown suitable for use in a smartphone.

Power Management: Clock Down or Turbo Up OS Driven Power Management
Comments Locked

67 Comments

View All Comments

  • teohhanhui - Thursday, May 6, 2010 - link

    But they'll be showcasing it on their Moblin/Meego which is Linux. Won't shoot themselves in the feet, will they?
  • rahvin - Thursday, May 6, 2010 - link

    And if it only runs on Moblin, only with specific kernel versions, uses a binary blob driver and isn't maintained it will be the same story as GMA500 all over again.
  • strikeback03 - Thursday, May 6, 2010 - link

    As pointed out, plenty of other Android phones are using the same graphics. And I haven't heard a lot of complaints about lack of drivers for the Droid/N1/etc.
  • elisha.pan - Wednesday, May 5, 2010 - link

    GMA500 has nothing with the Intel GMA series, but name. It is exactly the same with PowerVR SGX 535.
  • DanNeely - Wednesday, May 5, 2010 - link

    This is the same GPU used in almost every other smart phone on the market, except that it's designed to be clocked up to twice as fast. It's not going to run Crysis *rolls eyes* but it's more than capable of doing everything a smart phone/internet tablet will need to do.
  • ekul - Wednesday, May 5, 2010 - link

    exactly. without open source drivers for the graphic any development of meego outside of intel will never go anywhere. One of the reasons I bought my current netbook is the gma 950 has excellent open source drivers that just work.

    Open source development moves fast. Closed source binaries get left behind because they can't keep up with the release schedule. The current gma 500 drivers already need a kernel several versions old as well as an old X server. How many releases is meego going to miss?
  • ViRGE - Wednesday, May 5, 2010 - link

    I can see why Anand thinks it's an interesting product, but based on his article I don't think Intel is quite there.

    The current need for 5 chips is going to be a problem no matter how Intel dresses things up, and if all phones end up looking like the design shown I wouldn't be surprised if the consumer reaction was tepid - a phone of that size is still pretty big. The video playback time is also going to be a problem when it comes to spec sheets (I doubt the real-world impact will be as huge), but OEMs like their spec sheets and consumers aren't too far off either. Just looking like it'll perform poorly there may be enough.

    The other issue is the reliance on an OS. At this point it seems like no one really wants another OS. Most people around here seemed to be more relieved than concerned when Palm went under. With BlackBerryOS, IPhoneOS, Android, and WinCE, there seems to be as many OSes as the market can reasonably handle. Moblin/MeeGo may be necessary for the hardware right now, but I see no reason to expect that it's going to be properly developed for consumer use like the above OSes were. Unless Intel can land RIM/Apple, they need to get Android up to par on Moorestown and they need to do it yesterday.

    Ultimately I think it's going to Medfield that's a proper ARM competitor. With fewer chips it will fit in to traditional designs, and with any luck Intel will be a node ahead of its competition on the manufacturing process. It won't solve the current OS reliance, but it'll put them in a better position than Moorestown does.
  • ET - Wednesday, May 5, 2010 - link

    Ultimately I think that most people don't care about the OS. The OS mainly matters in terms of applications available for it, and it's a pain for developers to address many OS's, but also an opportunity for new developers to carve their niche.

    That said, Anand did mention that Intel is making Android available for this new platform, which should be good enough.
  • IntelUser2000 - Wednesday, May 5, 2010 - link

    It's much closer than expected. There were quite frequent comments that thought it wouldn't even reach 5 hour on standby! Having a lot of knowledge and doing a bit research helps of course. Glad they can be roughly on par though.

    It's likely the idle power can't be achieved without optimized OSes. Even if you can run Windows on it, what's the point when you won't have the battery life for it? Windows uses too much on keeping legacy support and its too bloated for idle power under 50mW.

    Platform approach is the key to low power on Moorestown.
  • piroroadkill - Wednesday, May 5, 2010 - link

    I'm not sold. ARM has been more efficient for a lot longer, even though it's still being made on commonly larger processes than current Intel CPUs. All smartphones are ARM anyhow, so I don't see the advantage in having x86 in this space

Log in

Don't have an account? Sign up now