From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v11 0/3] Exynos 5410 support
Date: Mon, 02 Jun 2014 08:05:10 -0700 [thread overview]
Message-ID: <7hzjhvxsgp.fsf@paris.lan> (raw)
In-Reply-To: <CANhyOUeq1MMHHn9t+Fy5gpkb43y_rS9F_OAoJ_KFyM1pL4ZJ4w@mail.gmail.com> (Tarek Dakhran's message of "Fri, 30 May 2014 23:07:01 +0400")
Tarek Dakhran <t.dakhran@gmail•com> writes:
> Hi,
>
> On Fri, May 30, 2014 at 7:41 AM, Tushar Behera <trblinux@gmail•com> wrote:
>> On Thu, May 29, 2014 at 11:30 PM, Andreas F?rber <afaerber@suse•de> wrote:
>>> Hi Tarek,
>>>
>>>
>>> And I reproducibly get failures for CPUs 1-3, resulting in only one CPU
>>> in /proc/cpuinfo (compared to 4 on downstream 3.14):
>>>
>>> [ 0.045778] CPU: Testing write buffer coherency: ok
>>> [ 0.045968] /cpus/cpu at 0 missing clock-frequency property
>>> [ 0.045993] /cpus/cpu at 1 missing clock-frequency property
>>> [ 0.046016] /cpus/cpu at 2 missing clock-frequency property
>>> [ 0.046040] /cpus/cpu at 3 missing clock-frequency property
>>> [ 0.046059] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
>>> [ 0.046135] Setting up static identity map for 0x403a8920 - 0x403a8978
>>> [ 2.075052] CPU1: failed to come online
>>> [ 4.085095] CPU2: failed to come online
>>> [ 6.095142] CPU3: failed to come online
>>> [ 6.095237] Brought up 1 CPUs
>>> [ 6.095269] SMP: Total of 1 processors activated.
>>> [ 6.095303] CPU: All CPU(s) started in HYP mode.
>>> [ 6.095336] CPU: Virtualization extensions available.
>>>
>>> I also notice another apparent device tree issue:
>>>
>>> [ 7.341814] of_get_named_gpiod_flags: can't parse gpios property of
>>> node '/soc/mmc at 12220000/slot at 0[0]'
>>> [ 7.341850] of_get_named_gpiod_flags: can't parse gpios property of
>>> node '/soc/mmc at 12220000/slot at 0[0]'
>>>
>>> Are any of those known issues and being worked on?
>>> (The CPU failures affected 5420 Arndale Octa as well iirc.)
>>>
>>
>> Can you check after applying following two patches for Arndale-Octa
>> ([1],[2])? In other words, a patch similar to [2] might be required
>> for this board too if it is booting under secure mode.
>
> Firmware node already present into exynos5410-smdk5410.dts
> So with only patch[1] 4xA15 cores will boot on ODROID-XU and SMDK5410.
I also confirm that with 4xA15 cores boot when adding patch [1].
Kevin
>>
>> [1] http://www.spinics.net/lists/linux-samsung-soc/msg31776.html
>>
>> [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode
>>
>> [2] http://www.spinics.net/lists/linux-samsung-soc/msg31777.html
>>
>> [PATCH v2 Resend 2/2] ARM: dts: Add secure firmware support for Arndale-octa
>>
>>
>> --
>> Tushar Behera
>
> Best regards,
> Tarek
next prev parent reply other threads:[~2014-06-02 15:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 3:23 [PATCH v11 0/3] Exynos 5410 support Tarek Dakhran
2014-05-26 3:23 ` [PATCH v11 1/3] ARM: EXYNOS: Add support for EXYNOS5410 SoC Tarek Dakhran
2014-05-26 3:23 ` [PATCH v11 2/3] clk: exynos5410: register clocks using common clock framework Tarek Dakhran
2014-05-28 0:41 ` Mike Turquette
2014-05-28 2:20 ` Tarek Dakhran
2014-05-28 4:49 ` Kukjin Kim
2014-05-28 7:22 ` Mike Turquette
2014-05-26 3:23 ` [PATCH v11 3/3] ARM: dts: Add initial device tree support for EXYNOS5410 Tarek Dakhran
2014-05-26 11:11 ` [PATCH v11 0/3] Exynos 5410 support Tomasz Figa
2014-05-26 22:08 ` Kukjin Kim
2014-05-27 17:06 ` Kevin Hilman
2014-05-27 17:44 ` Kevin Hilman
2014-05-27 20:17 ` Tarek Dakhran
2014-05-27 20:37 ` Tomasz Figa
2014-05-27 20:44 ` Kevin Hilman
2014-05-29 13:36 ` Andreas Färber
2014-05-29 14:46 ` Tarek Dakhran
2014-05-29 18:00 ` Andreas Färber
2014-05-30 3:41 ` Tushar Behera
2014-05-30 19:07 ` Tarek Dakhran
2014-06-02 15:05 ` Kevin Hilman [this message]
[not found] ` <CAK9yfHwatFrQ9ssjJXi=eR3mz95xWQeRJ4-vkteR_Npksa3+tg@mail.gmail.com>
2014-05-30 19:15 ` Tarek Dakhran
2014-05-30 5:10 ` Tomasz Figa
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=7hzjhvxsgp.fsf@paris.lan \
--to=khilman@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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