Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1880792ybh; Fri, 17 Jul 2020 03:52:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJydBNgzi1IhKtl1tb+5TVXu1yKb6D8LUjHtTfaOrxUp/wt59QMaxXtVhOQdUHrpKaDB9TXU X-Received: by 2002:a17:906:6442:: with SMTP id l2mr7758150ejn.383.1594983139462; Fri, 17 Jul 2020 03:52:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594983139; cv=none; d=google.com; s=arc-20160816; b=UdgsdOdilE/fGJ+9U3AOFvSLE0h8TAooWrm/lW/DfqmURlqxp5G0Qy0zrGSjp5fXOr S05kST4zUYa188RKgGqP2PoekrAUgrEtgcJ+cykJ3XdxVgofd2NdJfIfD95dLDan1BEK bE20zI5wmx8F3MTHSRKmU62fjmEND3A/oLLeeXmWccSuJnBjVSfLyzqBEtPYD7iK+k0d tbdvolaYobgwbDdbzlk3tjF0ZZvelsAQTlPhxO27CqjIYh7ub8DGRpWdchCG+xPAmZIn SsHt5It8uTz1lymYkpaIDHdK30quGXbQeKcXBGCfZAp2tRrtS4cc/NL8rGUtv1/8NeVr UK7Q== 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 :user-agent:references:in-reply-to:date:to:from:subject:message-id; bh=VIwtmOJPWFmCuoxAQ2sl9rDenqmbW7WhHns4rjnbgwc=; b=YkIQuC4AF000rpMKMR4EGiWepwch8S47PR2ct3Io1+eKkGQdp02aaMbegVxo7ZxEw8 orUolHL9R64JuuU5AbouIVcsSGKf10lfKDVn6fuliDYUNDsA4yyVJA12zLXJCkoB7x/l dJUrQKJeWa/xBP9e0Q3BpEbY1s6ucm2+fKCzrMLCKDfI7NkmhRI5qHtqV3qoqpQKHFOi +P5QjOzS1DiQDtx7mWChbNr7InHQrKjzWwD5NJ0TBpGYjpUvtCTvPnDOYzaFGK7X7kG4 PBSPIITTL62tieXaaMJFBU4fBtoDWhYdBjknO5f7Nv7PJqwryIhvxy/I9zQCuivvCMGa ekdA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j23si4981821edy.251.2020.07.17.03.51.43; Fri, 17 Jul 2020 03:52:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726070AbgGQKvH (ORCPT + 99 others); Fri, 17 Jul 2020 06:51:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38560 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725912AbgGQKvH (ORCPT ); Fri, 17 Jul 2020 06:51:07 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4BE22C061755 for ; Fri, 17 Jul 2020 03:51:07 -0700 (PDT) Received: from gallifrey.ext.pengutronix.de ([2001:67c:670:201:5054:ff:fe8d:eefb] helo=localhost) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jwNxE-0003u7-5w; Fri, 17 Jul 2020 12:51:00 +0200 Message-ID: Subject: Re: [PATCH v5 0/4] Add support for iMX8MQ Display Controller Subsystem From: Lucas Stach To: Laurentiu Palcu , Philipp Zabel , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Laurentiu Palcu , dri-devel , Linux ARM , devicetree , Guido =?ISO-8859-1?Q?G=FCnther?= , lukas@mntmn.com, Linux Kernel Mailing List Date: Fri, 17 Jul 2020 12:50:56 +0200 In-Reply-To: <20200717094517.layssf75bxe3ijs4@fsr-ub1864-141> References: <20200709164736.18291-1-laurentiu.palcu@oss.nxp.com> <3c03afff3256ec36e12b9d9408830fbb4853f982.camel@pengutronix.de> <20200717092758.GR3278063@phenom.ffwll.local> <20200717094517.layssf75bxe3ijs4@fsr-ub1864-141> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.3 (3.36.3-1.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:201:5054:ff:fe8d:eefb X-SA-Exim-Mail-From: l.stach@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 Am Freitag, den 17.07.2020, 12:45 +0300 schrieb Laurentiu Palcu: > Hi Lukas and Daniel, > > On Fri, Jul 17, 2020 at 11:27:58AM +0200, Daniel Vetter wrote: > > On Fri, Jul 17, 2020 at 11:12:39AM +0200, Lucas Stach wrote: > > > Am Freitag, den 17.07.2020, 10:59 +0200 schrieb Daniel Vetter: > > > > On Fri, Jul 17, 2020 at 10:18 AM Lucas Stach wrote: > > > > > Hi Laurentiu, > > > > > > > > > > Am Donnerstag, den 09.07.2020, 19:47 +0300 schrieb Laurentiu Palcu: > > > > > > From: Laurentiu Palcu > > > > > > > > > > > > Hi, > > > > > > > > > > > > This patchset adds initial DCSS support for iMX8MQ chip. Initial support > > > > > > includes only graphics plane support (no video planes), no HDR10 capabilities, > > > > > > no graphics decompression (only linear, tiled and super-tiled buffers allowed). > > > > > > > > > > > > Support for the rest of the features will be added incrementally, in subsequent > > > > > > patches. > > > > > > > > > > > > The patchset was tested with both HDP driver (in the downstream tree) and the upstream > > > > > > MIPI-DSI driver (with a couple of patches on top, to make it work correctly with DCSS). > > > > > > > > > > I think the series (minus 3/5 and minor correction to the DT binding) > > > > > is fine to go in now. So just some formal questions: are you going to > > > > > maintain this driver in upstream? If so we should add a MAINTAINERS > > > > > entry to that effect. I can offer to act as a reviewer in this case. > > I can maintain the DCSS driver, sure, and the more reviewers the better. > Thanks for helping out with this. Should I send a v6 then with a patch > for MAINTAINERS? > > > > > > How do you intend to merge this? IMO pushing this through drm-misc > > > > > seems like the right thing to do. If you agree I can help you get this > > > > > applied. If you are going to maintain the driver on your own, I think > > > > > you should then apply for commit rights to drm-misc. > > > > > > > > drm/imx isn't listed yet as under the drm-misc umbrella, maybe we > > > > should put the entire collective of imx drivers under drm-misc? Or > > > > maybe it's just an oversight that the git repo isn't specified in the > > > > MAINTAINERS entry. Also maybe we should add the pengutronix kernel > > > > team alias there too? > > > > > > drm/imx was exclusively the IPUv3 up until now, which is in fact > > > maintained outside of drm-misc in its own git tree. This has worked > > > quite well in the past so even though IPUv3 doesn't see a lot of churn > > > these days the motivation to change anything to this workflow is quite > > > low. And yes, the git tree is missing from the MAINTAINERS entry. > > > > > > For the DCSS driver, if it's going to be maintained by NXP, I figured > > > it might be easier for Laurentiu to push things into drm-misc than set > > > up a separate public git tree. But IMHO that's fully up to him to > > > decide. > > > > /me puts on maintainer hat > > > > Much prefer drm-misc over random people playing maintainer and fumbling > > it. I think the reasonable options are either in the current imx tree, or > > drm-misc. Standalone tree for these small drivers just doesn't make much > > sense. > > I don't have anything against either method, though I have to agree I > like things to be simple. Going through drm-misc sounds simple enough to me. :) > However, since there is going to be more activity in the DRM IMX area in > the future, reviving the drm/imx tree, and push all IMX related stuff > through drm/imx, could make sense as well. I think drm-misc is the right place then. Please send a v6 with the following changes: - drop the component framework patch - drop the i.MX8MQ DT patch, this should go through Shawn's imx tree after the driver and binding has landed in drm-misc - you can add my Reviewed-by to the whole series or I can add it when applying - add a MAINTAINERS entry, please add me as a reviewer if you don't mind I can push this initial series into drm-misc until you've got your own commit rights. Regards, Lucas