Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932342AbbGVCC3 (ORCPT ); Tue, 21 Jul 2015 22:02:29 -0400 Received: from mailout1.samsung.com ([203.254.224.24]:38032 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754998AbbGVCC1 (ORCPT ); Tue, 21 Jul 2015 22:02:27 -0400 X-AuditID: cbfee68e-f79c56d000006efb-cd-55aef9a7d6d6 Message-id: <55AEF9AD.6090709@samsung.com> Date: Wed, 22 Jul 2015 11:02:21 +0900 From: Joonyoung Shim User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-version: 1.0 To: Krzysztof Kozlowski , Inki Dae , Seung-Woo Kim Cc: dri-devel@lists.freedesktop.org, Kyungmin Park , Kukjin Kim , linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Marek Szyprowski Subject: Re: Linux-next, Exynos Octa boot fail, bisected to: "drm/exynos: remove drm_iommu_attach_device_if_possible" References: In-reply-to: Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKIsWRmVeSWpSXmKPExsWyRsSkUHfFz3WhBpP/M1pc+fqezWLS/Qks Fq9fGFr0P37NbHG26Q27xeVdc9gsZpzfx2Sx9shddosZk1+yOXB6bFrVyeZxv/s4k0ffllWM Hp83yQWwRHHZpKTmZJalFunbJXBl7O5pZC7Yw1PxbfI21gbGaVxdjJwcEgImEuumrmeEsMUk Ltxbz9bFyMUhJLCUUWL9zONACQ6woh1zAiDi0xkl5iyaxArhPGCU2PV8PRNIN6+AlkTbojcs IA0sAqoS85bLgoTZBPQk7mw7DlYiKhAmcWZGBwtEuaDEj8n3wGwRgRqJ7tYzYDOZBe4zSjQ2 zWAGSQgLlEvc3f4HzBYSCJB4+HgjO4jNKRAsMeXfL7DjmIEW3L+oBRJmFpCX2LzmLTPIHAmB a+wS0862gvWyCAhIfJt8iAXiGVmJTQeYIR6WlDi44gbLBEaxWUhOmoUwdRaSqQsYmVcxiqYW JBcUJ6UXGekVJ+YWl+al6yXn525iBMbe6X/P+nYw3jxgfYhRgINRiYd3wtF1oUKsiWXFlbmH GE2BjpjILCWanA+M8LySeENjMyMLUxNTYyNzSzMlcd4EqZ/BQgLpiSWp2ampBalF8UWlOanF hxiZODilGhinO3beOJ+gUBKwrnSp2AdO9YOaB7mOKbw0dCv5Lu2+WvJ1ZGDy4fnc7yuXNS39 dnnrqTvtHS1bTMzTyzm+FkYvicneWmLk71D4rKLNf0rmOcOjk3+U/mAt9XnAWnKN/eMVnnPf H6bPkZrHf///vfXlzw6/TXt2J8tw8b3JTHvuHOlhabycsjtWiaU4I9FQi7moOBEAS2am4rgC AAA= X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsVy+t9jQd3lP9eFGjx6Y2lx5et7NotJ9yew WLx+YWjR//g1s8XZpjfsFpd3zWGzmHF+H5PF2iN32S1mTH7J5sDpsWlVJ5vH/e7jTB59W1Yx enzeJBfAEtXAaJORmpiSWqSQmpecn5KZl26r5B0c7xxvamZgqGtoaWGupJCXmJtqq+TiE6Dr lpkDdIuSQlliTilQKCCxuFhJ3w7ThNAQN10LmMYIXd+QILgeIwM0kLCGMWN3TyNzwR6eim+T t7E2ME7j6mLk4JAQMJHYMSegi5ETyBSTuHBvPVsXIxeHkMB0Rok5iyaxQjgPGCV2PV/PBFLF K6Al0bboDQtIM4uAqsS85bIgYTYBPYk7246DlYgKhEmcmdHBAlEuKPFj8j0wW0SgRqK79QzY TGaB+4wSjU0zmEESwgLlEne3/wGzhQQCJB4+3sgOYnMKBEtM+feLEWQXM9CC+xe1QMLMAvIS m9e8ZZ7AKDALyYpZCFWzkFQtYGRexSiaWpBcUJyUnmukV5yYW1yal66XnJ+7iREc2c+kdzCu arA4xCjAwajEwzvh6LpQIdbEsuLK3EOMEhzMSiK8S08AhXhTEiurUovy44tKc1KLDzGaAv0/ kVlKNDkfmHTySuINjU3MjCyNzA0tjIzNlcR5T+b7hAoJpCeWpGanphakFsH0MXFwSjUwitzo U30o13Ekat8pw0j3opK5v/MFOnj+CxWmJSxkOxv0wLFuikDjFCedG3bbVkftEi1hd/ru8qfz pW5r8hNekdcrnfn+zZh8P/Mh91+jwJt6WaZZ9ZsWyBiWOd//spD31dwLc03Pd/8yMM4pbXh/ aXLtwb26pvNy5GfU3FVw/LfLobNu58ePSizFGYmGWsxFxYkAaL7lMgIDAAA= 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 Content-Length: 1799 Lines: 47 On 07/21/2015 10:19 PM, Krzysztof Kozlowski wrote: > Hi, > > Today's linux-next (next-20150721) encounters boot failures on Exynos > Octa (Exynos5422) based boards. The boards hangs. I bisected it to: > > d80167b85024982c5f18d0481a5c248100360118 is the first bad commit > commit d80167b85024982c5f18d0481a5c248100360118 > Author: Joonyoung Shim > Date: Thu Jul 2 21:49:39 2015 +0900 > > drm/exynos: remove drm_iommu_attach_device_if_possible > > Already drm_iommu_attach_device checks whether support iommu internally. > It should clear channels always regardless iommu support. We didn't know > because we can detect the problem when iommu is enabled, so we don't > have to use drm_iommu_attach_device_if_possible and then we can remove > drm_iommu_attach_device_if_possible and clear_channels function pointer. > > Signed-off-by: Joonyoung Shim > Tested-by: Marek Szyprowski > Signed-off-by: Inki Dae > > :040000 040000 83379efbf4960f58d680371628ec04387935bd53 > da03c338b88e7cb6bda895b3dd52d78d9b6eba30 M drivers > > > Config: exynos > Boot log from Odroid XU3-Lite attached. > > Any hints or ideas? The point that hangs is when accesses fimd register in fimd_clear_channels function, so i doubt clock setting for fimd. It's gone something that hangs after i enable gating for ACLK_200_DISP1 clock. If ACLK_200_DISP1 clock needs for fimd really, i'm thinking how can it support. Any ideas? Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/