From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753254AbbCFCm0 (ORCPT ); Thu, 5 Mar 2015 21:42:26 -0500 Received: from mailout4.samsung.com ([203.254.224.34]:28320 "EHLO mailout4.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751763AbbCFCmW (ORCPT ); Thu, 5 Mar 2015 21:42:22 -0500 X-AuditID: cbfee691-f79b86d000004a5a-33-54f9140c2331 Message-id: <54F9140B.3060109@samsung.com> Date: Fri, 06 Mar 2015 11:42:19 +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> In-reply-to: <20150305185407.GK14093@leverpostej> Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBIsWRmVeSWpSXmKPExsWyRsSkQJdH5GeIwelODovHaxYzWfyddIzd 4v2yHkaLy/u1LZ4d1baYf+Qcq8Wuv/cZLSbdn8BiceNXG6tF/+PXzBabHl9jtbi8aw6bxYzz +4A67/xjs1h6/SKTxanrn4Fik1+yWbz8eILFQchjzbw1jB6/f01i9Ng56y67x6ZVnWwem5fU e1w50cTq0bdlFaPH501yARxRXDYpqTmZZalF+nYJXBnXj1xmLtgkUvF/3VnGBsZj/F2MHBwS AiYS79oUuhg5gUwxiQv31rN1MXJxCAksZZS4tXITM0TCRGLT9dusEInpjBKNN69BOa8ZJTa3 fWIFqeIV0JLYcPE6C4jNIqAqcaHjEpjNBhTf/+IGG4gtKhAmsXL6FRaIekGJH5PvgdkiAuoS Pbu+sIAMZRZ4yCYx5cs+sISwQKTEqZ4+JohtLcwSp3b8BktwChhKXGp+ATaVWUBHYn/rNChb XmLzmrfMIA0SAis5JNZd+8cIcZKAxLfJh1ggnpaV2HQA6jdJiYMrbrBMYBSbheSoWUjGzkIy dgEj8ypG0dSC5ILipPQiU73ixNzi0rx0veT83E2MwARw+t+ziTsY7x+wPsQowMGoxMOrIfgz RIg1say4MvcQoynQFROZpUST84FpJq8k3tDYzMjC1MTU2Mjc0kxJnFdH+mewkEB6Yklqdmpq QWpRfFFpTmrxIUYmDk6pBsZD1jde1DyVUGgSd/glfmRbo0Rr490+5hP3Cx0bgtINr8yq65Ka 9L4nO+LcNaXY+Ed6/sImWx4ufSjLxlSRzHe09oPSqqCcLZzXfi+9ZhJ0cfN7Hg/VibrBllEV nK8bumRFl2fMmHFtn2HhFKOipJLXjPujP5zyb3mza+WMD7lxcztsEngf3FRiKc5INNRiLipO BADi2d+n+wIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMKsWRmVeSWpSXmKPExsVy+t9jQV1ukZ8hBucWWls8XrOYyeLvpGPs Fu+X9TBaXN6vbfHsqLbF/CPnWC12/b3PaDHp/gQWixu/2lgt+h+/ZrbY9Pgaq8XlXXPYLGac 3wfUeecfm8XS6xeZLE5d/wwUm/ySzeLlxxMsDkIea+atYfT4/WsSo8fOWXfZPTat6mTz2Lyk 3uPKiSZWj74tqxg9Pm+SC+CIamC0yUhNTEktUkjNS85PycxLt1XyDo53jjc1MzDUNbS0MFdS yEvMTbVVcvEJ0HXLzAF6RUmhLDGnFCgUkFhcrKRvh2lCaIibrgVMY4Sub0gQXI+RARpIWMOY cf3IZeaCTSIV/9edZWxgPMbfxcjJISFgIrHp+m1WCFtM4sK99WxdjFwcQgLTGSUab15jhXBe M0psbvsEVsUroCWx4eJ1FhCbRUBV4kLHJTCbDSi+/8UNNhBbVCBMYuX0KywQ9YISPybfA7NF BNQlenZ9YQEZyizwkE1iypd9YAlhgUiJUz19TBDbWpglTu34DZbgFDCUuNT8Amwqs4COxP7W aVC2vMTmNW+ZJzAKzEKyZBaSsllIyhYwMq9iFE0tSC4oTkrPNdIrTswtLs1L10vOz93ECE4w z6R3MK5qsDjEKMDBqMTDqyH4M0SINbGsuDL3EKMEB7OSCO8mXqAQb0piZVVqUX58UWlOavEh RlNgGExklhJNzgcmv7ySeENjEzMjSyNzQwsjY3MlcV4l+7YQIYH0xJLU7NTUgtQimD4mDk4p YKpoltXIl/7XltX7YfsC6d87gg4yWHhsdtse8rS0Q/1+0aMvHzuvc25frSfQxlfD+L1y5eHk w8l1G7lvXKtiSL/DKMlT0rSss7Fn0yv5sF1NVVWvNCTXKT7YuPFKpvkngxtfvt8+KbKUP9Wm 3ldj2a0LOr/najef2TnlXpT0StZzr2Z4pDxIPK/EUpyRaKjFXFScCACDIkWiRgMAAA== 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, On 03/06/2015 03:54 AM, Mark Rutland wrote: > Hi, > >>>>>> + psci { >>>>>> + compatible = "arm,psci"; >>>>>> + method = "smc"; >>>>>> + cpu_off = <0x84000002>; >>>>>> + cpu_on = <0xC4000003>; >>>>>> + }; >>>>> >>>>> Back at v2 you mentioned that CPU_OFF wasn't working [1]. >>>>> >>>>> Do both CPU_ON and CPU_OFF work for all CPUs, including the boot CPU? >>>> >>>> The CPU1 ~ CPU7 are well woking about CPU_ON/OFF. >>>> CPU0 (boot CPU) is only well working for CPU_OFF. >>>> But when I try to turn on the CPU0 after CPU_OFF, I failed it. >>> >>> That's rather worrying. Can you look into what's going on here? I'd >>> rather not have dts describing things which are known to be broken. >> >> The board dts don't include any node for CPU_ON/OFF. > > I don't understand. The CPU_ON and CPU_OFF IDs are in the psci node > quoted above, and all the CPUs had enable-method = "psci". I mean that there are not additional dt node except for 'cpu' and 'psci' node. > >> When I try to turn on the CPU0 (boot CPU), fail to turn on and lockup happen. >> After lockup happen, I cannot use the console. > > That sounds like a pretty major bug. > > Are you able to investigate with a hardware debugger? I can't do because there are not any jtag connector. > > Do other CPUs eventually log errors regarding the lockup? Or is the > machine completely dead from this point on? I tested CPU0 on/off. When I turn on the CPU0, I fail it. But, kernel just show the error log without lockup. I gave you wrong infromation about CPU0 off. [test result of CPU0 on/off on Linux 4.0-rc2] root@localhost:~# echo 0 > /sys/devices/system/cpu/cpu0/online [ 420.965435] IRQ1 no longer affine to CPU0 [ 420.965439] IRQ2 no longer affine to CPU0 [ 4631.194227] CPU0: shutdown root@localhost:~# echo 1 > /sys/devices/system/cpu/cpu0/online [ 1164.601644] CPU0: failed to come online -bash: echo: write error: Input/output error As I experienced, Exynos SoC could not turn off the CPU0 (boot cpu). I think that we may need the hidden information of Exynos5433 from Exynos5433 architector. > >>>>> 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? Thanks, Chanwoo Choi