Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp756566ybm; Fri, 29 May 2020 11:21:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx/7tAN63WWAq/+zSW7PGd7IdMiICKlSyqf9dDznDOZtvE4wUsNpHRYCe+R1+/IgL42DaJU X-Received: by 2002:a05:6402:31ba:: with SMTP id dj26mr9239744edb.360.1590776472111; Fri, 29 May 2020 11:21:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590776472; cv=none; d=google.com; s=arc-20160816; b=EEg8Kdbg/dCmJmn6GMunRBPfIuGUDjWj7maTVAAg9QMKz6/dHhAJt0YXsXEy6g96TJ Hua9J1ZWTi1tOtG0QjPo3ywldiZ9yfRvH48dGqzThBz9kPv8YVzzLstiln6J215jaylR GAk7lOe0wBds20bj+UvJib8NW6dXqGK2BmW6crsR90UIOBmkmr4lKE5eoSWZ5xVqM/vX dhahUZ23ywhQhUbXsHk3grkt+JEczvuXkkqJcOfxFXM99hwtobRRiTzxCxkzopQROFZx siA9jENKf7zURGrLMMSZzQt4QSvD4P2lSGjO1WsFrQ+G20ectdOSC6fgC7F1CxtsEX5M 7uMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=+Zt0XlCRbQEAA6WM2kGlK/C6ChZT4zLq85OJJjGFn0o=; b=O0ImxitwcRUs+/3mqKqB/l94ygc1GOe1c7lbtAPzNCMmkCX/nDIcntFgU4FxEhZkNe NdXKoSI4kCqo5hu8wRAannxnMcVB2MPuoEqYXxBmdZOJ+wY2aNll/UBDAtkl9xAYLvcR tj9joYTsQoSHEV1FUJxSo2N8vR8adIDFXfBdGTzXc1mg6YluE6R25tZWq4wtUN+D5kCK tUI/NKfkvzSTKxzMy4p5fhm7LZBvf6FqrH1hBrFQ24iT9nlCThR/zre6S75CJlW6ZOov n4dcWaqSyn2jkb681+gHmlj4xTsyQ05bhEmMQrVQnE5Zaxaj+mQV22UaljaU7St10JLs uTAg== ARC-Authentication-Results: i=1; mx.google.com; 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 o4si1434000eje.269.2020.05.29.11.20.49; Fri, 29 May 2020 11:21:12 -0700 (PDT) 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; 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 S1727804AbgE2SSi (ORCPT + 99 others); Fri, 29 May 2020 14:18:38 -0400 Received: from mail-io1-f65.google.com ([209.85.166.65]:40617 "EHLO mail-io1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725839AbgE2SSi (ORCPT ); Fri, 29 May 2020 14:18:38 -0400 Received: by mail-io1-f65.google.com with SMTP id q8so331431iow.7; Fri, 29 May 2020 11:18:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=+Zt0XlCRbQEAA6WM2kGlK/C6ChZT4zLq85OJJjGFn0o=; b=GJivFlvt3y6X7Vmb7ySyS1RMdvuw9+XzYALE6D+fOmcSHUK919fhVEa0IeSQv/4hqD GACCMTwki/BZhun10i6Y9KQUCE4+xVmtipL4r/yiQ2O4/19DG/i4IrzSJKV9Xx9/SoEg 9e75ZfDUpznNycrYhvMB5APH99KFC6pN3Wv4T9WsUnlfP6+m1GL10wpR7wAubptJ+S+R 8uKTELPH+e55MnaM/uR4fJfg/LrrShOwkuWlWL/d7FyZdPk8i6Jhi5OzL5G62d1FNGU+ ebIxfCnnBqc277dxkNEuoo60IkT22ek0eOwen9/2YJ7OrtcwHvnF78deTo4FEuh2ytq+ PvGw== X-Gm-Message-State: AOAM532ZUn+RVrASnXFSGniLtbswcN3YqkRxJauvDVg8592Fe4nKLoWS KWmVyEAijrAf9/Ab9yO4Hw== X-Received: by 2002:a6b:5c19:: with SMTP id z25mr7597825ioh.119.1590776315569; Fri, 29 May 2020 11:18:35 -0700 (PDT) Received: from xps15 ([64.188.179.252]) by smtp.gmail.com with ESMTPSA id j63sm1246230ilg.50.2020.05.29.11.18.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 29 May 2020 11:18:34 -0700 (PDT) Received: (nullmailer pid 2691280 invoked by uid 1000); Fri, 29 May 2020 18:18:33 -0000 Date: Fri, 29 May 2020 12:18:33 -0600 From: Rob Herring To: Maxime Ripard Cc: Nicolas Saenz Julienne , Eric Anholt , dri-devel@lists.freedesktop.org, linux-rpi-kernel@lists.infradead.org, bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Dave Stevenson , Tim Gover , Phil Elwell , devicetree@vger.kernel.org Subject: Re: [PATCH v3 104/105] dt-bindings: display: vc4: hdmi: Add BCM2711 HDMI controllers bindings Message-ID: <20200529181833.GA2685451@bogus> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 27, 2020 at 05:49:14PM +0200, Maxime Ripard wrote: > The HDMI controllers found in the BCM2711 SoC need some adjustments to the > bindings, especially since the registers have been shuffled around in more > register ranges. > > Cc: Rob Herring > Cc: devicetree@vger.kernel.org > Signed-off-by: Maxime Ripard > --- > Documentation/devicetree/bindings/display/brcm,bcm2711-hdmi.yaml | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- > 1 file changed, 109 insertions(+) > create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2711-hdmi.yaml > > diff --git a/Documentation/devicetree/bindings/display/brcm,bcm2711-hdmi.yaml b/Documentation/devicetree/bindings/display/brcm,bcm2711-hdmi.yaml > new file mode 100644 > index 000000000000..6091fe3d315b > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/brcm,bcm2711-hdmi.yaml > @@ -0,0 +1,109 @@ > +# SPDX-License-Identifier: GPL-2.0 Dual license... > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/display/brcm,bcm2711-hdmi.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Broadcom BCM2711 HDMI Controller Device Tree Bindings > + > +maintainers: > + - Eric Anholt > + > +properties: > + compatible: > + enum: > + - brcm,bcm2711-hdmi0 > + - brcm,bcm2711-hdmi1 What's the difference between the 2 blocks? > + > + reg: > + items: > + - description: HDMI controller register range > + - description: DVP register range > + - description: HDMI PHY register range > + - description: Rate Manager register range > + - description: Packet RAM register range > + - description: Metadata RAM register range > + - description: CSC register range > + - description: CEC register range > + - description: HD register range > + > + reg-names: > + items: > + - const: hdmi > + - const: dvp > + - const: phy > + - const: rm > + - const: packet > + - const: metadata > + - const: csc > + - const: cec > + - const: hd > + > + clocks: > + description: The HDMI state machine clock > + > + clock-names: > + const: hdmi > + > + ddc: > + allOf: > + - $ref: /schemas/types.yaml#/definitions/phandle > + description: > > + Phandle of the I2C controller used for DDC EDID probing Goes in the connector. And isn't the standard name ddc-i2c-bus? > + > + hpd-gpios: > + description: > > + The GPIO pin for the HDMI hotplug detect (if it doesn't appear > + as an interrupt/status bit in the HDMI controller itself) Goes in the connector. > + > + dmas: > + maxItems: 1 > + description: > > + Should contain one entry pointing to the DMA channel used to > + transfer audio data. > + > + dma-names: > + const: audio-rx > + > + resets: > + maxItems: 1 > + > +required: > + - compatible > + - reg > + - reg-names > + - clocks > + - resets > + - ddc > + > +additionalProperties: false > + > +examples: > + - | > + hdmi0: hdmi@7ef00700 { > + compatible = "brcm,bcm2711-hdmi0"; > + reg = <0x7ef00700 0x300>, > + <0x7ef00300 0x200>, > + <0x7ef00f00 0x80>, > + <0x7ef00f80 0x80>, > + <0x7ef01b00 0x200>, > + <0x7ef01f00 0x400>, > + <0x7ef00200 0x80>, > + <0x7ef04300 0x100>, > + <0x7ef20000 0x100>; > + reg-names = "hdmi", > + "dvp", > + "phy", > + "rm", > + "packet", > + "metadata", > + "csc", > + "cec", > + "hd"; > + clocks = <&firmware_clocks 13>; > + clock-names = "hdmi"; > + resets = <&dvp 0>; > + ddc = <&ddc0>; > + }; > + > +... > -- > git-series 0.9.1