From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752732AbbC0Oee (ORCPT ); Fri, 27 Mar 2015 10:34:34 -0400 Received: from bhuna.collabora.co.uk ([93.93.135.160]:39410 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752210AbbC0Oed (ORCPT ); Fri, 27 Mar 2015 10:34:33 -0400 Message-ID: <55156A73.7060802@collabora.co.uk> Date: Fri, 27 Mar 2015 15:34:27 +0100 From: Javier Martinez Canillas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0 MIME-Version: 1.0 To: Krzysztof Kozlowski CC: Kukjin Kim , Olof Johansson , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Marek Szyprowski , Doug Anderson , Andrzej Hajda , linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/1] Revert "ARM: dts: add display power domain for exynos5250" References: <1427107800-21668-1-git-send-email-javier.martinez@collabora.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Krzysztof, On 03/27/2015 03:29 PM, Krzysztof Kozlowski wrote: > 2015-03-23 11:49 GMT+01:00 Javier Martinez Canillas > > I looked at the DP and FIMD drivers and with great help of Andrzej > Hajda found the issue: the FIMD driver does not enable DP clock > (DP_MIE_CLKCON register). The process looks like: > 1. Bootloader sets the DP_MIE_CLKCON to proper value. > 2. FIMD is probed, DP power domain is on. > 3. FIMD is deffered, DP power domain is turned off. > 4. The FIMD registers are reset so DP clock is turned off. > 5. DP driver is probed, DP power domain is turned on but clock is not enabled. > Great! I knew it was some setup missing that was made by the boot-loader. > I'll do some more testing and sent a patch for it till end of Monday > so I think we should not revert this commit. > Agree, I of course preferred to fix the actual cause instead of relying on the boot-loader to do the initialization but I wasn't able to figure it out so I posted this patch to revert the commit in the meantime. > Best regards, > Krzysztof > Best regards, Javier