Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751937AbdFOH2S (ORCPT ); Thu, 15 Jun 2017 03:28:18 -0400 Received: from fllnx210.ext.ti.com ([198.47.19.17]:62046 "EHLO fllnx210.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750814AbdFOH2R (ORCPT ); Thu, 15 Jun 2017 03:28:17 -0400 Subject: Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900 To: Aaro Koskinen , Tomi Valkeinen , Tony Lindgren , , , References: <20170614221133.k7gmbzzjsbmbjgbc@darkstar.musicnaut.iki.fi> From: Peter Ujfalusi Message-ID: Date: Thu, 15 Jun 2017 10:28:31 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170614221133.k7gmbzzjsbmbjgbc@darkstar.musicnaut.iki.fi> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1479 Lines: 39 On 2017-06-15 01:11, Aaro Koskinen wrote: > Hi, > > When booting v4.12-rc5 on Nokia N900, omapdrm fails to probe and there > is no display. > > Bisected to: > > a09d2bc1503508c17ef3a71c6b1905e3660f3029 is the first bad commit > commit a09d2bc1503508c17ef3a71c6b1905e3660f3029 > Author: Peter Ujfalusi > Date: Tue May 3 22:08:01 2016 +0300 > > drm/omap: Use omapdss_stack_is_ready() to check that the display stack is up > > Instead of 'guessing' based on aliases of the status of the DSS drivers, > use the new interface to check that all needed drivers are loaded. > In this way we can be sure that all needed drivers are loaded so it is > safe to continue the probing of omapdrm. > This method will allow the omapdrm to be probed 'headless', without > outputs. > > Signed-off-by: Peter Ujfalusi > Signed-off-by: Tomi Valkeinen > > Reverting the commit seems to fix the issue. When you revert this patch do you see a warning saying: "could not connect display: blah" ? if so what is 'blah'? n900 have two displays afaik, LCD and TVout. omapdss_stack_is_ready() is to ensure that we have all the drivers loaded for both displays, while by reverting it it is enough if one of them is loaded at the time we do the check and omapdrm would continue to probe, but the missing display (even if it is going to be probed a bit later) will not work. - P?ter