From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kukjin Kim Subject: RE: kernel panic when booting on exynos 5440 Date: Mon, 05 Jan 2015 19:13:53 +0900 Message-ID: <035701d028d0$4ef0fff0$ecd2ffd0$@kernel.org> References: <549BE7CC.1000005@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailout2.samsung.com ([203.254.224.25]:28070 "EHLO mailout2.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753221AbbAEKOH (ORCPT ); Mon, 5 Jan 2015 05:14:07 -0500 Received: from epcpsbgr2.samsung.com (u142.gpu120.samsung.co.kr [203.254.230.142]) by mailout2.samsung.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0NHP00CTK8F7M820@mailout2.samsung.com> for linux-samsung-soc@vger.kernel.org; Mon, 05 Jan 2015 19:13:55 +0900 (KST) In-reply-to: Content-language: ko Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: 'Ming Lei' , 'Pankaj Dubey' Cc: linux-samsung-soc@vger.kernel.org, 'Kukjin Kim' , 'Russell King' , 'Thomas Abraham' , 'linux-arm-kernel' Ming Lei wrote: > > Hi Guys, > Hi, Sorry for late response. > On Thu, Dec 25, 2014 at 6:32 PM, Pankaj Dubey wrote: > > +CC: Thomas Abraham > > > > Hi Ming, > > > > On Thursday 25 December 2014 02:18 PM, Ming Lei wrote: > >> > >> Hi Pankaj, > >> > >> In your commit fce9e5bb2(ARM: EXYNOS: Add support for > >> mapping PMU base address via DT), 'pmu_base_addr' is > >> only parsed for very limited machines from the table of > >> 'exynos_dt_pmu_match'. For other boards, 'pmu_base_addr' > >> will keep its default value of null, then panic() is triggered. > >> > > > > Yes, it will. > > As exynos5440 DT does not have PMU device node, neither above mentioned > > patch added corresponding matching device_id. > > If I remember correctly, I might have missed this because exynos5440 DT was > > not having PMU node. > > > >> What do you think about the problem? > > > > > > I missed this part, and I should have taken care of this in original patch > > itself. Well as of now I can think of only one solution that if we really > > want to keep support for exynos5440 in mainline kernel, to avoid above issue > > we should skip pmu mapping for exynos5440. In this case following patch will > > do this work. > > > > Also I will like to know from Kukjin that what best can be done now. > > If he is OK with below solution I can post the same. > > > > --------------------------------------------------------------- > > > > Subject: [PATCH] ARM: EXYNOS: do not try to map PMU for exynos5440 > > > > Commit id: 2e94ac42898f84d76e3c21dd91bc is not taking care > > of mapping of exynos5440 PMU register which will result in kernel panic. > > As of now let's avoid mapping of exynos5440 PMU. > > > > Signed-off-by: Pankaj Dubey > > Is there any opportunity to merge the fix? Or exynos5440 will not be > supported in future? > Basically, I'm fine on the change like others for exynos5440 at this moment and if any other comments, I'll let you know on the patch in mailing list. Happy new year. Thanks, Kukjin From mboxrd@z Thu Jan 1 00:00:00 1970 From: kgene@kernel.org (Kukjin Kim) Date: Mon, 05 Jan 2015 19:13:53 +0900 Subject: kernel panic when booting on exynos 5440 In-Reply-To: References: <549BE7CC.1000005@samsung.com> Message-ID: <035701d028d0$4ef0fff0$ecd2ffd0$@kernel.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Ming Lei wrote: > > Hi Guys, > Hi, Sorry for late response. > On Thu, Dec 25, 2014 at 6:32 PM, Pankaj Dubey wrote: > > +CC: Thomas Abraham > > > > Hi Ming, > > > > On Thursday 25 December 2014 02:18 PM, Ming Lei wrote: > >> > >> Hi Pankaj, > >> > >> In your commit fce9e5bb2(ARM: EXYNOS: Add support for > >> mapping PMU base address via DT), 'pmu_base_addr' is > >> only parsed for very limited machines from the table of > >> 'exynos_dt_pmu_match'. For other boards, 'pmu_base_addr' > >> will keep its default value of null, then panic() is triggered. > >> > > > > Yes, it will. > > As exynos5440 DT does not have PMU device node, neither above mentioned > > patch added corresponding matching device_id. > > If I remember correctly, I might have missed this because exynos5440 DT was > > not having PMU node. > > > >> What do you think about the problem? > > > > > > I missed this part, and I should have taken care of this in original patch > > itself. Well as of now I can think of only one solution that if we really > > want to keep support for exynos5440 in mainline kernel, to avoid above issue > > we should skip pmu mapping for exynos5440. In this case following patch will > > do this work. > > > > Also I will like to know from Kukjin that what best can be done now. > > If he is OK with below solution I can post the same. > > > > --------------------------------------------------------------- > > > > Subject: [PATCH] ARM: EXYNOS: do not try to map PMU for exynos5440 > > > > Commit id: 2e94ac42898f84d76e3c21dd91bc is not taking care > > of mapping of exynos5440 PMU register which will result in kernel panic. > > As of now let's avoid mapping of exynos5440 PMU. > > > > Signed-off-by: Pankaj Dubey > > Is there any opportunity to merge the fix? Or exynos5440 will not be > supported in future? > Basically, I'm fine on the change like others for exynos5440 at this moment and if any other comments, I'll let you know on the patch in mailing list. Happy new year. Thanks, Kukjin