linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/9] arm64: dts: exynos: Add dts files for 64-bit Exynos5433 SoC
Date: Tue, 10 Mar 2015 10:31:03 +0900	[thread overview]
Message-ID: <54FE4957.7050904@samsung.com> (raw)
In-Reply-To: <54F99B1A.3080600@samsung.com>

Hi Mark,

On 03/06/2015 09:18 PM, Chanwoo Choi wrote:
> Hi,
> 
> On 03/06/2015 08:40 PM, Mark Rutland wrote:

[snip]

>>
>>>>>>>> I take it CPUs boot at EL2?
>>>>>>
>>>>>> Do the CPUs boot at EL1 or EL2?
>>>>>
>>>>> Unfortunately, I cannot check the secure firmware for Exynos5433 SoC.
>>>>> I think that a few SoC provider probably would know it.
>>>>
>>>> I guess I asked the wrong question.
>>>>
>>>> Do CPUs enter the kernel at EL2 or at EL1?
>>>
>>> Could you give me a tip how to check the kernel at EL2 or EL1?
>>
>> Hmm... I thought we logged this but it looks like we don't.
>>
>> You could hack in a check of is_hyp_mode_available() and
>> is_hyp_mode_mismatched(). That will tell you if EL2/hyp is available,
>> and whether all CPUs enter at the same mode (mandatory per the boot
>> protocol).
> 
> OK, I'll try it.

I check the return value of is_hyp_mode_available() to catch whether EL1 or EL2. 

The is_hyp_mode_available() returns 'false' during kernel booting.
- __boot_cpu_mode[0]: 0xe11 (BOOT_CPU_MODE_EL1)
- __boot_cpu_mode[1]: 0x0

Best Regards,
Chanwoo Choi

  reply	other threads:[~2015-03-10  1:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  5:38 [PATCH v5 0/9] arm64: Add the support for new Exynos5433 SoC Chanwoo Choi
2015-03-05  5:38 ` [PATCH v5 1/9] arm64: dts: exynos: Add dts files for 64-bit " Chanwoo Choi
2015-03-05 12:24   ` Mark Rutland
2015-03-05 16:12     ` Chanwoo Choi
2015-03-05 17:04       ` Mark Rutland
2015-03-05 17:36         ` Chanwoo Choi
2015-03-05 18:54           ` Mark Rutland
2015-03-06  2:42             ` Chanwoo Choi
2015-03-06 11:40               ` Mark Rutland
2015-03-06 12:18                 ` Chanwoo Choi
2015-03-10  1:31                   ` Chanwoo Choi [this message]
2015-03-12 10:39                     ` Mark Rutland
2015-03-05  5:38 ` [PATCH v5 2/9] arm64: dts: exynos: Add MSHC dt node for Exynos5433 Chanwoo Choi
2015-03-05  5:38 ` [PATCH v5 3/9] arm64: dts: exynos: Add SPI/PDMA " Chanwoo Choi
2015-03-05  5:38 ` [PATCH v5 4/9] arm64: dts: exynos: Add PMU " Chanwoo Choi
2015-03-05  5:38 ` [PATCH v5 5/9] arm64: dts: exynos: Add RTC and ADC dt node for Exynos5433 SoC Chanwoo Choi
2015-03-05  5:38 ` [PATCH v5 6/9] arm64: dts: exynos: Add ADMA " Chanwoo Choi
2015-03-05  5:38 ` [PATCH v5 7/9] arm64: dts: exynos: Add I2S " Chanwoo Choi
2015-03-05  5:38 ` [PATCH v5 8/9] arm64: dts: exynos: Add TMU sensor " Chanwoo Choi
2015-03-05  5:38 ` [PATCH v5 9/9] arm64: dts: exynos: Add thermal-zones " Chanwoo Choi

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=54FE4957.7050904@samsung.com \
    --to=cw00.choi@samsung.com \
    --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).