From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 78861C79FA1 for ; Mon, 7 Sep 2026 15:36:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=cKCcNYkaZjDiohl090R5VHc/svuq+q9Fh8r6JrWL67U=; b=XZzboKyt5RthloiQr54TEUX2Ta xAfVIEkHGAo6DPrAU6OT0SEshMVO8YhgJQxOY3Yb5lgBrTnb3nnU9YxOXYcaI0ii09wRrtMdd06Xp +de94IWu/rKszzVhPlZOIsVIODoV1v1W84b3N3ROG4e9WzucLgcZE+DL/EBTkkr3bynUJwlruyf0B g0nOVGDWgQjXYrshvihFHqh7Ila6qQ4ePPCB1C5iqfBrrZDe0MvhV4EskAh87z9y8m7Q3EfpFysL/ YG2QNIKTeoG26Q3C+l8LCaDocP4QCmxP0LCXc2AZ/KBUy3kIWa2Is/kVzZ+chUkaKZ2w8IIHvPc4I z5U3bJxQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1x3bOw-00000007BcQ-0KVQ; Mon, 07 Sep 2026 15:36:54 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1x3bOu-00000007Bc6-3Jve; Mon, 07 Sep 2026 15:36:52 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 2384660D89; Mon, 7 Sep 2026 15:36:52 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 498E41F00A3A; Mon, 7 Sep 2026 15:36:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1788795411; bh=otIPJu+TzkOj3mNvPJg4bU2oZNf1j9J+ix1n6UG32WI=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=NeSlAWVsyypsF4hIil2ed2Y5sOHsUJrCS5HlU19as33dem4Pdr0UdPoHoFUbwTgKA OQdN2pZRQmlRgXnQyDdPlyXEhJk+QYiYKoX9lXeSNFl9OjhP6UCiaWZnbXSkZImlBt JmaQAktGIkLi+hKjDotKvTyfNLcsiU10gjkcszuPvXzTksdsm8nXze25H5nGg3xdxV VFLamu1kpet4ovM6g9fJhgzVrW7ma8RceLuoqDOtQ949WC8+Kjnkh5N3IJkjK9KYnm kYc87Gw+us1qpnW4rpDKRAEbsiGVkcxQmJYP9U28s5Ng+7RcYdLsSVazIJoLH3Nysr zM6jGpm6Y5g2A== Date: Mon, 7 Sep 2026 17:36:47 +0200 From: Maxime Ripard To: Liu Ying Cc: Francesco Dolcini , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org, p.zabel@pengutronix.de, airlied@gmail.com, simona@ffwll.ch, maarten.lankhorst@linux.intel.com, tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com, tglx@linutronix.de, vkoul@kernel.org, kishon@kernel.org, Frank.Li@nxp.com, lumag@kernel.org, aisheng.dong@nxp.com, agx@sigxcpu.org, u.kleine-koenig@baylibre.com, marek.vasut@mailbox.org Subject: Re: [PATCH v9 00/19] Add Freescale i.MX8qxp Display Controller support Message-ID: References: <20250414035028.1561475-1-victor.liu@nxp.com> <20260714193627.GA9616@francesco-nb> <20260716062612.GC9973@francesco-nb> MIME-Version: 1.0 In-Reply-To: X-BeenThere: linux-phy@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux Phy Mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1557353379821013956==" Sender: "linux-phy" Errors-To: linux-phy-bounces+linux-phy=archiver.kernel.org@lists.infradead.org --===============1557353379821013956== Content-Type: multipart/signed; micalg=pgp-sha384; protocol="application/pgp-signature"; boundary="nzpfrxwi4i53nnqx" Content-Disposition: inline --nzpfrxwi4i53nnqx Content-Type: text/plain; protected-headers=v1; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH v9 00/19] Add Freescale i.MX8qxp Display Controller support MIME-Version: 1.0 On Fri, Sep 04, 2026 at 04:49:19PM +0800, Liu Ying wrote: > On Fri, Sep 04, 2026 at 10:38:08AM +0200, Maxime Ripard wrote: > > On Fri, Sep 04, 2026 at 04:10:07PM +0800, Liu Ying wrote: > > > Hi Maxime, > > >=20 > > > On Thu, Sep 03, 2026 at 03:41:15PM +0200, Maxime Ripard wrote: > > > > On Thu, Jul 16, 2026 at 02:49:14PM +0800, Liu Ying wrote: > > > > > On Thu, Jul 16, 2026 at 08:26:12AM +0200, Francesco Dolcini wrote: > > > > > > On Thu, Jul 16, 2026 at 02:21:31PM +0800, Liu Ying wrote: > > > > > > > On Tue, Jul 14, 2026 at 09:36:27PM +0200, Francesco Dolcini w= rote: > > > > > > > > On Mon, Apr 14, 2025 at 11:50:09AM +0800, Liu Ying wrote: > > > > > > > > > Hi, > > > > > > > > >=20 > > > > > > > > > This patch series aims to add Freescale i.MX8qxp Display = Controller support. > > > > > > > > >=20 > > > > > > > > > The controller is comprised of three main components that= include a blit > > > > > > > > > engine for 2D graphics accelerations, display controller = for display output > > > > > > > > > processing, as well as a command sequencer. > > > > > > > >=20 > > > > > > > > ... > > > > > > > >=20 > > > > > > > > >=20 > > > > > > > > > To follow up i.MX8qxp TRM, I changed the controller name = to "Display Controller" > > > > > > > > > instead of the previous "DPU". "DPU" is only mentioned i= n the SoC block > > > > > > > > > diagram and represents the whole display subsystem which = includes the display > > > > > > > > > controller and prefech engines, etc. > > > > > > > > >=20 > > > > > > > > > With an additional patch[1] for simple-pm-bus.c, this ser= ies facilitates > > > > > > > > > testing a LVDS panel on i.MX8qxp MEK. > > > > > > > > >=20 > > > > > > > > > Please do NOT merge patch 14-19. They are only used to f= acilitate testing > > > > > > > > > the LVDS panel. > > > > > > > >=20 > > > > > > > > What's the plan to conclude this work? What's the latest st= atus? > > > > > > > > I am looking forward to have a way to use the i.MX8QXP disp= lay with > > > > > > > > mainline, but to my understanding some required changes on = the SOC dtsi > > > > > > > > are not merged. > > > > > > > >=20 > > > > > > > > Can you help? > > > > > > >=20 > > > > > > > I planned to add display controller DT node after prefetch en= gine support [1] > > > > > > > is picked up so that the prefetch engine could be enabled tog= ether with the > > > > > > > display controller. Just want to avoid a DT that only enable= s the display > > > > > > > controller or bypasses the prefetch engine. It makes the dis= play controller > > > > > > > driver simpler. > > > > > > >=20 > > > > > > > [1] https://lore.kernel.org/all/20251027-imx8-dc-prefetch-v5-= 0-4ecb6c6d4941@nxp.com/ > > > > > >=20 > > > > > > That series is from October 2025, is there anything blocking to= move it > > > > > > forward? > > > > >=20 > > > > > It lacks a Reviewed-by tag(at least a Acked-by tag) from a drm-mi= sc committer > > > > > for every driver patch in that series. Also, it seems that Marek= (Cc'ed) is > > > > > not a big fan of [1](See i.MX95 display support discussion[2]). > > > >=20 > > > > I was just pointed at this series, and I'm not sure why it's blocke= d. It > > > > looks like you were waiting for a Reviewed-by by a drm-misc maintai= ner, > > > > but I gave mine already and I'm a drm-misc maintainer, sooo... :) > > >=20 > > > Your Reviewed-by tags were on the initial i.MX8qxp Display Controller= driver > > > patches. And, those patches have already landed. > > >=20 > > > Now, I'm waiting for Acked-by or Reviewed-by tags on those driver pat= ches > > > which add i.MX8qxp Display Controller *prefetch engines* support. > > > 'b4 trailers -u' doesn't include any Reviewed-by from you on those pa= tches... > > > I sent v6 prefetch engine patch series[1] just now. > > > It would be great to have your Acked-by or Reviewed-by tags on those = driver > > > patches :) > >=20 > > It looks like you had a reviewed-by by someone on all these patches > > already, so you could have merged them. >=20 > Oh, okay. I *thought* one merge criteria is at least one Acked-by from a > drm-misc committer on each driver patch by reading the guildlines[1]. > But now I've got the idea. Thanks. >=20 > [1] https://drm.pages.freedesktop.org/maintainer-tools/committer/committe= r-drm-misc.html For a driver, it's totally enough to have a reviewed-by by someone with experience with the driver too. Maxime --nzpfrxwi4i53nnqx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iJUEABMJAB0WIQTkHFbLp4ejekA/qfgnX84Zoj2+dgUCap7aDwAKCRAnX84Zoj2+ doeCAX9T+LgYMTWQNSla28ip6yR0qM88eain+6vQBAG1kI/IdbDa9glAvdQEOOTv fXTYoEIBf3QACWC1uGpzItuPa9Zyaak4mtnpldIns/xtAj3bAcQXgRWbVExWIL8G v4gPxoV7fw== =8ZHA -----END PGP SIGNATURE----- --nzpfrxwi4i53nnqx-- --===============1557353379821013956== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy --===============1557353379821013956==--