Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp8685831ybi; Tue, 23 Jul 2019 13:07:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqyYDD7sNM6cZIt3wY1W7MVrXx6N17FRHL4y61Yll39jQFqQ2P4E4Ibc7tVqQCziOeGGUdrt X-Received: by 2002:a17:902:788f:: with SMTP id q15mr83615747pll.236.1563912434965; Tue, 23 Jul 2019 13:07:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563912434; cv=none; d=google.com; s=arc-20160816; b=0GmyyLYRCs/aMvi5rpWgodnbu8x+2QIwShF/g3gpjBQLGejLTePIiRyUMdRS/fkGLK wMgBoIkoc4i87VFjvT2wvnZxoC47e2BvCTB3+gYb6w+b/0dVqkGay06NHbFKj/nhZ+Ri ollpHbBI1cWIxibyS2lTaFSz+Q1hsIA5fno18L49qnIfU58YxtEOV27tDPRESkCDTJ5y SpA3jEyyPrZXjunsj1aLvze9bT3SpAQ51GFT9cvgrQZ/m5wB9IrVFwquvoVs4Qw5bNay 7tPlDpLvV/TaLEOxr5v2Lm8aztcVfkieODcN6khG/s7s0DApo5zUuFkQYxnQh9gr2DEb M7dg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=xO9+n+TBFjTj56cc+YFOO3yy4Ftkm15O45nOSvP97T0=; b=XgPasC/1n1Qn05Ny/KkFhw+PDhOSyMxJwQ3fwb4RbLZt9QZGHgRrF7R6fXcWEkUpGI t+0OVt8fYGIwwwkZPENdZLEbzBj4tMXLklJTkt7Bkhl38zam3UNwQh5GD4Hqc5J7xDuc fIsTI1hR7glPjRZnvP9LjWQvHw5XRp+B/fL2nPGU8wWgubJxi7vXrZsuxvp2ZFPDqRzA aX5OxJKNhfsxJfZjnFH3vMHQZkztdPPT80859GnmCnZYKIeYAPD8jY0JocxcigxWr2Tv DZHdz7VCiK8bTqL/bjcUT+EybLEeEmVpuRO/2oyF21Ytcv1NyDVDK02Z8jnraTG2jaY3 VOkA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r17si4441467pgo.125.2019.07.23.13.06.59; Tue, 23 Jul 2019 13:07:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389034AbfGWK3j (ORCPT + 99 others); Tue, 23 Jul 2019 06:29:39 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:47271 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389028AbfGWK3i (ORCPT ); Tue, 23 Jul 2019 06:29:38 -0400 Received: from lupine.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:1a17] helo=lupine) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1hps37-0005i0-8w; Tue, 23 Jul 2019 12:29:37 +0200 Message-ID: <1563877776.3731.3.camel@pengutronix.de> Subject: Re: [EXT] Re: [v1] gpu: ipu-v3: allow to build with ARCH_LAYERSCAPE From: Philipp Zabel To: Wen He , "linux-kernel@vger.kernel.org" , "dri-devel@lists.freedesktop.org" Cc: Leo Li Date: Tue, 23 Jul 2019 12:29:36 +0200 In-Reply-To: References: <20190508105755.5881-1-wen.he_1@nxp.com> <1562322724.4291.5.camel@pengutronix.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:1a17 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2019-07-09 at 03:11 +0000, Wen He wrote: [...] > > Thank you for the patch, but this does not seem right. > > ipuv3-crtc.c is part of DRM_IMX, which already depends on IMX_IPUV3_CORE. > > How did you manage to make it try to compile imxdrm? I assume the answer to my question is that you have removed the IMX_IPUV3_CORE dependency in the LS1028A BSP? > Thanks for the review, Philipp, > > NXP LS1028A platform use same Display IP with IMX8, so they have use same display > transmit controller drivers, config 'DRM_IMX' is used to support drm common drivers > on the NXP I.MX and LS1028A, display transmit controller is coming to plan upstream. Is it the i.MX8MQ DCSS or the i.MX8QM DPU that is shared with LS1028A? > Actually, we have done compile of the imxdrm on LS1028A BSP release. Can you point me changes that have been applied? It is still unclear to me how you managed to build imx-drm, unless you have removed the IMX_IPUV3_CORE dependency from DRM_IMX. > > Since LS1028A does not have the IPUv3, keeping this under COMPILE_TEST > > should be correct. > > Although LS1028A does not have the IPVv3, but DRM_IMX depends on it, LS1028A display > Transmit controller drivers also depends on DRM_IMX, so we need add this dependency to > solve the compile issue. The imx-drm driver is not suited to drive the i.MX8 display controllers. They should get their own drm drivers, as they have nothing in common with the i.MX5/6 IPU. There are no video capture capabilities, so they don't need the subsystem spanning driver layout, and without muxable shared encoders there is no need for the component design either. regards Philipp