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

  • vol7ron - Wednesday, April 25, 2012 - link

    I doubt windows would expect PCI channels lol. Though, it might need drivers to operate.

    Everything you need is on the phone for windows to operate (Screen, CPU, Video, RAM and Disk space) exists, even though Windows doesn't require it all. Though, Windows does need some way to communicate with those devices (device drivers), which Win7/etc probably doesn't have.
  • Shadowmaster625 - Wednesday, April 25, 2012 - link

    A few years from now it is likely I might be able to acquire one of these for dirt cheap. (Broken screen, etc) I would use it just for an ultra low power ultra low profile *single-function* pc. I would very much like to know if this hardware can run windows 7. It doesnt need to run well, it just needs to be able to go on the web and do basic things similar to an atom nettop.
  • superPC - Wednesday, April 25, 2012 - link

    it won't run windows 7. unlike windows 8, windows 7 requires standard RAM not LPDDR. windows 7 also requires some form of PCI.
  • Musafir_86 - Wednesday, April 25, 2012 - link

    -Excuse me, but IMHO, the type of physical RAM shouldn't matter. If not, we couldn't be able to load these OSes on VMs at all. :)

    Regards.
  • B3an - Thursday, April 26, 2012 - link

    Why would you even want to run Win 7 on this when Win 8 would clearly be WAY better suited, not to mention it also uses less resources and RAM while remaining faster/snappier than 7.
  • rahvin - Friday, April 27, 2012 - link

    I'd imagine he wants to know because Windows 8 is going to be only slightly less successful than Vista. Personally I'd guess around 5% of the Vista sales. It's a disaster in waiting unless they make dramatic last minute changes. You should try using it.
  • joshv - Wednesday, April 25, 2012 - link

    I am not sure why this chipset matters. Intel usually wins on x86 compatibility with older software. In the phone space there is no existing x86 code, and in fact they are stuck emulating another ABI - so they will be slower and less efficient that competitors that implement that ABI natively.

    That leaves Intel to compete on price/performance alone in a market where their competitors have 99.9% of the market. An odd position for Intel.

    Perhaps this makes more sense in a Windows 8 tablet?
  • Impulses - Wednesday, April 25, 2012 - link

    Its netbooks all over again, on a much bigger scale. ARM is moving upscale, if Intel doesn't start competing directly they will eventually start ceding some existing market share (when tablets/laptops start to overlap more, and the writing's on the wall with Windows for ARM).

    Only difference is they're up against a capable rival(s) as opposed to a limping AMD, so they can't just come out of the gate strong and them dog it and let the lower end market stagnate in order to maintain profits.

    This is a small first step but it'll allow them to ink more deals and possibly cement a strong foundation for upcoming Win8 ARM tablets which is probably their bigger long term concern.
  • dcollins - Wednesday, April 25, 2012 - link

    Did you even read the article?

    The x86 vs ARM issue is mostly a non-issue that will be completely resolved within a few months. Dalvik apps are JIT compiled to ARM and x86 and will perform similarly. In fact Intel might have an advantage here because they have the best compiler engineers in the world with decades of experience in generating high performance x86 code. NDK apps will generally be supported natively; developers only have to check a box to include x86 binaries. Even Apps that aren't compiled with x86 support are translated prior to installation on the users device. Nothing about the instruction set makes Medfield slower than ARM.

    Performance today is comparable to modern ARM processors even when running an out of date, slower OS. Performance in 4.0.x should match or outperform even Krait. Graphics performance is middle of the road, but that's a major concern for many smartphone buyers (myself included). Even in benchmarks that purposefully stress mutliple cores, Medfield holds its own against the many cored competitors. Real world usage is more lightly threaded.

    Browser performance is the most important metric for my usage and here Intel performs extremely well. If Medfield is available in a 4.x phone when it comes time for me to upgrade, I will seriously consider it versus a Krait based offering. Now imagine a next generation Atom build on 22nm with dual core, hyperthreading and possibly OoO execution: that chip will eat A15s for breakfast.
  • dcollins - Wednesday, April 25, 2012 - link

    edit: "Graphics performances... is NOT a major concern"

Log in

Don't have an account? Sign up now