Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp46057pxb; Thu, 21 Jan 2021 00:30:05 -0800 (PST) X-Google-Smtp-Source: ABdhPJx9k21f7H5AvCRQP3yHDWevN4A9M34DET9ufdhl98kfnMj518FlhOSJ/bzDosyP7+aOMBFs X-Received: by 2002:aa7:d9c3:: with SMTP id v3mr9989215eds.133.1611217805324; Thu, 21 Jan 2021 00:30:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611217805; cv=none; d=google.com; s=arc-20160816; b=aGaJVUGCEx2UncPFAmqrKWYD5B7fY+XdqCUmUiHjasqUYPEmUPkb1d4kiP7saETv5m ftQtWS5wg6/ud10yTqIED2gCWoIFcKXPD/6qROkje2KAMm0tkrnFDdUqk/2c8XApmojL dagcI8rjDlSNvadzg3J6VwRT5Dn8ulF7s7UnuxIkRQDNEEiqld27mMLT2lS1d6PjEJQj w+19BjTZQKyVx7d3CypFWL3uCxzzJsTmbJTHzgenwF6dl6mt3we70GPx4uJTD54YnnOD MNddiBOd1uq1v59KbWL1OttPwmPaxI5GVtdX2RJr91mpQw5KgziPQSmN+k3tLqzf7qa+ NtGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=FTev7URHDSmEdaSPwGwV1PXV15mbTbLtaLRB5kzgKjs=; b=aTZg5jjtLe1blNYm30X+N0E2yPJGl0O9TR6f/yKzJWiOtg5GBWw8EY3Dqgi6hkEnYQ WViqbsoaRQxPOscaVJ8Tuq05B3pisABXNx4SZpXtUQzh63KGi4GhsJXH31ZkpEbOLlPW EO06uKpDiYMnCPiCI6NMeXcFmHcNb0Wo2ziDVoK6FslxxVRe5vaIu+E2b++8dxN0rw5q BWqgbyXlU2fJlvGQxM2Ffb8UVYrzQtGDPa+hSKr6WRG1zNgx9B9YpX11PzHYTK9i18/Q w3rjls5RyJaTRkz0VOEmlXwkF0I7kXW5yMX78XFHjAP619bfbd81G7yZfrL0RepRvYAr ERyg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=mOSdaqme; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e22si1874561edu.9.2021.01.21.00.29.42; Thu, 21 Jan 2021 00:30:05 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=mOSdaqme; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727945AbhAUI0B (ORCPT + 99 others); Thu, 21 Jan 2021 03:26:01 -0500 Received: from mail.kernel.org ([198.145.29.99]:52864 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727001AbhAUITz (ORCPT ); Thu, 21 Jan 2021 03:19:55 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 65E1723976; Thu, 21 Jan 2021 08:18:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1611217141; bh=hhhptWrujcElAbSl2ou/FOxBVarF2/4ZICpA78koQKY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mOSdaqmeY7neZr1NBdUhHGAUKUpB/zX8/VLMLHq0RUKZrQm5L/GslnlEd/F0MmgDs KmDJSbUyVPrRRYMjLpHTZFacGkiu2MzPBeB3+ZF/hGQ26lmZlKTazZ/o2LlxuL1E39 DA0psnM6msta+GWNePYVYBp/ct2i+jmVrMIK399eteygz67RoZmJC+y4azViV7HWQV vSzPpc1cJT/RDpgUL4SCbxvsQK27k3yNIIoadcN/3PCMYc1QBowK9ToZ3eru3tWvGG oOS/WNXftOI/g647lAalt85eSJoVi4EI92NujfyXHBgXEm3dIzVO55Mbw7q9I2+3rC gwZRcTkLQpEFA== Date: Thu, 21 Jan 2021 09:18:55 +0100 From: Matthias Brugger To: Chun-Kuang Hu Cc: Philipp Zabel , David Airlie , linux-kernel , DRI Development , CK Hu , "moderated list:ARM/Mediatek SoC support" , Daniel Vetter , Matthias Brugger , Linux ARM Subject: Re: [PATCH v2 3/5] drm/mediatek: Change disp/ddp term to mutex in mtk mutex driver Message-ID: References: <20210106231729.17173-1-chunkuang.hu@kernel.org> <20210106231729.17173-4-chunkuang.hu@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 21, 2021 at 07:46:44AM +0800, Chun-Kuang Hu wrote: > Hi, Matthias: > > Matthias Brugger 於 2021年1月21日 週四 上午2:27寫道: > > > > On Thu, Jan 07, 2021 at 07:17:27AM +0800, Chun-Kuang Hu wrote: > > > From: CK Hu > > > > > > mtk mutex is used by both drm and mdp driver, so change disp/ddp term to > > > mutex to show that it's a common driver for drm and mdp. > > > > > > Signed-off-by: CK Hu > > > Signed-off-by: Chun-Kuang Hu > > > --- > > > drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 30 +-- > > > drivers/gpu/drm/mediatek/mtk_drm_drv.c | 2 +- > > > drivers/gpu/drm/mediatek/mtk_drm_drv.h | 2 +- > > > drivers/gpu/drm/mediatek/mtk_mutex.c | 305 ++++++++++++------------ > > > drivers/gpu/drm/mediatek/mtk_mutex.h | 26 +- > > > 5 files changed, 182 insertions(+), 183 deletions(-) > > > > > [...] > > > diff --git a/drivers/gpu/drm/mediatek/mtk_mutex.c b/drivers/gpu/drm/mediatek/mtk_mutex.c > > > index 1c8a253f4788..98a060bf225d 100644 > > > --- a/drivers/gpu/drm/mediatek/mtk_mutex.c > > > +++ b/drivers/gpu/drm/mediatek/mtk_mutex.c > > [...] > > > > > > -static const struct of_device_id ddp_driver_dt_match[] = { > > > +static const struct of_device_id mutex_driver_dt_match[] = { > > > { .compatible = "mediatek,mt2701-disp-mutex", > > > - .data = &mt2701_ddp_driver_data}, > > > + .data = &mt2701_mutex_driver_data}, > > > { .compatible = "mediatek,mt2712-disp-mutex", > > > - .data = &mt2712_ddp_driver_data}, > > > + .data = &mt2712_mutex_driver_data}, > > > { .compatible = "mediatek,mt8167-disp-mutex", > > > - .data = &mt8167_ddp_driver_data}, > > > + .data = &mt8167_mutex_driver_data}, > > > { .compatible = "mediatek,mt8173-disp-mutex", > > > - .data = &mt8173_ddp_driver_data}, > > > + .data = &mt8173_mutex_driver_data}, > > > {}, > > > }; > > > -MODULE_DEVICE_TABLE(of, ddp_driver_dt_match); > > > +MODULE_DEVICE_TABLE(of, mutex_driver_dt_match); > > > > I think it would make sense in a follow-up patch to update the binding > > to use "mediatek,mt2701-mutex" to reflect that mutex is used for drm and > > mdp driver. Make sense? > > Yes, it make sense. I would try to update the binding, but I wonder > device tree should be backward compatible? Let's discuss in that > follow-up patches. > From my understanding, we will need to keep the of_device_id entries for the old binding in the driver (so that old DTs still work) while we should enforce the new binding. I'm not sure if the yaml has a option for out-of-date compatibles. Regards, Matthias