From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Peter Chubb <peter.chubb@nicta.com.au>, Chanho Park <parkch98@gmail.com>
Cc: kgene@kernel.org, jy0922.shim@samsung.com, cw00.choi@samsung.com,
linux-samsung-soc@vger.kernel.org,
javier.martinez@collabora.co.uk, khilman@linaro.org,
sjoerd.simons@collabora.co.uk, heesub.shin@samsung.com,
m.szyprowski@samsung.com, b.zolnierkie@samsung.com,
Chanho Park <chanho61.park@samsung.com>
Subject: Re: [PATCHv3] ARM: dts: add exynos5422-cpus.dtsi to correct cpu order
Date: Tue, 02 Jun 2015 21:02:23 +0900 [thread overview]
Message-ID: <556D9B4F.3070508@samsung.com> (raw)
In-Reply-To: <84k2vmwzxc.wl-peter.chubb@nicta.com.au>
W dniu 02.06.2015 o 12:29, Peter Chubb pisze:
>>>>>> "Chanho" == Chanho Park <parkch98@gmail.com> writes:
>
> Chanho> The odroid-xu3 board which is based on exynos5422 not
> Chanho> exynos5800 is booted from cortex-a7 core unlike
> Chanho> exynos5800. The odroid-xu3's cpu order is quite strange. cpu0
> Chanho> and cpu5-7 are cortex-a7 cores and cpu1-4 are cortex-a15
> Chanho> cores. To correct this mis-odering, I added exynos5422.dtsi
> Chanho> and reversing cpu orders from exynos5420. Now, cpu0-3 are
> Chanho> cortex-a7 and cpu4-7 are cortex-a15.
>
> Does this patch make any difference? CPUs are numbered in the kernel
> in the order they're enumerated; with this patch or using the old dts
> I see the CPUs numbered the same after boot. And only 5 of the 8 come
> up: processor 0 is an A7; processors 1 through 4 are A15.
In my case (Odroid XU3 Lite, next-20150529) the patch makes difference.
The A7 is 0-3 and A15 is 4-7 so the patch changes the order.
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-06-02 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 12:24 [PATCHv3] ARM: dts: add exynos5422-cpus.dtsi to correct cpu order Chanho Park
2015-06-01 23:55 ` Krzysztof Kozlowski
2015-07-01 13:35 ` Chanho Park
2015-07-01 23:50 ` Krzysztof Kozlowski
2015-06-02 3:29 ` Peter Chubb
2015-06-02 12:02 ` Krzysztof Kozlowski [this message]
2015-06-02 12:49 ` Chanho Park
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=556D9B4F.3070508@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=heesub.shin@samsung.com \
--cc=javier.martinez@collabora.co.uk \
--cc=jy0922.shim@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=parkch98@gmail.com \
--cc=peter.chubb@nicta.com.au \
--cc=sjoerd.simons@collabora.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.