Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp1217507rwd; Thu, 8 Jun 2023 14:14:36 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5KvIlGggp9NoWI6NO6ur6H69RgLwQj2AVXmjdyE+QUuB8yFD+bPZxa1oNAuo8b//p5F0YO X-Received: by 2002:a05:6358:baa2:b0:129:ca25:6486 with SMTP id dg34-20020a056358baa200b00129ca256486mr4476999rwb.29.1686258875992; Thu, 08 Jun 2023 14:14:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686258875; cv=none; d=google.com; s=arc-20160816; b=Krdzg5Y5s9oZcNftdUS2hA0pEEQh1zto7J2oDQ1RusLwJNc6LRwu+/ocFy6JEEiN8C tXJ/I1m4o+9fSY3FPpzopiYrAVjDASQQmQDwtsR6atjm638XI9wyAYQSszLJxpLWmg0S pb4o9tZSv9RlbNYfhaCI/u7jx1kzVCAymgDF8qUKgahRQ4X1FcLH0Ouw2epjpJL+4wRa LLIxA7f372KnZkdqfJCGrJr8muStA+QgKnxLv5fUVm7rogRwu8oqBftUtlLggw9SOCJO H/aD84iNa53niHhJ1uIlnxg5nv86iZ9r0tVrFmXdCVHkt8h8DY2y15sWYWF6Y1mGT0Or tspw== 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-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=659QQ5o0RJcYetO+FfSdtr0AtP1kq3MC1W2qbtyWfug=; b=PHgFwRREcYNqwPEZ6CEQTTVcgvsB128U+gHQDyMZ0ISibB5CcWd9byjQMF8dpzirsR IXZnomp004dTgwmVfGVqXVrPKAixrFEFV8gQYE9t9se7idQy/2w+BgV6SnCQVsI3VPbn Jwu9G5Jyta8ZhI60bMEsyMd4EPobY6P6HZB2171vRC/4uEVDy/XpC++joxDCdhzQxMIM AYBa0joyBfo7QyIQ4C2wTWoitfNxKPriJ6nNxXDhrwa95DtDgBSsB/AxdLkLaFEI93VW rxRUcyaTzfNLmM9mtH/3pdk5nBwIt7QZoEMSXotZVj2RJB9POI8M+H+uD85P5E9GYTmz dK5Q== ARC-Authentication-Results: i=1; mx.google.com; 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=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k13-20020a636f0d000000b00542aa78ebdasi1424284pgc.838.2023.06.08.14.14.22; Thu, 08 Jun 2023 14:14:35 -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; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235802AbjFHVFX (ORCPT + 99 others); Thu, 8 Jun 2023 17:05:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56070 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236912AbjFHVFT (ORCPT ); Thu, 8 Jun 2023 17:05:19 -0400 Received: from mail-io1-f51.google.com (mail-io1-f51.google.com [209.85.166.51]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9686830D4; Thu, 8 Jun 2023 14:05:08 -0700 (PDT) Received: by mail-io1-f51.google.com with SMTP id ca18e2360f4ac-777b4560ae8so50365639f.2; Thu, 08 Jun 2023 14:05:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686258308; x=1688850308; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=659QQ5o0RJcYetO+FfSdtr0AtP1kq3MC1W2qbtyWfug=; b=dtNOaNk1U0c9VtA823XT9CmtDmYu0LuJlxIllw8Xz5Sj3c7CcaPNAH8CvVMDS1rdx6 s0gR5lbwLTTwiI3pFcY3DHZpu2p2Z9atuWcOHxaycHBfkYILiSQwf8k3QQs1eNexOUmS 6+0Aqxsqs3pOAqyV49ilBZ4VEbqH41IIutXxElBiDP+v3iMpwT+MtrZN4IcpAqsejWx9 Uw6JDVNKtsAIJmVheH3LhbNbQwrHFzoS7rbiR3crKDPpqEuOnXw0YUzXMz9qtl/l2Fxh JKU/jjLq3ytRsUC7bWCk0SRVHHVY20vzKE/Zp/HWeeEt982iTa0oszkdiIwHzRTq3Eq7 leQw== X-Gm-Message-State: AC+VfDzfvz3KCJA+u3f4mwvJUi4q7ECCSRlZDTtaIxkvbYy0Ki2rhg67 AvNigJW5+r73nr7XNYv5rA== X-Received: by 2002:a6b:fb12:0:b0:77a:c741:b749 with SMTP id h18-20020a6bfb12000000b0077ac741b749mr3956832iog.1.1686258307710; Thu, 08 Jun 2023 14:05:07 -0700 (PDT) Received: from robh_at_kernel.org ([64.188.179.250]) by smtp.gmail.com with ESMTPSA id i14-20020a02ca4e000000b00411b2414eb5sm490387jal.94.2023.06.08.14.05.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 08 Jun 2023 14:05:06 -0700 (PDT) Received: (nullmailer pid 3445498 invoked by uid 1000); Thu, 08 Jun 2023 21:05:04 -0000 Date: Thu, 8 Jun 2023 15:05:04 -0600 From: Rob Herring To: Guillaume Ranquet Cc: Chunfeng Yun , Kishon Vijay Abraham I , Vinod Koul , Krzysztof Kozlowski , Matthias Brugger , Chun-Kuang Hu , Philipp Zabel , David Airlie , Daniel Vetter , CK Hu , Jitao shi , linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Krzysztof Kozlowski , AngeloGioacchino Del Regno , mac.shen@mediatek.com, stuart.lee@mediatek.com Subject: Re: [PATCH v4 1/8] dt-bindings: display: mediatek: add MT8195 hdmi bindings Message-ID: <20230608210504.GA3436215-robh@kernel.org> References: <20220919-v4-0-687f09a06dd9@baylibre.com> <20220919-v4-1-687f09a06dd9@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220919-v4-1-687f09a06dd9@baylibre.com> X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00, FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no 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, May 29, 2023 at 04:30:58PM +0200, 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 the legacy "mediatek,hdmi-ddc" binding. > > Signed-off-by: Guillaume Ranquet > --- > .../bindings/display/mediatek/mediatek,hdmi.yaml | 59 ++++++++++++++++++---- > .../display/mediatek/mediatek,mt8195-hdmi-ddc.yaml | 45 +++++++++++++++++ > 2 files changed, 93 insertions(+), 11 deletions(-) > > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi.yaml > index b90b6d18a828..4f62e6b94048 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,10 @@ properties: > maxItems: 1 > > clocks: > - items: > - - description: Pixel Clock > - - description: HDMI PLL > - - description: Bit Clock > - - description: S/PDIF Clock > + maxItems: 4 > > clock-names: > - items: > - - const: pixel > - - const: pll > - - const: bclk > - - const: spdif > + maxItems: 4 > > phys: > maxItems: 1 > @@ -58,6 +51,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 +82,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 I don't understand how the same h/w block can have completely different clocks. If not the same h/w or evolution of the same h/w, then do a separate schema. > + > + 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..84c096835b47 > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,mt8195-hdmi-ddc.yaml > @@ -0,0 +1,45 @@ > +# 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 > + > + mediatek,hdmi: > + $ref: /schemas/types.yaml#/definitions/phandle > + description: > + A phandle to the mt8195 hdmi controller > + > +required: > + - compatible > + - clocks > + > +additionalProperties: false > + > +examples: > + - | > + #include > + #include > + hdmiddc0: i2c { > + compatible = "mediatek,mt8195-hdmi-ddc"; > + mediatek,hdmi = <&hdmi0>; > + clocks = <&clk26m>; How does one access this h/w device? There is nothing described to access it. Rob