From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-19.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C4120C47085 for ; Tue, 25 May 2021 00:02:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 929816142C for ; Tue, 25 May 2021 00:02:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229978AbhEYAEP (ORCPT ); Mon, 24 May 2021 20:04:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49462 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229875AbhEYAEJ (ORCPT ); Mon, 24 May 2021 20:04:09 -0400 Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2687AC061342 for ; Mon, 24 May 2021 17:02:40 -0700 (PDT) Received: by mail-pf1-x42f.google.com with SMTP id q67so5122893pfb.4 for ; Mon, 24 May 2021 17:02:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=aS2FXtbqE5xTeUczZX5p4dHrNjJBACW91SRGxxJRtNE=; b=lzpSd5rWPmHUsOwDcrWP2v3NS9aQ3jxCxECSbeE1gdkyj2kgaPc82gmiEoUIdAaTu6 nasPFE6JUYsDPQ5FrdRV93gW8cbba2QWfhYx+ybG6BPxXhPx2by4izujhsspt1vHyG1W hV4w2me2ESliNawtPsnpHKdEfJzfv1zLp1Xnk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=aS2FXtbqE5xTeUczZX5p4dHrNjJBACW91SRGxxJRtNE=; b=PAMi7ycZ39pEQKAnch0VTgcSEmTZYGj29vkR/GNUFRdTHJ7asowR+uzA2Szk6s2jtE nn3+qfP64GP4EYSqjBb7PJKhUuDU38ZcsJhlzclwT31KM/RiRlD7ead9xB75GpvX+P+k BqzFXzqZHO7MaRJRToZgq92xg6AcsLItWvZVrXV8wyiE9wP95it2E4OGKRvBMomCaAbT XSd4RIdgBptyCy+b7lNewLAzFXrHtBlYNdSk26Kpil/ZfxKSMSEZSeyT8aCNyqGNQQTW +sQ4ZbxOaW942ab8gEwA63uk2ra+z9ta8WiujMLsVTXU3XrSyzo7/DsAy3q9YVWrToJy mClg== X-Gm-Message-State: AOAM533Rwz7LROkVfFboxmGiX4dPirNAjlZzDN/dRAyyip39Nj3fpNg7 sKm1//l7wNkJaRxz8pCMH+QLag== X-Google-Smtp-Source: ABdhPJw/K4Ffsq5mJ1xUQPdTUkUfGUtNdW7pXLVPCAvIecDthB8kfmRjrEffJtTweMb5rHEKnvwxZg== X-Received: by 2002:a62:7f51:0:b029:2dc:e1c9:ef71 with SMTP id a78-20020a627f510000b02902dce1c9ef71mr27204538pfd.33.1621900959554; Mon, 24 May 2021 17:02:39 -0700 (PDT) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:201:26d1:4df0:7cdf:ce13]) by smtp.gmail.com with ESMTPSA id f18sm10696741pjh.55.2021.05.24.17.02.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 May 2021 17:02:39 -0700 (PDT) From: Douglas Anderson To: Andrzej Hajda , Neil Armstrong , Laurent Pinchart , Jonas Karlman , Sam Ravnborg Cc: linux-arm-msm@vger.kernel.org, Linus W , Lyude Paul , Bjorn Andersson , Steev Klimaszewski , robdclark@chromium.org, Maarten Lankhorst , Thierry Reding , dri-devel@lists.freedesktop.org, Stanislav Lisovskiy , Stephen Boyd , Douglas Anderson , Daniel Vetter , David Airlie , Rob Herring , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v8 02/11] dt-bindings: drm: Introduce the DP AUX bus Date: Mon, 24 May 2021 17:01:50 -0700 Message-Id: <20210524165920.v8.2.Id3c048d22e72a9f90084a543b5b4e3f43bc9ab62@changeid> X-Mailer: git-send-email 2.31.1.818.g46aad6cb9e-goog In-Reply-To: <20210525000159.3384921-1-dianders@chromium.org> References: <20210525000159.3384921-1-dianders@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org We want to be able to list an eDP panel as a child of an eDP controller node to represent the fact that the panel is connected to the controller's DP AUX bus. Though the panel and the controller are connected in several ways, the DP AUX bus is the primary control interface between the two and thus makes the most sense to model in device tree hierarchy. Listing a panel in this way makes it possible for the panel driver to easily get access to the DP AUX bus that it resides on, which can be useful to help in auto-detecting the panel and for turning on various bits. NOTE: historically eDP panels were _not_ listed under their controller but were listed at the top level of the device tree. This will still be supported for backward compatibility (and while DP controller drivers are adapted to support the new DT syntax) but should be considered deprecated since there is no downside to listing the panel under the controller. For now, the DP AUX bus bindings will only support an eDP panel underneath. It's possible it could be extended to allow having a DP connector under it in the future. The idea for this bus's design was hashed out over IRC [1]. [1] https://people.freedesktop.org/~cbrill/dri-log/?channel=dri-devel&date=2021-05-11 Signed-off-by: Douglas Anderson --- My DT yaml-fu is still weak. If I did something stupid, please help me learn how to do this better! NOTE: there is no "Example" in this bindings file. Yikes! This is because I wanted to keep this patch separate from the one that enables the first eDP controller. See the patch ("dt-bindings: drm/aux-bus: Add an example") for the example. ALSO: if anyone else would like to be listed as a "Maintainer" in this file then please shout! Changes in v8: - Separate DP AUX bus binding is new for v8. .../bindings/display/dp-aux-bus.yaml | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/dp-aux-bus.yaml diff --git a/Documentation/devicetree/bindings/display/dp-aux-bus.yaml b/Documentation/devicetree/bindings/display/dp-aux-bus.yaml new file mode 100644 index 000000000000..5e4afe9f98fb --- /dev/null +++ b/Documentation/devicetree/bindings/display/dp-aux-bus.yaml @@ -0,0 +1,37 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/dp-aux-bus.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: DisplayPort AUX bus + +maintainers: + - Douglas Anderson + +description: + DisplayPort controllers provide a control channel to the sinks that + are hooked up to them. This is the DP AUX bus. Over the DP AUX bus + we can query properties about a sink and also configure it. In + particular, DP sinks support DDC over DP AUX which allows tunneling + a standard I2C DDC connection over the AUX channel. + + To model this relationship, DP sinks should be placed as children + of the DP controller under the "aux-bus" node. + + At the moment, this binding only handles the eDP case. It is + possible it will be extended in the future to handle the DP case. + For DP, presumably a connector would be listed under the DP AUX + bus instead of a panel. + +properties: + $nodename: + const: "aux-bus" + + panel: + $ref: panel/panel-common.yaml# + +additionalProperties: false + +required: + - panel -- 2.31.1.818.g46aad6cb9e-goog