Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1987413rwb; Mon, 7 Nov 2022 07:58:03 -0800 (PST) X-Google-Smtp-Source: AMsMyM6eNJHy2wkZlvUUO7ProznGWojHorirABUm1c5T1hbyQMBic3Is00csJHxf4wJu1S/SWLlT X-Received: by 2002:a17:907:1ca2:b0:7ad:e51b:3c7a with SMTP id nb34-20020a1709071ca200b007ade51b3c7amr37334183ejc.665.1667836682918; Mon, 07 Nov 2022 07:58:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1667836682; cv=none; d=google.com; s=arc-20160816; b=b+JWies/+F5zmO/GwEO4eQqkKGByh2PHsM/wUZ5coyRDIttWzFQ+uVieYvwwqeHFZj 0j8f4Rnovq/qvUXMNHU7OkcLGlXNrobcV/1VihXsCsBfNHHSnSXiHqbkQKMk7khMnREz 2D3O0lUyVRRIp9QCuqonswVPXvhYWFRvGe+arx3gOnHTDVhe2uMUZCfqHJTdxYGjGyTH MCvuyGprOm/tbRTFzD7l9NqKb63qbgEz1oHCcjd/Hkae9WEo6/iKb202Oko2DTwqWYEC k5E58/poxJVEINaiB1ALrIlo2RYaLxWp2LBSD/Jcybpit2h2zdIJOlNnKLizxw8oV5xT vA5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:mime-version :in-reply-to:references:user-agent:from:dkim-signature; bh=ZfXdjQhTZQkr1X94ZZoUwqUu1jkMou77X3rg8dG96a8=; b=cqivvbWaKQt2Nb1MwjRkKazt0py981ZZ9TYqtKuzoMH+x6F+zL5O5f2LXF88SxN4Yr K3EPROsA7mqBdUpChNVow/LoXJQsV2mTiF7vUG2hOOt+AT2wIb5gNlTM3gHdYZSenc1N 9QbDk3S6ziebkUmy07VyV/fSpaoSbC864cPnA+ut7vZWo/Rdg1sSU3F2Dj6zvQIisjBF DyQR+f1CfNLxgG0EytNKMmm/U4wF/GqrKm22HZSlHIEhvb6AmmA+KyXwZCvOFekLm3SW /VmlbsBMpjRK/x9AdR3Gxm8nm0fr98mND/2mFGRupUiEq+pbRqNwchPoj5GE3URMdsn6 7BPA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b="YY/rIl08"; 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 p17-20020a056402045100b004617c3c9297si8882975edw.252.2022.11.07.07.57.39; Mon, 07 Nov 2022 07:58:02 -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="YY/rIl08"; 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 S231519AbiKGOmb (ORCPT + 93 others); Mon, 7 Nov 2022 09:42:31 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56010 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231440AbiKGOm3 (ORCPT ); Mon, 7 Nov 2022 09:42:29 -0500 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 AB7671A04F for ; Mon, 7 Nov 2022 06:42:27 -0800 (PST) Received: by mail-lf1-x130.google.com with SMTP id g7so17059195lfv.5 for ; Mon, 07 Nov 2022 06:42:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=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=ZfXdjQhTZQkr1X94ZZoUwqUu1jkMou77X3rg8dG96a8=; b=YY/rIl083jijvHJKrVqGCLgKhx1v5KpSxBKiU1+0a9eewETgjWVakNpnGhGMKPrXgU cO1XJQO7ms2EabCorEz5LwdJjlGCPz21MpkLr+SLY5nglIWcT4dTmCAt7R2Wcv76yuWt p0Cgd/gsGoHIDF5So+E1NrRbe8cHiv3++mag11g+FaFv1hRcS8klQrwysIw0VTmqGBR6 9HdC0oO1CFvTxOOtKywSXSkN7S5iDbHc2GMV/2PX7V2ItPNgLhh04mFuO6sjt605vxAd yM8BKtaJs2AvTjF3tQC58gaQ2CzGVEVzIZBoIhmPeANGprFmO3fgZwoQKGDEXFdPdXyb Yhqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=ZfXdjQhTZQkr1X94ZZoUwqUu1jkMou77X3rg8dG96a8=; b=T3xXO/2EKuMALLTA9IG631ISb7R56qNr69bVWDJk2GUT19v9CWV4T4g6VSSm+WuUD8 fObsUEh65jwt3m9uAbdCvni4RI2RF/WvwZniIr3lVy9zXM2HHBUXi1s4uFNdsXPFawnk Q2rPMJZ8KlbmBZVrhClDCU1EqYA+nkVCMuTW/0uv69Zl/Kg4lvuID8nFBvrC7B41ZgUi z7qvNMHSSEqhB0/6aXVw+oXitPo32/qZVDFtS4d6S9pwmGRVkxAzZ0hlo9XVvkazqnEp zAu73n2FS8yJh/2fR+L6AOiMDshx3rG7oHyzt4UtQn8TjF/zXg0l7vLe2DaXJ4FAhiUX r6fg== X-Gm-Message-State: ACrzQf2K2JUvV4J8rW5uGO2h4ka2yafL2MrFDn/aFXzwliRhWr9h67io 3PtH9U2xFJyRgd/lIlhVvpmH+AEMJncdaFWK4HUBQQ== X-Received: by 2002:a19:8c57:0:b0:4ae:2436:818c with SMTP id i23-20020a198c57000000b004ae2436818cmr368888lfj.346.1667832145955; Mon, 07 Nov 2022 06:42:25 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Mon, 7 Nov 2022 14:42:25 +0000 From: Guillaume Ranquet User-Agent: meli 0.7.2 References: <20220919-v3-0-a803f2660127@baylibre.com> <20220919-v3-2-a803f2660127@baylibre.com> In-Reply-To: MIME-Version: 1.0 Date: Mon, 7 Nov 2022 14:42:25 +0000 Message-ID: Subject: Re: [PATCH v3 02/12] dt-bindings: display: mediatek: add MT8195 hdmi bindings To: Krzysztof Kozlowski , Kishon Vijay Abraham I , Rob Herring , Chun-Kuang Hu , Chunfeng Yun , Jitao shi , Matthias Brugger , Vinod Koul , CK Hu , Daniel Vetter , David Airlie , Krzysztof Kozlowski , Philipp Zabel Cc: linux-arm-kernel@lists.infradead.org, stuart.lee@mediatek.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, AngeloGioacchino Del Regno , linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, mac.shen@mediatek.com, linux-phy@lists.infradead.org Content-Type: text/plain; charset="UTF-8" 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=ham 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, 07 Nov 2022 11:02, Krzysztof Kozlowski wrote: >On 04/11/2022 15:09, 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 >> --- >> .../bindings/display/mediatek/mediatek,hdmi.yaml | 61 ++++++++++++++++++---- >> .../display/mediatek/mediatek,mt8195-hdmi-ddc.yaml | 51 ++++++++++++++++++ >> 2 files changed, 101 insertions(+), 11 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi.yaml >> index bdaf0b51e68c..9710b7b6e9bf 100644 >> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi.yaml >> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi.yaml >> @@ -21,6 +21,7 @@ properties: >> - mediatek,mt7623-hdmi >> - mediatek,mt8167-hdmi >> - mediatek,mt8173-hdmi >> + - mediatek,mt8195-hdmi >> >> reg: >> maxItems: 1 >> @@ -29,18 +30,12 @@ properties: >> maxItems: 1 >> >> clocks: >> - items: >> - - description: Pixel Clock >> - - description: HDMI PLL >> - - description: Bit Clock >> - - description: S/PDIF Clock >> + minItems: 4 > >Drop minItems, it's not needed when equal to maxItems. > >> + maxItems: 4 >> >> clock-names: >> - items: >> - - const: pixel >> - - const: pll >> - - const: bclk >> - - const: spdif >> + minItems: 4 > >Drop minItems, it's not needed when equal to maxItems. > > >> + maxItems: 4 >> >> phys: >> maxItems: 1 >> @@ -58,6 +53,9 @@ properties: >> description: | >> phandle link and register offset to the system configuration registers. >> >> + power-domains: >> + maxItems: 1 >> + >> ports: >> $ref: /schemas/graph.yaml#/properties/ports >> >> @@ -86,9 +84,50 @@ required: >> - clock-names >> - phys >> - phy-names >> - - mediatek,syscon-hdmi >> - ports >> >> +allOf: >> + - if: >> + properties: >> + compatible: >> + contains: >> + const: mediatek,mt8195-hdmi >> + then: >> + properties: >> + clocks: >> + items: >> + - description: APB >> + - description: HDCP >> + - description: HDCP 24M >> + - description: Split HDMI >> + clock-names: >> + items: >> + - const: hdmi_apb_sel >> + - const: hdcp_sel >> + - const: hdcp24_sel >> + - const: split_hdmi >> + >> + required: >> + - power-domains >> + else: >> + properties: >> + clocks: >> + items: >> + - description: Pixel Clock >> + - description: HDMI PLL >> + - description: Bit Clock >> + - description: S/PDIF Clock >> + >> + clock-names: >> + items: >> + - const: pixel >> + - const: pll >> + - const: bclk >> + - const: spdif >> + >> + required: >> + - mediatek,syscon-hdmi >> + >> additionalProperties: false >> >> examples: >> diff --git 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: http://devicetree.org/schemas/display/mediatek/mediatek,mt8195-hdmi-ddc.yaml# >> +$schema: http://devicetree.org/meta-schemas/core.yaml# >> + >> +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 > >Unless you expect it to grow, I propose to drop clock-names. It's not >useful when the name is the same as name of hardware. > >Best regards, >Krzysztof > Thx for your suggestions, I'll apply them in v4. Thx, Guillaume.