Medfield: Intel in a Smartphone

I touched on this before but there were a number of reasons we never saw Moorestown in a smartphone. One part of the problem was the number of packages required to implement the platform, the other was that it simply lacked some of the things that smartphone OEMs implicitly expect to live on an SoC. The internal Intel guidance was that Moorestown required 2 packages to implement (Lincroft and Langwell), and in addition to those two you needed an external PMIC and DRAM. There wasn’t support for PoP memory, only external LPDDR1, and there was only support for 5 MP camera and 720p encode.

Medfield builds in every way on top of this by delivering a bona fide SoC with PoP LPDDR2 (2 x 32 bit support), improved ISP from Intel’s Silicon Hive acquisition, video encode and decode blocks from Imagination, SGX 540 graphics at 400 MHz, additional I/O, and an external Avatele Passage PMIC (Intel calls this an MSIC). The result is a platform that looks to an OEM like any of the other competitors - it’s a combination of SoC, PMIC, and some PoP LPDDR2, as opposed to the previous solution which required two additional external packages. Intel has a few slides online about this evolution and how things have moved inside the single Medfield package, and the result again is something that finally looks like any one of countless ARM-based SoCs.

The specific part inside the X900 is an Atom Z2460 32nm SoC (the platform is Medfield, Penwell is the SoC, and the CPU inside is a Saltwell), and inside a Penwell is the Atom Saltwell core running at up to 1.6 GHz with 512KB of L2 cache, a PowerVR SGX 540 GPU at 400 MHz, and a dual channel LPDDR2 memory interface. Anand has already written about the CPU architecture itself pretty comprehensively, and how it compares to ARM’s Cortex A9 and A15 designs. The long and short of it is that Saltwell is still a dual-issue, in-order core with Hyper-Threading support. There’s a 16 stage integer pipeline, no dedicated integer multiply or divide units (they’re shared with the floating point hardware), and in addition to the 512KB L2 cache there’s a separate 256KB SRAM which is lower power and on its own voltage plane. When Saltwell goes into its deepest sleep state, the CPU state and some L2 cache data gets parked here, allowing the CPU voltage to be lowered even more than the SRAM voltage. As expected, with Hyper-Threading the OS sees two logical cores to execute tasks on.

The other interesting thing is support for EIST and additional C states when the device is idle. Dynamic CPU clocks through the linux governor is something absolutely critical for getting a smartphone with acceptable battery life. What’s interesting here is that Penwell’s advertised dynamic range is between 100 MHz and 1.6 GHz with fine grained 100 MHz increments between, in addition to the C6 state where CPU state data is saved in the on-SoC low power SRAM and the platform is basically suspended (deep sleep).

However, the Android governor onboard the X900 only includes a few steps between 600 MHz and the maximum 1.6 GHz burst clock, in addition to C6. You can see this either by inspecting the governor’s available scaling frequencies:

$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1600000 1400000 1200000 900000 600000 
$ cat time_in_state
1600000 233495
1400000 12304
1200000 19780
900000 25801
600000 5306262

Or by using an Android application which inspects exactly this data. I spent a day with the Medfield phone in my pocket and made a note of capturing what the state data was after the day’s end, and the CPU does indeed go into C6 while idle and in the pocket, and spend a lot of time at the minimum 600 MHz clock with some bursts to 1.6 GHz when I’m doing things.

 

The reality is that most of the smartphone’s time is really spent idling, waking up only to watch some DRX slots or process background tasks. It is curious to me however that Intel isn’t implementing their Ultra-LFM modes between 100 and 600 MHz - it’s possible there’s no voltage scaling below 600 MHz which in turn doesn’t make it worth jumping into these lower clocks quite yet.

Depending on the device’s thermals, Intel’s governor will select between those available frequencies. There actually are four thermal zones in the device, on the back, front, baseband, and SoC itself. The SoC can go up to 90C before you get throttled (which is pretty typical for Intel CPUs), 75 C on the back, 64 C on the front, and 80 C on the modem. Those sound high but aren’t out of the ordinary for some of the other SoCs I’ve seen who have similar thermal management. In addition, if the platform gets too hot, the display brightness will be clamped to 50%.

I have to admit that I did see the display brightness get clamped once as shown above, but only once during a period where I was running the display at 100% brightness and maxing out the CPU. The bottom back of the X900 can indeed get warm, but nothing inordinate or near the thermals that are set in the software management.

Finally, Saltwell supports the same instruction set as Core 2, including SSE3 and Intel 64. We can check this by looking at the CPU flags from cpu_info as well:

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 39
model name : Intel(R) Atom(TM) CPU Z2460  @ 1.60GHz
stepping : 2
cpu MHz : 600.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 xtpr pdcm movbe lahf_lm arat tpr_shadow vnmi flexpriority
bogomips : 3194.88
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 32 bits virtual
power management:

The rest of the Medfield platform we’ll talk about in the appropriate sections, but the big takeaway is that Intel finally has a real x86 SoC for smartphones and tablets. In addition to the Z2460 that we’re looking at in the X900, Intel has two other SKUs which round out the high end and low end. At the low end is the Z2000 which is functionally identical to the Z2460 but with a maximum CPU clock of 1.0 GHz, no HT, and an SGX 540 clock of 320 MHz, and the Z2580 which is clearly targeted at Windows 8 tablets with two Saltwell cores clocked up to 1.8 GHz, and PowerVR SGX544MP2 graphics at 533 MHz for Direct3D 9_3 compliance.

The Road to Medfield, and The Device Android on x86 and Binary Translation
Comments Locked

106 Comments

View All Comments

  • jed22281 - Thursday, April 26, 2012 - link

    Vanilla MeeGo is nothing like MeeGo-Harmattan (aka Maemo6x) on the N9...
    The only relation Tizen has with Vanilla MeeGo, is that it's structured/administered in a similar fashion.
    Plus many of the same partners involved in MeeGo, have moved to Tizen...
    The developmental libraries/environment is totally different, although there's still some tacit support for Qt.
    MeR+Nemo (& other UX's e.g. Cordia/Plasma etc) is what has supplanted the original MeeGo.
    And yes you could in theory run MeR+Nemo or Tizen on this or other Medfied devices.
    But I'm not so sure they'd necessarily be any less locked down than ARM-based ones.
    Locked boot loader etc... But once that's out of the way, they'd have their advantages.
  • ironargonaut - Wednesday, April 25, 2012 - link

    From what I see the only phones that best Intel in performance are not on the battery chart.

    If a phone computes something faster, will that not mean it can do more in less time? Thus, while the artificial surfing battery time is "average", wouldn't I be able to surf more pages and run more apps also in that same time period?

    What is the power/performance metric?
  • fm123 - Thursday, April 26, 2012 - link

    There is no clear way to tell from this, given that the CPU is likely ramping up and down. The other phones are not listed, I suspect, as they are new. They actually include newer battery saving features, so you can't see that yet on this comparison.
  • ironargonaut - Thursday, April 26, 2012 - link

    So,then could I safely say, that since battery life is not listed here, of the phones in both tests Intel has the highest cpu performance with midrange battery life.

    If they are not going to test the batteries of the same phones then you shouldn't have them listed on the same graph for CPU power. IMHO

    It's like a Ford commercial saying Ford fullsize has better gas mileage then Chevy, more towing power than Dodge, more cargo space then Toyota etc..

    Which if written the way of this article is more like Ford worse gas mileage than Dodge, less towing power than Toyota, less cargo space then Chevy etc...

    All are misleading. IMHO
  • mcquade181 - Wednesday, April 25, 2012 - link

    For the benefit of all us older technophiles with slightly less than perfect hearing, could you please, please test the earpiece volume when testing cellular phones?

    I had to ditch my otherwise great Nokia N8 because of its ridiculously low earpiece volume, which made it unusable in anything but perfectly quiet environments.

    The other very useful test would be how well the phone operates in both voice and data modes in areas at the fringe of network coverage, i.e. the phone’s range. The Samsung Galaxy S2 does not fare that well in this test and is no where near as good as my old Nokia N8. Surprisingly, very, very few reviews of the Galaxy S2 mention how average its fringe reception is.
  • cmdrdredd - Wednesday, April 25, 2012 - link

    To not include any iphone results to the GLbenchmark except offscreen since offscreen looks so great on the iphone and the results I've obtained from around the web when running on the phone's screen show it not to be that much better than the fastest Android devices. How many people ac tually do GPU functions that aren't running on the phone's screen? Not many...
  • suman - Wednesday, April 25, 2012 - link

    While BT is very cool technology, why is there so much hoopla around it. We released the Bluestacks App Player (beta) a month ago and have a binary translator embedded in it. We can run ARM NDK, X86 NDK, Dalvik applications side by side on our player.
  • iamastranger - Thursday, April 26, 2012 - link

    Basically all are missing a point here. It is a FFRD with miimal changes done by LAVA. Wait for a OEM like Moto deliver x86 based phone.
  • danielt - Thursday, April 26, 2012 - link

    Hoe come this site never review the amazing Galaxy Note?
  • RajeevRaj - Thursday, April 26, 2012 - link

    One aspect not touched upon here is the price of the XOLO as compared to the other smartphones in the compare list. The XOLO costs INR 22000 ($420). Most other phones in the list (which are available in India) cost upwards of INR 27-28000 (>$520). As example the Samsung Galaxy S2 costs INR 28-30,000 ($550) and iPhones cost upward of INR 35000. (>$700)

    So if you factor in a price to features ratio also in the comparisons, the XOLO looks very attractive for a smartphone buyer in India.

Log in

Don't have an account? Sign up now