From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753449AbbDNHyM (ORCPT ); Tue, 14 Apr 2015 03:54:12 -0400 Received: from mailout3.samsung.com ([203.254.224.33]:55458 "EHLO mailout3.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751650AbbDNHx7 (ORCPT ); Tue, 14 Apr 2015 03:53:59 -0400 X-AuditID: cbfee691-f79ca6d00000456a-d6-552cc77f068e Message-id: <552CC77F.10801@samsung.com> Date: Tue, 14 Apr 2015 16:53:35 +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 , "kgene@kernel.org" Cc: "arnd@arndb.de" , "olof@lixom.net" , Marc Zyngier , 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 v7 1/9] arm64: dts: exynos: Add dts files for 64-bit Exynos5433 SoC References: <1426637856-3730-1-git-send-email-cw00.choi@samsung.com> <1426637856-3730-2-git-send-email-cw00.choi@samsung.com> <20150330160940.GA13731@leverpostej> <5519E2B6.2030905@samsung.com> <20150402173558.GB30669@leverpostej> <551DD321.6030707@samsung.com> <20150407102523.GA23190@leverpostej> <20150413105618.GD4076@leverpostej> <552BB14A.6010205@samsung.com> <20150413154949.GI4076@leverpostej> In-reply-to: <20150413154949.GI4076@leverpostej> Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPIsWRmVeSWpSXmKPExsWyRsSkRLfhuE6owacdTBaP1yxmsvg76Ri7 xftlPYwWl/drW8w/co7VYtff+4wWk+5PYLG48auN1aL/8Wtmi02Pr7FaXN41h81ixvl9QF13 /rFZLL1+kcni1PXPQLHJL9ksXn48weIg6LFm3hpGj9+/JjF6bFrVyeaxeUm9x5UTTawefVtW MXp83iQXwB7FZZOSmpNZllqkb5fAlXGx/ylLwTKeivnbmhkbGJ9wdjFycEgImEgc+xjbxcgJ ZIpJXLi3nq2LkYtDSGApo8TW1vesEAkTiaPbf0ElFjFKPJ18jwnCecAose/xIUaQKl4BDYkT u06CdbAIqErMv/ONBcRmE9CS2P/iBhuILSoQJrFy+hUWiHpBiR+T74HZIgJ+EhMnLGMBGcos MJVNYtWe22BDhQUiJd7vX88CsW02s8TFtj6wSZwCBhIHz/SAdTML6Ejsb53GBmHLS2xe85YZ pEFCYC6HxKez/SwQJwlIfJt8iAXiaVmJTQeYIX6TlDi44gbLBEaxWUiOmoVk7CwkYxcwMq9i FE0tSC4oTkovMtUrTswtLs1L10vOz93ECIz30/+eTdzBeP+A9SFGAQ5GJR7eEz46oUKsiWXF lbmHGE2BrpjILCWanA9MKnkl8YbGZkYWpiamxkbmlmZK4rw60j+DhQTSE0tSs1NTC1KL4otK c1KLDzEycXBKNTDyxQs9ebbxw1EDydWBGg1lbScbtjT52nXc6HO6vXfPXneeIJfjDq1FwTdc bryTu/l5yUPFhpJGTy/TyUt3Gk3uN+kvnL9ia+4VhWzrgptirI9K3aYqXdlSsENlyb+yID2h 2mlCFWlc+xTa9f+cTfVil7I4wh1xbdqBnu13LKdMLolwyJaafEyJpTgj0VCLuag4EQCEIYMG 8gIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFKsWRmVeSWpSXmKPExsVy+t9jAd364zqhBoeazCwer1nMZPF30jF2 i/fLehgtLu/Xtph/5Byrxa6/9xktJt2fwGJx41cbq0X/49fMFpseX2O1uLxrDpvFjPP7gLru /GOzWHr9IpPFqeufgWKTX7JZvPx4gsVB0GPNvDWMHr9/TWL02LSqk81j85J6jysnmlg9+ras YvT4vEkugD2qgdEmIzUxJbVIITUvOT8lMy/dVsk7ON453tTMwFDX0NLCXEkhLzE31VbJxSdA 1y0zB+gDJYWyxJxSoFBAYnGxkr4dpgmhIW66FjCNEbq+IUFwPUYGaCBhDWPGxf6nLAXLeCrm b2tmbGB8wtnFyMkhIWAicXT7LzYIW0ziwr31QDYXh5DAIkaJp5PvMUE4Dxgl9j0+xAhSxSug IXFi10lWEJtFQFVi/p1vLCA2m4CWxP4XN8AmiQqESaycfoUFol5Q4sfke2C2iICfxMQJy1hA hjILTGWTWLXnNthQYYFIiff717NAbJvNLHGxrQ9sEqeAgcTBMz1g3cwCOhL7W6exQdjyEpvX vGWewCgwC8mSWUjKZiEpW8DIvIpRNLUguaA4KT3XUK84Mbe4NC9dLzk/dxMjOJ08k9rBuLLB 4hCjAAejEg/vCR+dUCHWxLLiytxDjBIczEoivEGHgUK8KYmVValF+fFFpTmpxYcYTYFhMJFZ SjQ5H5jq8kriDY1NzIwsjcwNLYyMzZXEeefoyoUKCaQnlqRmp6YWpBbB9DFxcEo1MIY3yRfK O6xVNtP8dOzntnJPpQTh/xd0t1YEd31yTYupnN9nrn/iSvuud+Y3OZ8572/yWDPxksXZ9/d1 V8R/27ZFQ8FYXPmhQWt0r98ijTe/JBYc62A6bmOata+gQWGphKnhJM4VpXJvEqw51Ft0MkQu ejDJWqTJiC3iFeA84jJv1i/nUw8ZlFiKMxINtZiLihMBlvNbvT0DAAA= 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 Kukjin and Mark, On 04/14/2015 12:49 AM, Mark Rutland wrote: >>>>>> So NAK to the PSCI node and PSCI enable method in this dts until we >>>>>> either have a working firmware, or a reasonable mechanism to handle the >>>>>> deficiency. >>>>> >>>>> There is only CPU0 hotplug issue. Excpet CPU{1-7} are well working. >>>> >>>> I understand that, but the issue with CPU0 is still a blocker from my >>>> PoV. >>>> >>>>> To fix this issue, we must need the help of firmware developer. >>>>> But, We never get the any help. >>>> >>>> Previously dyou said that you did not have access to the source code >>>> rather than not having help from the relevant firmware engineers. I take >>>> it you have informed them of the issue with CPU0? >> >> I didn't ask any help to firmware engineer because I didn't know who firmware engineer >> and also didn't access the source code. If I knew the engineer and can access them, >> I would have asked some help to them or inquired the reason about CPU0 not hotplugged. > > You must have acquired the firmware (or board(s) with the firmware > preloaded) from somewhere. Surely you can work backwards from there to > file a bug report and/or inquire as to who you need to speak to... As you commented, I got the board that firmware was preloaded. Unfortunately, I didn't know the any routine to contact firmware developer and developer about SoC design. Dear Kukjin, I need your help about CPU0 issue of Exynos SoC. Could you answer why CPU0 cannot be hotplugged on Exynos SoC? Thanks, Chanwoo Choi