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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 57D0AC43334 for ; Thu, 16 Jun 2022 21:29:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=rdHzdInDXh//gMknbVdBwAraX19GeKLczZTJ3raOyKQ=; b=p2HCzX8wtMB/uW 8Oa7+4zQSg/YhMlWqEQrRFHQmDtzOqzWOGr4jRVOzgpVkedaQV4HeqDM4/GUiMYiZdZQ3sNucbfiK nfuOVLEyqNljfdl7cLnm2ZzxcfH71MK5i27VlMcQ7qGNCqvmUy9vChQC0j3KsLsLRULAXGbJmLlca aKXmRahkDapISWBkciaeolvZNl5eJMAIzXtyYfVczVenR4QiDYV7xBRysa44R1JVIfXEEUFpLN6vg Ej07x81RWW1j7Oh4Wu99i3f8H+3qYgwj9N6MBkPtr/YevRDsCvTjvweL8PRbbEshmtwUNkPQo5FNJ 9Ox/3d8dYTl4nlqhBcHw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o1x2N-004R7f-99; Thu, 16 Jun 2022 21:28:23 +0000 Received: from mail-il1-f172.google.com ([209.85.166.172]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o1x2I-004R4H-81; Thu, 16 Jun 2022 21:28:19 +0000 Received: by mail-il1-f172.google.com with SMTP id d6so1789522ilm.4; Thu, 16 Jun 2022 14:28:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=p2fPALb1JPQ4AHcfCxgMf5Jxk8npv4hWtBM7JpKyakw=; b=McoR5V6bYryOcUwMxx1kqJjJTXPx4QluFmSdoCpnBKZJyh1CW0fsrnLVd85cqlAG/g cgCgcGikLS7lo1bSxjVo0uVY2VOp6/385nk483cZDDB9yx32uy+DHafEePpPQ0ksfhej 6ow3JxBAF+qZ6e7AQBK2016kiIhIlEIZFvdwZ6Udsg3SYn1Zsx+PPv3ktn2w1uyuKzUe WMhK0N1Fn7jTWX4FZSUGjzPQebz8CEesN2HntDE8W5TvC0rCd/XsipzgjrnmWRkWX/Bm 45X+/3uEHuJySmypqIRQZJAeFVx3P8hqh6PWvgFnJpJH/qZLAk9uqq/mhd2opy/W7T+D jNhg== X-Gm-Message-State: AJIora+nSfk4ajmSQTofiow5/97CrOSM28IQNemySQOTbZFtsqBasufJ QlsNjrfj15vYqWCJhkXa+g== X-Google-Smtp-Source: AGRyM1vXz8zr1qepnCDtLqZTRG9xKb9gNBJydHo8HDS0dVqWruV80818zrXGU2iTTEoR7y/TLi/J4w== X-Received: by 2002:a05:6e02:1bc8:b0:2d4:342:9c68 with SMTP id x8-20020a056e021bc800b002d403429c68mr4075981ilv.254.1655414896016; Thu, 16 Jun 2022 14:28:16 -0700 (PDT) Received: from robh.at.kernel.org ([64.188.179.251]) by smtp.gmail.com with ESMTPSA id j8-20020a02a688000000b003314f874ac8sm1357939jam.36.2022.06.16.14.28.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Jun 2022 14:28:15 -0700 (PDT) Received: (nullmailer pid 4024739 invoked by uid 1000); Thu, 16 Jun 2022 21:28:13 -0000 Date: Thu, 16 Jun 2022 15:28:13 -0600 From: Rob Herring To: Rex-BC Chen Cc: chunkuang.hu@kernel.org, p.zabel@pengutronix.de, daniel@ffwll.ch, krzysztof.kozlowski+dt@linaro.org, mripard@kernel.org, tzimmermann@suse.de, matthias.bgg@gmail.com, deller@gmx.de, airlied@linux.ie, msp@baylibre.com, granquet@baylibre.com, jitao.shi@mediatek.com, wenst@chromium.org, angelogioacchino.delregno@collabora.com, ck.hu@mediatek.com, dri-devel@lists.freedesktop.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-fbdev@vger.kernel.org, Project_Global_Chrome_Upstream_Group@mediatek.com Subject: Re: [PATCH v11 01/10] dt-bindings: mediatek,dp: Add Display Port binding Message-ID: <20220616212813.GA3991754-robh@kernel.org> References: <20220610105522.13449-1-rex-bc.chen@mediatek.com> <20220610105522.13449-2-rex-bc.chen@mediatek.com> <20220614202336.GA2400714-robh@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220616_142818_325059_93F5A47E X-CRM114-Status: GOOD ( 28.28 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Jun 16, 2022 at 09:22:16PM +0800, Rex-BC Chen wrote: > On Tue, 2022-06-14 at 14:23 -0600, Rob Herring wrote: > > On Fri, Jun 10, 2022 at 06:55:13PM +0800, Bo-Chen Chen wrote: > > > From: Markus Schneider-Pargmann > > > > > > This controller is present on several mediatek hardware. Currently > > > mt8195 and mt8395 have this controller without a functional > > > difference, > > > so only one compatible field is added. > > > > > > The controller can have two forms, as a normal display port and as > > > an > > > embedded display port. > > > > > > Signed-off-by: Markus Schneider-Pargmann > > > Signed-off-by: Guillaume Ranquet > > > [Bo-Chen: Fix reviewers' comment] > > > Signed-off-by: Bo-Chen Chen > > > --- > > > .../display/mediatek/mediatek,dp.yaml | 101 > > > ++++++++++++++++++ > > > 1 file changed, 101 insertions(+) > > > create mode 100644 > > > Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml > > > > > > diff --git > > > a/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.ya > > > ml > > > b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.ya > > > ml > > > new file mode 100644 > > > index 000000000000..10f50a0dcf49 > > > --- /dev/null > > > +++ > > > b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.ya > > > ml > > > @@ -0,0 +1,101 @@ > > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > > +%YAML 1.2 > > > +--- > > > +$id: > > > https://urldefense.com/v3/__http://devicetree.org/schemas/display/mediatek/mediatek,dp.yaml*__;Iw!!CTRNKA9wMg0ARbw!yqAl1KhfbHqHN7-5aeqhzqeOVhPU_Z5beko5q-y-s5pcfp1WL5oVGvY5UF4EfWm4PWjc5mjBwyBUMsr_RI45ipbhsw$ > > > > > > +$schema: > > > https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml*__;Iw!!CTRNKA9wMg0ARbw!yqAl1KhfbHqHN7-5aeqhzqeOVhPU_Z5beko5q-y-s5pcfp1WL5oVGvY5UF4EfWm4PWjc5mjBwyBUMsr_RI5WzYKENQ$ > > > > > > + > > > +title: MediaTek Display Port Controller > > > + > > > +maintainers: > > > + - Chun-Kuang Hu > > > + - Jitao shi > > > + > > > +description: | > > > + Device tree bindings for the MediaTek display port and > > > + embedded display port controller present on some MediaTek SoCs. > > > + > > > +properties: > > > + compatible: > > > + enum: > > > + - mediatek,mt8195-dp-tx > > > + - mediatek,mt8195-edp-tx > > > + > > > + reg: > > > + maxItems: 1 > > > + > > > + nvmem-cells: > > > + maxItems: 1 > > > + description: efuse data for display port calibration > > > + > > > + nvmem-cell-names: > > > + const: dp_calibration_data > > > + > > > + power-domains: > > > + maxItems: 1 > > > + > > > + interrupts: > > > + maxItems: 1 > > > + > > > + ports: > > > + $ref: /schemas/graph.yaml#/properties/ports > > > + properties: > > > + port@0: > > > + $ref: /schemas/graph.yaml#/properties/port > > > + description: Input endpoint of the controller, usually > > > dp_intf > > > + > > > + port@1: > > > + $ref: /schemas/graph.yaml#/properties/port > > > + description: Output endpoint of the controller > > > + > > > + required: > > > + - port@0 > > > + - port@1 > > > + > > > + max-lanes: > > > + maxItems: 1 > > > + description: maximum number of lanes supported by the > > > hardware. > > > > We already have a 'data-lanes' property defined in > > 'video-interfaces.yaml' that can serve this purpose. > > > > Hello Rob, > > Thanks for review. > From the description of video-interfaces.yaml, I think it's not quite > match what we need. We only need this value be one of "1,2,4". data-lanes = <0>; data-lanes = <0 1>; data-lanes = <0 1 2 3>; Limiting the number of lanes to something less than the max is exactly how this property is used in addition to being able to show the mapping of lanes. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel