linux-kernel - Re: Linux-next, Exynos Octa boot fail, bisected to: "drm/exynos: remove drm_iommu_attach_device_if

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <55AEF9AD.6090709@samsung.com>
Date:	Wed, 22 Jul 2015 11:02:21 +0900
From:	Joonyoung Shim <jy0922.shim@...sung.com>
To:	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	Inki Dae <inki.dae@...sung.com>,
	Seung-Woo Kim <sw0312.kim@...sung.com>
Cc:	dri-devel@...ts.freedesktop.org,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Kukjin Kim <kgene@...nel.org>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: Linux-next, Exynos Octa boot fail,
 bisected to: "drm/exynos: remove drm_iommu_attach_device_if_possible"

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 <jy0922.shim@...sung.com>
> 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 <jy0922.shim@...sung.com>
>     Tested-by: Marek Szyprowski <m.szyprowski@...sung.com>
>     Signed-off-by: Inki Dae <inki.dae@...sung.com>
> 
> :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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/