From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751858AbcFWIMt (ORCPT ); Thu, 23 Jun 2016 04:12:49 -0400 Received: from metis.ext.4.pengutronix.de ([92.198.50.35]:60403 "EHLO metis.ext.4.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751188AbcFWIMm (ORCPT ); Thu, 23 Jun 2016 04:12:42 -0400 Message-ID: <1466669559.2278.4.camel@pengutronix.de> Subject: Re: Problem with gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading From: Philipp Zabel To: Stanislav Meduna Cc: linux-kernel@vger.kernel.org, Dennis Gilmore Date: Thu, 23 Jun 2016 10:12:39 +0200 In-Reply-To: <164dd12f-cce7-911d-abaa-bf5daab40e6f@meduna.org> References: <164dd12f-cce7-911d-abaa-bf5daab40e6f@meduna.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:96de:80ff:fec2:9969 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stanislav, Am Mittwoch, den 22.06.2016, 19:43 +0200 schrieb Stanislav Meduna: > Hi, > > the c04e6e9 patch > > gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading > > broke display connected to a TQMa53 i.MX53 board. The lines > > imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops ipu_crtc_ops) > imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops ipu_crtc_ops) > > are not present anymore and the display shows random lines. > > I am using the 4.4.12-rt19+ kernel with some local changes, but > > the area of this patch is not touched by either. > > I am not sure whether my device tree is at fault (I am not > an expert here nor did I created the file from scratch) or the patch > does not take some special case into account. In any case > reverting the patch solves the problem for me. It's not your fault. Please update to 4.4.13 or apply commit 310944d148e3 ("drm/imx: Match imx-ipuv3-crtc components using device node in platform data"). That should fix this issue. See the patch description for more details. regards Philipp