Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp10618650rwl; Mon, 2 Jan 2023 05:41:49 -0800 (PST) X-Google-Smtp-Source: AMrXdXsTrz+hTRAJYn+BS27ECUd52g7Vv3a4VgpXno2OKo8oHAQff0Xu00VdEWHD87PsQGYno0TL X-Received: by 2002:a17:903:1092:b0:189:d8fb:152c with SMTP id u18-20020a170903109200b00189d8fb152cmr38382263pld.30.1672666909167; Mon, 02 Jan 2023 05:41:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672666909; cv=none; d=google.com; s=arc-20160816; b=J6oPteUlpsS1Grm19Hc2KPES7ISs52bDRIaAB1EAN3STSrerIk2/Jw6ODkIazY+hOj Tjdq+Oesggp5Bk0eIL8wUfaOK3dC860mr8n/qhJnFfN6b924lQtoEkFIxgLtczkY9qnE 1krAjd3j+C/zl1OyhHNJ/4z21xlBVBUm1qNKBVCCrCWaz9Vq70wL2aAVAzmlT/LpGUSA iHrZUcLYddfsvzgMh/m9U3fF8VqmnhhPqFXQPIPcLuRynBeLZLsboQM8OH5Qy3Yy7uYF dVXafG1VNf5Q0ZQxatGD9MxOqb+37njPJQ8BCg5VuBei2t4Y3nLz0AiZcr6gNc4cjZ1b rFXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:mime-version:in-reply-to:references:user-agent:from :dkim-signature; bh=yUeJe0drBbTMgiYkIr+hpKI3FSwnBgCuZWCVk8bkpiQ=; b=eU3aLySzOOyokBzlMsHOQL0eXmDG1HMoIToag3Eo0PJI40yrcwxzG+nuH8fxbZuOIg EnRqIbnY91XycjL3f6T/hCKSqmGQyv6QGxxy7x/ptTQ7g6DrUjXdDu8Pn8S7FmroNRvM RVsfj6+OgsdplrCNwOtT48OXFAXghAqNnoQzha9+G7pGDnvcDJdqOK8aD5kh9j/owMD7 8i/tGgAGm3L3S3Q/Q6Eea5N+0UXPcmCiDLF3WY/bh49jj0OkcPYm54AOUKTfcqEXGRc2 mkAmlIowOpy1yeZiCXaHiCvcJ2Gazj0dMtwyATpkhBjT+fDJjysUWBLfy0zh5acLDqEE bHyA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=sJKeU3WC; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 21-20020a170902c11500b0016be68156aesi29191855pli.173.2023.01.02.05.41.41; Mon, 02 Jan 2023 05:41:49 -0800 (PST) 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=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=sJKeU3WC; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232691AbjABNij (ORCPT + 61 others); Mon, 2 Jan 2023 08:38:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39288 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232579AbjABNig (ORCPT ); Mon, 2 Jan 2023 08:38:36 -0500 Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 62149CCC for ; Mon, 2 Jan 2023 05:38:35 -0800 (PST) Received: by mail-qt1-x82c.google.com with SMTP id bp44so19825082qtb.0 for ; Mon, 02 Jan 2023 05:38:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:in-reply-to:references:user-agent:from:from:to:cc :subject:date:message-id:reply-to; bh=yUeJe0drBbTMgiYkIr+hpKI3FSwnBgCuZWCVk8bkpiQ=; b=sJKeU3WCdOQHKogctAuHoH1Lb5awwjpVpHefGzuQH49JgYhK41rW3ae5mHbdmBGjsY UnNOamQKAW85+d3DJvYxWEY0sQwr8sxKKtQaJB5/ZBhMt7NlGdpExaGUTvd1Ym8DFBJN z/E2hVpZRbW12fzg0X2Kj7ZDsGIcLif6Q2AhzKLokR+qFZiuaAbfbrrFr+unYfzjUdTo IBWE8DrMPJ7CwXxGloffvAvF0SeiBqq0lV8Vq6+n+EzQHdffJcGYNIxvZMkpsWb/VBo6 wuXMNTIGHn3SZ4HlhcRTVEyDdo/VUZ2atZFin0VDm7biJW7nnru9XUW+S1aJ2RCzJq8Z kYbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:in-reply-to:references:user-agent:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=yUeJe0drBbTMgiYkIr+hpKI3FSwnBgCuZWCVk8bkpiQ=; b=RsEwflfRuEjZPP/UNM/5ULf0aD8WaTCUw7Du6OPHW2tqsSkZ2UaB1Ga5gvclSNoW58 ubM8hy9V5zJ1QGWl/XVDSZ+wVpFQr21tmGdIhVBWp5//7hqPL645TmA5lB2TvhnKs0Lr 6opmWcy/Td6qrvxMtmbHL0y5VC45x9AqnsUG7QPZQyElCnudwqbS3rS+Jragllgh3+ld ZXDcrArpMfh+TH1D3IPMTreZUshiN4eqY7Gu2ZYQOHk4PceL/WtVH8D1tDUGKrzWDYvz aOcjkA1PtXSpK9jLXtztc79Peqbam/4WZyxBbxiJsZIq+18KBvHkjz6XaZeZb/VjnjpZ x+Mg== X-Gm-Message-State: AFqh2kp7mWjUi4iDx5uxCyRrJpgAxdlUwTpuc9z9WNBXGlaQu6i4xHNT OoKw1ALkrDCV/VMuriHzj0BpwhyD5pZ3qw5OWjRpww== X-Received: by 2002:ac8:4d50:0:b0:3a8:a6e:1b4 with SMTP id x16-20020ac84d50000000b003a80a6e01b4mr1646554qtv.313.1672666714390; Mon, 02 Jan 2023 05:38:34 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Mon, 2 Jan 2023 13:38:33 +0000 From: Guillaume Ranquet User-Agent: meli 0.7.2 References: <20220919-v3-0-a803f2660127@baylibre.com> <20220919-v3-2-a803f2660127@baylibre.com> <7da1e73a0cca6867a060d5b69d45e8d4dfc89748.camel@mediatek.com> In-Reply-To: <7da1e73a0cca6867a060d5b69d45e8d4dfc89748.camel@mediatek.com> MIME-Version: 1.0 Date: Mon, 2 Jan 2023 13:38:33 +0000 Message-ID: Subject: Re: [PATCH v3 02/12] dt-bindings: display: mediatek: add MT8195 hdmi bindings To: CK Hu , "robh+dt@kernel.org" , "kishon@ti.com" , Chunfeng Yun , "chunkuang.hu@kernel.org" , Jitao Shi , "daniel@ffwll.ch" , "matthias.bgg@gmail.com" , "p.zabel@pengutronix.de" , "airlied@gmail.com" , "rzysztof.kozlowski+dt@linaro.org" , "koul@kernel.org" Cc: "linux-kernel@vger.kernel.org" , "inux-mediatek@lists.infradead.org" , Mac Shen , "evicetree@vger.kernel.org" , "rzysztof.kozlowski@linaro.org" , Stuart Lee , "ri-devel@lists.freedesktop.org" , "inux-arm-kernel@lists.infradead.org" , "linux-phy@lists.infradead.org" , "angelogioacchino.delregno@collabora.com" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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 Mon, 26 Dec 2022 06:18, CK Hu (=E8=83=A1=E4=BF=8A=E5=85=89) wrote: >Hi, Guillaume: > >On Fri, 2022-11-04 at 15:09 +0100, Guillaume Ranquet wrote: >> Add mt8195 SoC bindings for hdmi and hdmi-ddc >> >> On mt8195 the ddc i2c controller is part of the hdmi IP block and >> thus has no >> specific register range, power domain or interrupt, making it simpler >> than its the legacy "mediatek,hdmi-ddc" binding. >> >> Signed-off-by: Guillaume Ranquet >> --- >> > >[snip] > >> a/Documentation/devicetree/bindings/display/mediatek/mediatek,mt8195- >> hdmi-ddc.yaml >> b/Documentation/devicetree/bindings/display/mediatek/mediatek,mt8195- >> hdmi-ddc.yaml >> new file mode 100644 >> index 000000000000..2dc273689584 >> --- /dev/null >> +++ >> b/Documentation/devicetree/bindings/display/mediatek/mediatek,mt8195- >> hdmi-ddc.yaml >> @@ -0,0 +1,51 @@ >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >> +%YAML 1.2 >> +--- >> +$id: >> https://urldefense.com/v3/__http://devicetree.org/schemas/display/mediat= ek/mediatek,mt8195-hdmi-ddc.yaml*__;Iw!!CTRNKA9wMg0ARbw!wwVQuq5lzW0lvUFUkVX= PWT8cIu96xdkn4tMams1E55qyxEZmgV1i0WfpOlq57w$ >> >> +$schema: >> https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml= *__;Iw!!CTRNKA9wMg0ARbw!wwVQuq5lzW0lvUFUkVXPWT8cIu96xdkn4tMams1E55qyxEZmgV1= i0WdSGOSxzw$ >> >> + >> +title: Mediatek HDMI DDC for mt8195 >> + >> +maintainers: >> + - CK Hu >> + - Jitao shi >> + >> +description: | >> + The HDMI DDC i2c controller is used to interface with the HDMI DDC >> pins. >> + >> +properties: >> + compatible: >> + enum: >> + - mediatek,mt8195-hdmi-ddc >> + >> + clocks: >> + maxItems: 1 >> + >> + clock-names: >> + items: >> + - const: ddc >> + >> + mediatek,hdmi: >> + $ref: /schemas/types.yaml#/definitions/phandle >> + description: >> + A phandle to the mt8195 hdmi controller >> + >> +required: >> + - compatible >> + - clocks >> + - clock-names >> + >> +additionalProperties: false >> + >> +examples: >> + - | >> + #include >> + #include >> + hdmiddc0: i2c { >> + compatible =3D "mediatek,mt8195-hdmi-ddc"; >> + mediatek,hdmi =3D <&hdmi0>; >> + clocks =3D <&clk26m>; >> + clock-names =3D "ddc"; >> + }; > >I think we should not have a virtual device. This ddc is part of >mt8195-hdmi device, so just keep mt8195-hdmi, and let mt8195-hdmi >driver to probe the sub driver of ddc driver. > >Regards, >CK Hi CK, Thx for your input. Though I would strongly prefer to keep the ddc as a separate "virtual devic= e". It aligns better with the goal of reusing as much code as possible from the HDMI V1 IP, which is something you have been advocating since V1 of this patch quite some time ago and has shaped this patch. To me we are in a state that is clean and avoids branching in the hdmi common code. Would you reconsider and allow the use of that virtual device? Thx, Guillaume. > >> + >> +... >>