Tarek Dakhran <t.dakhran@xxxxxxxxxxx> writes: > On 12/10/2013 08:40 PM, Kevin Hilman wrote: >> Vyacheslav Tyrtov <v.tyrtov@xxxxxxxxxxx> writes: >> >>> The series of patches represent support of Exynos 5410 SoC >>> >>> The Exynos 5410 is the first Samsung SoC based on bigLITTLE architecture >>> >>> Patches add new platform description, support of clock controller and device >>> tree for Exynos 5410. >>> >>> Dual cluster support for Exynos 5410 (EDCS) has been removed from this series >>> This patches is activating only the big cluster (all A15 cores) >> Testing this series on top of v3.13-rc3, plus a couple of other >> necessary changes (which should've probably been noted in the changelog): >> >> 1) change CONFIG_NR_CPUS=8 in .config >> 2) add the exynos combiner patch from Chander: >> [PATCH v2] irqchip: exynos-combiner: remove hard-coded irq_base value >> >> I'm still only seeing 2 out of 4 cores come up on my odroid-xu: >> >> [ 0.045000] CPU: Testing write buffer coherency: ok >> [ 0.045000] CPU0: update cpu_power 1024 >> [ 0.045000] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 >> [ 0.045000] Setting up static identity map for 0x403717d8 - 0x40371830 >> [ 0.045000] CPU1: Booted secondary processor >> [ 0.065000] CPU1: update cpu_power 1024 >> [ 0.065000] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 >> [ 1.075000] CPU2: failed to boot: -38 >> [ 2.075000] CPU3: failed to boot: -38 >> [ 2.075000] Brought up 2 CPUs >> [ 2.075000] SMP: Total of 2 processors activated. >> [ 2.075000] CPU: All CPU(s) started in SVC mode. >> > Hi Kevin, > > EDCS(exynos dual cluster support) moved to separate patch now. > This patches introduce only base SoC support (2xA15). Thanks for the clarification I thought there were 4 A15s, and the changelog mentioned this patch enabled "all A15s". Kevin > Patches tested on samsung smdk5410 board. > > Next version of EDCS patches will be available soon. > They allow power on and boot all 8 cores. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |