Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp613963rwb; Tue, 4 Oct 2022 08:20:35 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6BEaK0/BYxX34cT9bppZrfcF0DaFkZF+bCEyZcZwYFZmbQ9rGHyYbL3f/syM0KxffF7uDA X-Received: by 2002:a17:906:d54d:b0:786:6f5:e0c1 with SMTP id cr13-20020a170906d54d00b0078606f5e0c1mr19430886ejc.293.1664896834902; Tue, 04 Oct 2022 08:20:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664896834; cv=none; d=google.com; s=arc-20160816; b=iDBhkC4IywoNDSrgt82nPqcHq+jLi7yIyVFCP3U3EkrWptAhTZc2okaPgje55St1dF BdR1bcl1cBJ+Y/egxMfNRmRX5PoAMaYc1Z0RlY7VeQP68Ly7TbukDBl0fb0POTJVgqz7 SBbnpF/UJyzmHkH+C11AQ8wrOaHm0bkYJbGUtsd231xp00ynaDHeQnRK3h1U/Wsh6p9O uwtO/nSyrSm/i4K8fxUxltws4EtC/3LP0O/WAo6+yckG/vIM1y/O+nwhDaJ1+Ib6jMaA 9+tJJ5Wyy8JP6q6y4UU4yHB0tLQybSvxxd56KwxgNO0lwwm4kRGPf91CcfG2XTOBwtnB w2nw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=CWdX4tvEDe9KXAQIvWXUpR26N6THyFmklq+pYn7/wck=; b=RlkNCwPahd0bqGGHIyRNGwY2Bk/Omz5S2ZPkY9/pGOHcV6y3Lk49306/HF3xsfCgpR VIOn/jx9uLWV3RAP87LsGLazUfsqbeTtXL710ZQUnS3VyOn+vM25UnJ1JI2Dw205VMQS 5hM9WoHkglJmvQ23yQEnAE/897N717Cp5W7ooCTCvzOk8dYlF/QIeoKkxKKXI4toiH9D XT+jUYkdZYtu3NWDiZ0f2Aq4adI3Iv2MeWSY5Jz+KdTZmMeMCg55l6Eqi6hNbI6o/x7V 2ZlqyVsIfVJ0/yPvr7giiopOERJ5pkKtC7hg9dnLsMfgjdia0MUVIDLOTjP29k6L7K0k 0kOw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="v9qAcpY/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id he8-20020a1709073d8800b0078307781936si12533001ejc.359.2022.10.04.08.20.09; Tue, 04 Oct 2022 08:20:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="v9qAcpY/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229550AbiJDPFT (ORCPT + 99 others); Tue, 4 Oct 2022 11:05:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54056 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229532AbiJDPFQ (ORCPT ); Tue, 4 Oct 2022 11:05:16 -0400 Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9E72D51416 for ; Tue, 4 Oct 2022 08:05:14 -0700 (PDT) Received: by mail-lf1-x130.google.com with SMTP id o7so14282817lfk.7 for ; Tue, 04 Oct 2022 08:05:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date; bh=CWdX4tvEDe9KXAQIvWXUpR26N6THyFmklq+pYn7/wck=; b=v9qAcpY/EulrMR7IHMzcNeWHI6LbF7pg8NXAg+ErSDmILTlVv9VuATHeiDFUuS0GDk fMPUpg+ZIm2fvpOjwhU0jNrO51zTdX5Wo89TE4EpRBM2U6EglD08H2D49MIHAr+WLhko QutFGm6gKSaXJOgqQqp0VLMjpvhTVkSYKRXOY7lsbEpK7hpvEMVYv/IOjeuYVy2lpDuy RIbwA4QZi5UsdDLDWczQYuAqCNJVPlYdCGswtZoaf03Nol5+mrQy953CxoP1IFoIOrTU nFaOMmcYVh/vGEvNaZPxeKoSDLmFz2Hx+xOXxbVYjjLs1Y6XZTdt5PUigU9+DBfhOe6G ScPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date; bh=CWdX4tvEDe9KXAQIvWXUpR26N6THyFmklq+pYn7/wck=; b=CE074thcClqgZWj640B5vyg9km7IzPVsGF2DfpVGIOQU1sdpiyCAsYWTiNG87zCmNJ Zmb3EmqfE9nroU5LRc+bJnyQdqFdLQLKXSaGTj8fjHg2u0lDw3FHt1EmnnpwVKZtuEls sF8CazpXHBazTTR8ZtFzh4zzsgPxR8qigXYIL1FesstlOm+HbDTGnotAGZdUXW7MsPQ1 2+IfzH42pflWpSuFmm3ixiEoHOYQ6wSoq3h/uKV5AD0sJKedBWcbukCKBqQ4OJC1pSSL sPER26MzfpRiNAjuumFW/myEnusBcIbXBcReKHI55aIi5/5wpuvr+KHVFPysfwFyGXg8 d2nw== X-Gm-Message-State: ACrzQf0zdFujYNI13a7xfCKzWKB1g9Vf7dGnRfV74CKxAJoWpy4Oi14Q jzFoVsFNMsVzDMP8KvkzvOU5RQ== X-Received: by 2002:a19:6909:0:b0:4a2:5d5a:2f49 with SMTP id e9-20020a196909000000b004a25d5a2f49mr430421lfc.66.1664895912921; Tue, 04 Oct 2022 08:05:12 -0700 (PDT) Received: from [192.168.0.21] (78-11-189-27.static.ip.netia.com.pl. [78.11.189.27]) by smtp.gmail.com with ESMTPSA id a16-20020a19f810000000b00494643db68fsm1952030lff.81.2022.10.04.08.05.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Oct 2022 08:05:12 -0700 (PDT) Message-ID: <49daae86-e922-9a17-ebed-2a33a5eeb18e@linaro.org> Date: Tue, 4 Oct 2022 17:05:11 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.0 Subject: Re: [PATCH v1 17/17] drm/mediatek: Add mt8195-dpi support to drm_drv Content-Language: en-US To: Guillaume Ranquet , Michael Turquette , Kishon Vijay Abraham I , Matthias Brugger , Vinod Koul , Stephen Boyd , David Airlie , Rob Herring , Philipp Zabel , Krzysztof Kozlowski , Daniel Vetter , Chunfeng Yun , CK Hu , Jitao shi , Chun-Kuang Hu Cc: linux-mediatek@lists.infradead.org, dri-devel@lists.freedesktop.org, Pablo Sun , linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, Mattijs Korpershoek , linux-arm-kernel@lists.infradead.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org References: <20220919-v1-0-4844816c9808@baylibre.com> <20220919-v1-17-4844816c9808@baylibre.com> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/10/2022 13:55, Guillaume Ranquet wrote: >> No. You said what the code is doing. I think I understand this. You >> still do not need more compatibles. Your sentence did not clarify it >> because it did not answer at all to question "why". Why do you need it? >> >> Sorry, the change looks not correct. >> >> Best regards, >> Krzysztof >> > > I need a new compatible to adress the specifics of mt8195 in the mtk_dpi driver, > the change is in this series with: > [PATCH v1 16/17] drm/mediatek: dpi: Add mt8195 hdmi to DPI driver [1] But you do not have specifics of mt8195. I wrote it in the beginning. > > I then need to add that compatible to the "list" here in mtk_drm_drv. No, you do not... I checked the driver and there is no single need... or convince me you need. > I don't see a way around this unless I rewrite the way mtk_drm_drv works? Why rewrite? You have all compatibles in place. > > Maybe if I declare a new compatible that is generic to all mediatek > dpi variants? You were asked to use fallback. Don't create some fake fallbacks. Use existing ones. > and have all the dts specify the node with both the generic dpi and > the specific compatible? > > dpi@xxx { > compatible = "mediatek,dpi", "mediatek,mt8195-dpi"; I don't know what's this but certainly looks odd. Some wild-card compatible in front (not fallback) and none are documented. > ... > } > > Then I can "collapse" all the dpi related nodes in mtk_drm_drv under > "mediatek,dpi" ? > > I guess would have to do the change for all other components that are needed in > mtk_drm_drv (mmsys, aal, ccor, color, dither, dsc, gamma, mutex...). > > That's the only trivial way I can think of implementing this with the > current status > of the mtk_drm stack. > > Do you have any other ideas in mind? Use fallback of compatible device. That's the common pattern. Everywhere, Mediatek as well. Best regards, Krzysztof