linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/3] Exynos 5410 support
Date: Thu, 12 Dec 2013 16:32:46 -0800	[thread overview]
Message-ID: <87haad615d.fsf@linaro.org> (raw)
In-Reply-To: <52A836C9.9020405@samsung.com> (Tarek Dakhran's message of "Wed, 11 Dec 2013 13:56:25 +0400")

Tarek Dakhran <t.dakhran@samsung.com> writes:

> On 12/10/2013 08:40 PM, Kevin Hilman wrote:
>> Vyacheslav Tyrtov <v.tyrtov@samsung.com> 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.

  reply	other threads:[~2013-12-13  0:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 14:26 [PATCH v5 0/3] Exynos 5410 support Vyacheslav Tyrtov
2013-12-10 14:26 ` [PATCH v5 1/3] ARM: EXYNOS: Add support for EXYNOS5410 SoC Vyacheslav Tyrtov
2013-12-10 14:26 ` [PATCH v5 2/3] clk: exynos5410: register clocks using common clock framework Vyacheslav Tyrtov
2013-12-10 14:26 ` [PATCH v5 3/3] ARM: dts: Add initial device tree support for EXYNOS5410 Vyacheslav Tyrtov
2013-12-10 16:40 ` [PATCH v5 0/3] Exynos 5410 support Kevin Hilman
2013-12-11  9:56   ` Tarek Dakhran
2013-12-13  0:32     ` Kevin Hilman [this message]
2013-12-11 22:29 ` Kukjin Kim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87haad615d.fsf@linaro.org \
    --to=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).