• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Does anyone know, specifically, what model processor this phone has?

MStreeter

Newbie
It's a Qualcom Snapdragon... something. I'm seeing conflicting reports both from Google and system information applications. Thought I'd ask here.

Anyone in the know?
 
I've been wondering this myself. Qualcomm's website has it listed as MSM8655. The buildprops just call it "m3s". Our kernel is configured for "lge_m3s-perf", contains "CONFIG_ARCH_MSM7X30=y" in the defconfig, and uses files for MSM7x30. Our second-stage bootloader is built from a tree with "msm7x30" in the path, and some of the functions return a "MSM7630".

There's this bit of code in the kernel that has me scratching my head, too.
Code:
static struct pll pll2_tbl[] = {
    {  42, 0, 1, 0 }, /*  806 MHz */
    {  53, 1, 3, 0 }, /* 1024 MHz */
    { 125, 0, 1, 1 }, /* 1200 MHz */
    {  73, 0, 1, 0 }, /* 1401 MHz */
};

/* Use negative numbers for sources that can't be enabled/disabled */
#define SRC_LPXO (-2)
#define SRC_AXI  (-1)
/*
 * Each ACPU frequency has a certain minimum MSMC1 voltage requirement
 * that is implicitly met by voting for a specific minimum AXI frequency.
 * Do NOT change the AXI frequency unless you are _absoulutely_ sure you
 * know all the h/w requirements.
 */
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
    { 0, 24576,  SRC_LPXO, 0, 0,  30720000,  900, VDD_RAW(900) },
    { 0, 61440,  PLL_3,    5, 11, 61440000,  900, VDD_RAW(900) },
    { 1, 122880, PLL_3,    5, 5,  61440000,  900, VDD_RAW(900) },
    { 0, 184320, PLL_3,    5, 4,  61440000,  900, VDD_RAW(900) },
    { 0, MAX_AXI_KHZ, SRC_AXI, 1, 0, 61440000, 900, VDD_RAW(900) },
    { 1, 245760, PLL_3,    5, 2,  61440000,  900, VDD_RAW(900) },
    { 1, 368640, PLL_3,    5, 1,  122800000, 900, VDD_RAW(900) },
    /* AXI has MSMC1 implications. See above. */
    { 1, 768000, PLL_1,    2, 0,  153600000, 1050, VDD_RAW(1050) },
    /*
     * AXI has MSMC1 implications. See above.
     */
    { 1, 806400,  PLL_2, 3, 0, UINT_MAX, 1100, VDD_RAW(1100), &pll2_tbl[0]},
    { 1, 1024000, PLL_2, 3, 0, UINT_MAX, 1200, VDD_RAW(1200), &pll2_tbl[1]},
    { 1, 1200000, PLL_2, 3, 0, UINT_MAX, 1200, VDD_RAW(1200), &pll2_tbl[2]},
    { 1, 1401600, PLL_2, 3, 0, UINT_MAX, 1250, VDD_RAW(1250), &pll2_tbl[3]},
    { 0 }
};


/*
 * Truncate the frequency table at the current PLL2 rate and determine the
 * backup PLL to use when scaling PLL2.
 */
void __init pll2_fixup(void)
{
    struct clkctl_acpu_speed *speed = acpu_freq_tbl;
    u8 pll2_l = readl(PLL2_L_VAL_ADDR) & 0xFF;

    for ( ; speed->acpu_clk_khz; speed++) {
        if (speed->src != PLL_2)
            backup_s = speed;
        if (speed->pll_rate && speed->pll_rate->l == pll2_l) {
            speed++;
            speed->acpu_clk_khz = 0;
            return;
        }
    }

    pr_err("Unknown PLL2 lval %d\n", pll2_l);
    BUG();
}
You start with that table with a list of CPU speeds and voltages. When this function is called shortly after bootup, if reads a value from the processor and truncates that table to limit it to what the processor says it supports. On our phone, it truncates the table by chopping off the 1200000 and 1401600. That means that it has decided that our processor supports 1024000.




So, you have qualcomm, who made the thing saying it has a msm8655. And then you have LG, who compiled all the software thinking its a MSM7630. And you have the processor itself, which tells the kernel that it supports 1GHz. LG is advertising the phone as 800MHz.

It may come down to one of us just opening up the little guy and reading the words on the chip itself.
 
I don't know if this means anything, but when I've done benchmarks, I've had CPU readings up to 1050. Which means its not set to a specific maximum or at least not 1024
 
In the system information app I was using I saw "MSM7x30" as well, and scratched my head in befuddlement. My carrier, Ting, listed it as 800 MHz MSM7627A, yet the phone tells me it's clocked at 1024 GHz. Puzzling...

At least subjectively, this doesn't feel like an old gen S1 processor. It cost $193 unsubsidized, there's no way the processor is -that- much of a bargain bin.

This isn't the most imperative of research, but I would like to learn a bit more about my SoC. I feel more confident tinkering with my phone if I know what's in it.
 
Back
Top Bottom