ARM told us to expect some of the first 64-bit ARMv8 based SoCs to ship in 2014, and it looks like we're seeing just that. Today Qualcomm is officially announcing its first 64-bit SoC: the Snapdragon 410 (MSM8916).

Given that there's no 64-bit Android available at this point, most of the pressure to go to 64-bit in the Android space is actually being driven by the OEMs who view 64-bit support as a necessary checkbox feature at this point thanks to Apple's move with the A7. Combine that with the fact that the most ready 64-bit IP from ARM is the Cortex A53 (successor to the Cortex A5/A7 line), and all of the sudden it makes sense why Qualcomm's first 64-bit mobile SoC is aimed at the mainstream market (Snapdragon 400 instead of 600/800).

I'll get to explaining ARM's Cortex A53 in a moment, but first let's look at the specs of the SoC:

Qualcomm Snapdragon 410

Internal Model Number

MSM8916

Manufacturing Process

28nm LP

CPU

4 x ARM Cortex A53 1.2GHz+

GPU

Qualcomm Adreno 306

Memory Interface

1 x 64-bit LPDDR2/3

Integrated Modem

9x25 core, LTE Category 4, DC-HSPA+

At a high level we're talking about four ARM Cortex A53 cores, likely running around 1.2 - 1.4GHz. Having four cores still seems like a requirement for OEMs in many emerging markets unfortunately, although I'd personally much rather see two higher clocked A53s. Qualcomm said the following about 64-bit in its 410 press-release:

"The Snapdragon 410 chipset will also be the first of many 64-bit capable processors as Qualcomm Technologies helps lead the transition of the mobile ecosystem to 64-bit processing.”

Keep in mind that Qualcomm presently uses a mix of ARM and custom developed cores in its lineup. The Snapdragon 400 line already includes ARM (Cortex A7) and Krait based designs, so the move to Cortex A53 in the Snapdragon 410 isn't unprecedented. It will be very interesting to see what happens in the higher-end SKUs. I don't assume that Qualcomm will want to have a split between 32 and 64-bit designs, which means we'll either see a 64-bit Krait successor this year or we'll see more designs that leverage ARM IP in the interim.

As you'll see from my notes below however, ARM's Cortex A53 looks like a really good choice for Qualcomm. It's an extremely power efficient design that should be significantly faster than the Cortex A5/A7s we've seen Qualcomm use in this class of SoC in the past.

The Cortex A53 CPU cores are paired with an Adreno 306 GPU, a variant of the Adreno 305 used in Snapdragon 400 based SoCs (MSM8x28/8x26).

The Snapdragon 410 also features an updated ISP compared to previous 400 offerings, adding support for up to a 13MP primary camera (no word on max throughput however).

Snapdragon 410 also integrates a Qualcomm 9x25 based LTE modem block (also included in the Snapdragon 800/MSM8974), featuring support for LTE Category 4, DC-HSPA+ and the usual legacy 3G air interfaces.

All of these IP blocks sit behind a single-channel 64-bit LPDDR2/3 memory interface.

The SoC is built on a 28nm LP process and will be sampling in the first half of 2014, with devices shipping in the second half of 2014. Given its relatively aggressive schedule, the Snapdragon 410 may be one of the first (if not the first) Cortex A53 based SoCs in the market.

A Brief Look at ARM's Cortex A53

ARM's Cortex A53 is a dual-issue in-order design, similar to the Cortex A7. Although the machine width is unchanged, the A53 is far more flexible in how instructions can be co-issued compared to the Cortex A7 (e.g. branch, data processing, load-store, & FP/NEON all dual-issue from both decode paths).

The A53 is fully ISA compatible with the upcoming Cortex A57, making A53 the first ARMv8 LITTLE processor (for use in big.LITTLE) configurations with an A57

The overall pipeline depth hasn't changed compared to the Cortex A7. We're still dealing with an 8-stage pipeline (3-stage fetch pipeline + 5 stage decode/execute for integer or 7 for NEON/FP). The vast majority of instructions will execute in one cycle, leaving branch prediction as a big lever for increasing performance. ARM significantly increased branch prediction accuracy with the Cortex A53, so much that it was actually leveraged in the dual-issue, out-of-order Cortex A12. ARM also improved the back end a bit, improving datapath throughput.

The result of all of this is a dual-issue design that's pushed pretty much as far as you can without going out-of-order. Below are some core-level performance numbers, all taken in AArch32 mode, comparing the Cortex A53 to its A5/A7 competitors:

Core Level Performance Comparison

All cores running at 1.2GHz

DMIPS

CoreMark

SPECint2000

ARM Cortex A5

1920

-

350

ARM Cortex A7

2280

3840

420

ARM Cortex A9 r4p1

-

-

468

ARM Cortex A53

2760

4440

600

Even ignoring any uplift from new instructions or 64-bit, the Cortex A53 is going to be substantially faster than its predecessors. I threw in hypothetical SPECint2000 numbers for a 1.2GHz Cortex A9 to put A53's performance in even better perspective. You should expect to see better performance than a Cortex A9r4 at the same frequencies, but the A9r4 is expected to hit much higher frequencies (e.g. 2.3GHz for Cortex A9 r4p1 in NVIDIA's Tegra 4i).

ARM included a number of power efficiency improvements and is targeting 130mW single-core power consumption at 28nm HPM (running SPECint 2000). I'd expect slightly higher power consumption at 28nm LP but we're still talking about an extremely low power design.

I'm really excited to see what ARM's Cortex A53 can do. It's a potent little architecture, one that I wish we'd see taken to higher clock speeds and maybe even used in higher end devices at the same time. The most obvious fit for these cores however is something like the Moto G, which presently uses the 32-bit Cortex A7. Given Qualcomm's schedule, I wouldn't be surprised to see something like a Moto G update late next year with a Snapdragon 410 inside. Adding LTE and four Cortex A53s would really make that the value smartphone to beat.

Post Your Comment

95 Comments

There are also specific security and ease-of-programming benefits to 64 bit. The Linux kernel used in Android supports address space randomization; it's much easier to pick an unexpected address range when you have 64 bits to play with. And the POSIX mmap() functionality can work on much later files with a 64-bit address space, making it easier to write performant apps that work with large data sets (high MP photos, for instance).Reply

Having 64 bit applications is even a disadvantage when you have little (say 1GB or less) of memory. As mentioned http://www.anandtech.com/show/7460/apple-ipad-air-...">here on Anandtech 64bit apps use 20-30% more memory so 1GB of memory on a 64bit phone/tablet equals to ~0.75 GB memory on a 32bit device. Meaning that you see reloading tabs in browsers and apps occur sooner.Reply

Estimates are that going to 64 bit can bring a 15% increase in performance by itself. There is a multiplication factor to that when you include the other improvements made.

But for a number of mathematical calculations, such as those made using encryption, estimates are that there could easily be a 10x improvement. The touch sensor would be benefiting. Perhaps that's why it's so fast.Reply

Yes and no. Yes in terms of testing the demand for low-end 4-bit chips to allow for easier and faster adoption later. Then hit the market with high-end fast chips when it mushroomed. Secondly to stake in the ground that Qualcomm has a production 64bit Arm chip that it can do amazing 64bit chips later when the demand shoots up in the market. Qualcomm has been able to move fast, so that is a real advantage to competitors like Nvdia who announces and OEMs wait and wait. Then waited somemore ...Reply

I think that in first approximation you're right: using 64bit CPU to run 32bit code is substantially useless. It will go a bit faster in some cases, consume a bit more, all things being equal.I think though that the point of 64bit CPU is a mid/long term preparation.I think it is inevitable to see mobile systems with 4GB or more of memory: already the tablets, especially 10" tablets, could (should?) be used to multitask and to run some relatively intense computational programs. I think what Qualcomm is trying to avoid is what happened int the PC market, where the need for 4GB+ of RAM was there and at that point the vast majority of PCs used 32bit CPUs.For cellphones, especially the ones in the ranges targeted by the 410, I really don't see any significant benefit, other than making the architecture future-proof and having 64bit-only devices across the board.Reply