WTR3925

There are a few things that are important when talking about a transceiver. To recap, transceivers have a few key elements. On the receive side, we see the need for low noise amplifiers, down-converters, and narrow-band amplifiers. On the transmit side, we need a driver amplifier, up-converter, and another set of narrow-band amplifiers. While most of RF360 is built on relatively old process nodes for CMOS technology, the transceiver can be built on newer CMOS processes because it’s doesn’t have to handle the level of signal that the rest of the front end does.

At a high level, the WTR3925 really brings two new capabilities to the table. First, it does away with the need for a companion transceiver in order to achieve carrier aggregation, which the WTR1625L/WFR1620 combination provided. It seems that this is due to the need for additional ports on the transceiver, which the WTR1625L lacked. The other improvement is that WTR3925 moves to a new 28nm RF process, as opposed to the 65nm RF process used for the WTR1625L.

As a quick aside, RF processes are largely similar to CMOS processes, although with a few modifications. These changes can be thicker metal in interconnects between transistors and memcaps, which are analogous to capacitors in DRAM. Qualcomm claims that this will drive down power consumption, however this is a product of a new architecture that takes advantage of the smaller process node. Unlike digital logic such as what we see on the baseband, RF does not directly benefit from scaling to lower processes. In fact, there is a chance that scaling to lower process nodes can hurt power consumption because even though the transistor can operate faster, there is more noise As a result of this noise, the amplifiers in the transceivers may need more stages and more power in order to achieve the same noise figure.

MDM9x35

While baseband was previously one of the most popular topics in RF, as can be seen by this article RF is much more than just the baseband. However, the baseband is a critical part of the chain. The RF front end is critical for reception and a myriad of other issues, but feature support and control of the front-end lies with the baseband. The baseband must properly interpret the information that the front-end provides and also send out information to the front-end to transmit.

Fortunately, the baseband is implemented with digital logic, so there are significant benefits to moving to the latest and greatest CMOS process node. Lower voltage (and therefore power) is needed to drive the transistors, and it becomes easier to drive higher performance in the DSP. In the case of the MDM9x35, we see that there's a QDSP clocked at 800 MHz for modem functions, and a 1.2 GHz Cortex A7 for functions such as mobile hotspot.

In the case of MDM9x35, there are two major contributors to the reduction in power consumption. The first is the move from 28nm HPm to 20nm SoC. While 20nm SoC doesn’t utilize FinFET, we still see scaling in power, performance, and density. The other area where we see power savings is better implementation of various algorithms. As a result, we should see around 20-25% power savings with the same workload.

MDM9x45

In the time since the first MDM9x35 devices were launched, Qualcomm has also iterated on modems. With the 9x45 generation, we see a move to category 10 LTE, which includes 450 Mbps maximum download speed when aggregating three 20 MHz carriers, and two 20 MHz carriers on the uplink for a maximum of 100 Mbps. Although the Snapdragon 810 doesn't have a 9x45 IP block for the modem, the Snapdragon 810 does support up a maximum of 450 Mbps for download with category 9 LTE. However, there is no uplink carrier aggregation in such a scenario. Uplink carrier aggregation is only possible with category 7, which limits downlink speeds to 300 Mbps.

Qualcomm claims that the MDM9x45 should bring around 40% energy savings in an LTE carrier aggregation scenario when compared to the MDM9x25 modem. In addition, these new modems bring in a new generation of GNSS location, with support for EU's Galileo constellation. It's likely that the DSPs and other aspects of this modem have been beefed up relative to the 9x35 and 8994 modems to enable category 10 data rates.

RF: Antenna Tuner, CMOS PA/Switch Qualcomm's Energy Aware Scheduler
Comments Locked

119 Comments

View All Comments

  • PC Perv - Thursday, February 12, 2015 - link

    Did review state on what OS the benchmarks were run? KitKat, Lollipop, 64-bit/32-bit, etc.? Sorry if I missed it.
  • Gigaplex - Thursday, February 12, 2015 - link

    Why go through all that detail on how their software stack for big.LITTLE improves over stock ARM, without testing to see if it works? The Exynos article the other day showed that big.LITTLE flat out didn't work, performing worse than parking on little cores but consuming more energy. Does Qualcomms one actually improve things here?
  • bigstrudel - Thursday, February 12, 2015 - link

    I'm beyond skeptical of 810's performance under actual thermal constraints like inside a flagship smartphone.
  • PC Perv - Thursday, February 12, 2015 - link

    I am not sure how useful those system-level benches (Basemark, 3DMark) are to compare different platforms. On same platform (OS), I can see the value.
  • HisDivineOrder - Thursday, February 12, 2015 - link

    Given all the press runs (here, PCper) Qualcomm are doing, the loss of that Samsung contract must have REALLY got someone's knickers in a twist.
  • blzd - Thursday, February 12, 2015 - link

    Good article. Thanks for including some S800 devices in some of the device comparisons, more of that (older SoC for comparison) please if you can.
  • tuxRoller - Thursday, February 12, 2015 - link

    I'll say this once again: email Rob Clark of red hat. He's been working on a clean-room implementation of adreno (https://github.com/freedreno/freedreno) for a few years and has gotten quite far (gl 2.1/gl|es 2.0, iirc).
    He's a super nice guy, and given that Qualcomm has been contributing, a bit, to his project he may be loathe to harm the relationship, but, if nothing else, you can read through his repo to understand the arch.
  • aryonoco - Thursday, February 12, 2015 - link

    Fantastic preview, thanks guys, it's been great at AT over the last couple of weeks!

    Just a note, in future and especially when reviewing shipping devices, could you pay some attention to the 2-year upgrade performance improvement as well? Most people (in the developed world at least) seem to be on 2-year upgrade cycles, and so it makes sense to compare the current generation to the phone that's in their hand. AT does this for desktop/laptop CPUs and GPUs (for example informing people that if you already have Ivy Bridge, there's not much performance to be gained by Haswell etc) so it would be great it if that coverage extends to mobile platforms as well (for example comparing SD810 with SD600 and the level of improvement one might expect between them).
  • wyewye - Friday, February 13, 2015 - link

    Why no Wifi tests?

    You say it supports MU-MIMO and 801.22ad, but anywhere else I read only "ac" and MU-MIMO is supported.
  • PC Perv - Friday, February 13, 2015 - link

    Page 6, after the Geekbench floating-point chart, you said:

    "In this case Snapdragon 810 performance is relatively close to Exynos 5433 performance even though it has the advantage of running in AArch64 mode, which should give the FP numbers a boost over the Exynos. This is likely an isolated case where the Krait architecture and Snapdragon 805's high clock speed play to its favor."

    And I have no idea what you are saying. I do not want to sound rude, but this kind of writing is what I saw from previous articles written by Mr. Ho (and Mr. Chester).

Log in

Don't have an account? Sign up now