All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanho Park <chanho61.park@samsung.com>
To: 'Krzysztof Kozlowski' <k.kozlowski@samsung.com>,
	'Joonyoung Shim' <jy0922.shim@samsung.com>,
	'Kukjin Kim' <kgene@kernel.org>
Cc: 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,
	'Bartlomiej Zolnierkiewicz' <b.zolnierkie@samsung.com>
Subject: RE: [PATCH] ARM: dts: add exynos5422.dtsi to correct cpu order
Date: Thu, 28 May 2015 17:43:13 +0900	[thread overview]
Message-ID: <030f01d09922$55a2e120$00e8a360$@samsung.com> (raw)
In-Reply-To: <5566A7A0.4080608@samsung.com>

Hi,

> When adding new 5422 board we can split out CPU configuration to
> separate DTSI file. I already posted patches for Odroid XU3-family
> common DTSI file for XU3 Lite board:
> http://www.spinics.net/lists/linux-samsung-soc/msg44868.html

IMHO, all of the exynos5422 boards will be same cpu configurations. That's
why I added new exynos5422.dtsi.

> 
> > BTW, booting of secondary cpus are still broken. Is there any progress
> of
> > the patch[1]?
> > This patch is also generated top of the patch with some fixes.
> >
> > [1]. http://www.spinics.net/lists/linux-samsung-soc/msg39523.html
> 
> No progress so far. Apparently nobody knows why this works and what to
> do with it. I would suspect booted CPUs stuck somewhere in BL1 or BL2
> and writing to PMU_SPARE2 kicks them. However this is just a guess.
> 
> Kukjin which could be the closest person to the real knowledge (LSI) did
> not gave his feedback.
> 
> We have a lot of such hacks and undocumented interfaces between kernel
> and bootloaders. IMHO it would be good to start documenting them.

Good. But, who can do it?

Best Regards,
Chanho Park

  reply	other threads:[~2015-05-28  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 15:15 [PATCH] ARM: dts: add exynos5422.dtsi to correct cpu order Chanho Park
2015-05-28  1:58 ` Joonyoung Shim
2015-05-28  4:00   ` Chanho Park
2015-05-28  5:29     ` Krzysztof Kozlowski
2015-05-28  8:43       ` Chanho Park [this message]
2015-05-31  7:09         ` Krzysztof Kozlowski
2015-05-28  8:49     ` Marek Szyprowski
2015-05-28 17:19       ` Kevin Hilman

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='030f01d09922$55a2e120$00e8a360$@samsung.com' \
    --to=chanho61.park@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=heesub.shin@samsung.com \
    --cc=javier.martinez@collabora.co.uk \
    --cc=jy0922.shim@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=khilman@linaro.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --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.