From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751571AbbCJBbL (ORCPT ); Mon, 9 Mar 2015 21:31:11 -0400 Received: from mailout1.samsung.com ([203.254.224.24]:34616 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751083AbbCJBbH (ORCPT ); Mon, 9 Mar 2015 21:31:07 -0400 X-AuditID: cbfee68f-f791c6d000004834-49-54fe49588af9 Message-id: <54FE4957.7050904@samsung.com> Date: Tue, 10 Mar 2015 10:31:03 +0900 From: Chanwoo Choi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-version: 1.0 To: Mark Rutland Cc: Chanwoo Choi , "kgene@kernel.org" , Marc Zyngier , "arnd@arndb.de" , "olof@lixom.net" , Catalin Marinas , Will Deacon , "inki.dae@samsung.com" , "chanho61.park@samsung.com" , "sw0312.kim@samsung.com" , "jh80.chung@samsung.com" , "ideal.song@samsung.com" , "a.kesavan@samsung.com" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-samsung-soc@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v5 1/9] arm64: dts: exynos: Add dts files for 64-bit Exynos5433 SoC References: <1425533911-14800-1-git-send-email-cw00.choi@samsung.com> <1425533911-14800-2-git-send-email-cw00.choi@samsung.com> <20150305122459.GC14093@leverpostej> <20150305170450.GG14093@leverpostej> <20150305185407.GK14093@leverpostej> <54F9140B.3060109@samsung.com> <20150306114021.GF8700@leverpostej> <54F99B1A.3080600@samsung.com> In-reply-to: <54F99B1A.3080600@samsung.com> Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOIsWRmVeSWpSXmKPExsWyRsSkUDfC81+Iwc4eKYvHaxYzWfyddIzd 4v2yHkaLy/u1LZ4d1baYf+Qcq8Wuv/cZLSbdn8BiceNXG6tF/+PXzBabHl9jtbi8aw6bxYzz +4A67/xjs1h6/SKTxanrn4Fik1+yWbz8eILFQchjzbw1jB6/f01i9Ng56y67x6ZVnWwem5fU e1w50cTq0bdlFaPH501yARxRXDYpqTmZZalF+nYJXBkLHx9mKnjGUXF0SXoD40e2LkZODgkB E4mny5+yQNhiEhfurQeKc3EICSxllDh5eA1cUfeV84wQiUWMEkc29TNBOK8ZJa5dXMUIUsUr oCWxdOULZhCbRUBVov1VN5jNBhTf/+IG2CRRgTCJldOvsEDUC0r8mHwPzBYRUJfo2fWFBWQo s8BDNokpX/aBJYQFIiVO9fQxgdhCAi+YJb4vVwOxOQW0JQ78nQq2gFlAR2J/6zQ2CFteYvOa t8wggyQEVnJInL7yhRXiIgGJb5MPAQ3lAErISmw6wAzxmqTEwRU3WCYwis1CctMsJGNnIRm7 gJF5FaNoakFyQXFSepGxXnFibnFpXrpecn7uJkZg/J/+96x/B+PdA9aHGAU4GJV4eBlM/oUI sSaWFVfmHmI0BbpiIrOUaHI+MMnklcQbGpsZWZiamBobmVuaKYnzLpT6GSwkkJ5YkpqdmlqQ WhRfVJqTWnyIkYmDU6qBcfs0zoYLi3eF7fd/Vh5q4MO8fCELV7Xhcn3ewzOPR0/pfcOzQqyt Pr/Z5Z1QVeP6GTlRDuX2DBPTfP87SLT6HuhOeuWZdCLwxGYHh6Vhinb8iWHhhmeY3FrMLp88 dZrvqlX52Su9G+asuph6/nzk1cO2Fzv++rQd1D9XxHpvPW/R6t4m1UZvJZbijERDLeai4kQA 35Vx0foCAAA= X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrIKsWRmVeSWpSXmKPExsVy+t9jAd1wz38hBkvXGVk8XrOYyeLvpGPs Fu+X9TBaXN6vbfHsqLbF/CPnWC12/b3PaDHp/gQWixu/2lgt+h+/ZrbY9Pgaq8XlXXPYLGac 3wfUeecfm8XS6xeZLE5d/wwUm/ySzeLlxxMsDkIea+atYfT4/WsSo8fOWXfZPTat6mTz2Lyk 3uPKiSZWj74tqxg9Pm+SC+CIamC0yUhNTEktUkjNS85PycxLt1XyDo53jjc1MzDUNbS0MFdS yEvMTbVVcvEJ0HXLzAF6RUmhLDGnFCgUkFhcrKRvh2lCaIibrgVMY4Sub0gQXI+RARpIWMOY sfDxYaaCZxwVR5ekNzB+ZOti5OSQEDCR6L5ynhHCFpO4cG89UJyLQ0hgEaPEkU39TBDOa0aJ axdXgVXxCmhJLF35ghnEZhFQlWh/1Q1mswHF97+4ATZVVCBMYuX0KywQ9YISPybfA7NFBNQl enZ9YQEZyizwkE1iypd9YAlhgUiJUz19TCC2kMALZonvy9VAbE4BbYkDf6eCLWAW0JHY3zqN DcKWl9i85i3zBEaBWUh2zEJSNgtJ2QJG5lWMoqkFyQXFSem5RnrFibnFpXnpesn5uZsYwcnl mfQOxlUNFocYBTgYlXh4GUz+hQixJpYVV+YeYpTgYFYS4ZXQAgrxpiRWVqUW5ccXleakFh9i NAUGwURmKdHkfGDiyyuJNzQ2MTOyNDI3tDAyNlcS51WybwsREkhPLEnNTk0tSC2C6WPi4JRq YEy8d33NPmeNcvNTb0yPHFv+qav6/hw37WP9s8Qj8hfvdc66YnGx6I5sRcajAPvy8Nnevp6z Njm+SoycX1u+1Wz+4b2/Hn94sZAleQPnCYkdU+12td7WOf/ji0KO2MUksX+rk2+saklQ5/n9 2zrkYvpf7dK8G7cjIs4s2hYWv7D494NGl/iUbl4lluKMREMt5qLiRABLeNrzRAMAAA== DLP-Filter: Pass X-MTR: 20000000000000000@CPGS X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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