Message ID | 20230614073125.17958-2-shawn.sung@mediatek.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:994d:0:b0:3d9:f83d:47d9 with SMTP id k13csp1074428vqr; Wed, 14 Jun 2023 01:09:03 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5vcLZk7/UbcsvgE/yecVkQU64Im4D+qi+PterMNvHijKgy9Y1uSAjtZX+QEjHdqjPidJ0N X-Received: by 2002:a05:6808:d50:b0:398:1c55:82bd with SMTP id w16-20020a0568080d5000b003981c5582bdmr11537309oik.45.1686730142582; Wed, 14 Jun 2023 01:09:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686730142; cv=none; d=google.com; s=arc-20160816; b=1BD2U3ODEA9vSKJbM3hb9MPxFom86N+vSyBqs0W1ZmPsF1oU7FvHZhcRbEj5u0aJMA 60tzRJB6CwyBbkT7PomY6iGn7tyjgGWtaSY39HNv/kCezxnIhsjQMA6Fpv33pt52mIAc bY/6yLxqONz00AKdjKVAN/0sP2gfnBEz0WQNc8qDL76Gl5NSKByMovRYmF19L4T5JEQw l3Hlvp4CEPiJxDPaIttfjQ8PrNyPYRGc0qXTipkx6gqV4XmAV/ETIiatQuHoDeZTmRO+ 4JizdOQ5aHvjND2J+SvVm57BQ/O6qzZupYNaabjoF68UB5SJ5r3vsFkqqsYhdFYtKDZ4 OOZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=0XfcLm2226ywh5z9orK1WYKPEry9DXdr8F7YQh+6JrA=; b=v/lZ+nSglrbwsTWn5hd0QFWXhk13px/De0GCwTEneW24dYuI66mRWT9U3TEK5QS7sS XOP2FxbF3DXO7Hpx8Qvw5sjs2NkzIjZdvPe0UQTUI5xr1mwD9SWiihaTszDnC5RUavL1 f2D+odmcCUaeJ79UW6TkLHZhkzXxgW5c6SaJ+EpvUGNjK5k2z3Ayi1iJI0OWsivv0GTW LEG62JkUn5W6p/bc5m9k9Dy9cjdS/DxTZN8t3yFx1oMzoRw8jfFfF9/P2hnyVTP5kqeF 0VwYkSy2JFqObRnLcTBv/80oZmakJ5U3da17ogUDCS8DgYuqqrPwRyOZ6wogoltGoBBP S8kQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mediatek.com header.s=dk header.b="jbv/DZts"; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=mediatek.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g1-20020a17090adac100b0024df18639fasi11944876pjx.154.2023.06.14.01.08.49; Wed, 14 Jun 2023 01:09:02 -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; dkim=pass header.i=@mediatek.com header.s=dk header.b="jbv/DZts"; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=mediatek.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243163AbjFNIAW (ORCPT <rfc822;jesperjuhl76@gmail.com> + 99 others); Wed, 14 Jun 2023 04:00:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35880 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234356AbjFNH7e (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 14 Jun 2023 03:59:34 -0400 Received: from mailgw01.mediatek.com (unknown [60.244.123.138]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CD7F01FD8; Wed, 14 Jun 2023 00:59:26 -0700 (PDT) X-UUID: 83ccbd5e0a8511ee9cb5633481061a41-20230614 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mediatek.com; s=dk; h=Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:CC:To:From; bh=0XfcLm2226ywh5z9orK1WYKPEry9DXdr8F7YQh+6JrA=; b=jbv/DZtsmefkred32iRQAmAz7jonPEj7XCWwbw0IKtCrzyU2BtmD4LqHRucZyYqWY6SP0TbeCPh3tC6pamIkd8VguujjJiAkJMx9o185GHQGtfr9Y7R/Z7GbS8/DwKAXghtT5+USP5uSfKA9BubP3KbqfJ7fQO1YVE/rEpcm5pU=; X-CID-P-RULE: Release_Ham X-CID-O-INFO: VERSION:1.1.26,REQID:d3a42462-69bd-40bb-8d63-2744909f67e7,IP:0,U RL:0,TC:0,Content:0,EDM:0,RT:0,SF:0,FILE:0,BULK:0,RULE:Release_Ham,ACTION: release,TS:0 X-CID-META: VersionHash:cb9a4e1,CLOUDID:1549933e-7aa7-41f3-a6bd-0433bee822f3,B ulkID:nil,BulkQuantity:0,Recheck:0,SF:102,TC:nil,Content:0,EDM:-3,IP:nil,U RL:0,File:nil,Bulk:nil,QS:nil,BEC:nil,COL:0,OSI:0,OSA:0,AV:0,LES:1,SPR:NO X-CID-BVR: 0 X-CID-BAS: 0,_,0,_ X-CID-FACTOR: TF_CID_SPAM_SNR X-UUID: 83ccbd5e0a8511ee9cb5633481061a41-20230614 Received: from mtkmbs11n1.mediatek.inc [(172.21.101.185)] by mailgw01.mediatek.com (envelope-from <shawn.sung@mediatek.com>) (Generic MTA with TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 256/256) with ESMTP id 829182747; Wed, 14 Jun 2023 15:31:45 +0800 Received: from mtkmbs13n2.mediatek.inc (172.21.101.108) by mtkmbs11n1.mediatek.inc (172.21.101.185) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Wed, 14 Jun 2023 15:31:43 +0800 Received: from mtksdccf07.mediatek.inc (172.21.84.99) by mtkmbs13n2.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.2.1118.26 via Frontend Transport; Wed, 14 Jun 2023 15:31:43 +0800 From: Hsiao Chien Sung <shawn.sung@mediatek.com> To: Chun-Kuang Hu <chunkuang.hu@kernel.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Philipp Zabel <p.zabel@pengutronix.de>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> CC: <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-mediatek@lists.infradead.org>, <devicetree@vger.kernel.org>, <Project_Global_Chrome_Upstream_Group@mediatek.com>, Singo Chang <singo.chang@mediatek.com>, Nancy Lin <nancy.lin@mediatek.com>, Jason-JH Lin <jason-jh.lin@mediatek.com>, Shawn Sung <shawn.sung@mediatek.com> Subject: [PATCH v2 01/15] dt-bindings: display: mediatek: ethdr: Add compatible for MT8188 Date: Wed, 14 Jun 2023 15:31:11 +0800 Message-ID: <20230614073125.17958-2-shawn.sung@mediatek.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20230614073125.17958-1-shawn.sung@mediatek.com> References: <20230614073125.17958-1-shawn.sung@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain X-MTK: N X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY,URIBL_BLOCKED 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1768664745701626973?= X-GMAIL-MSGID: =?utf-8?q?1768664745701626973?= |
Series |
Add display driver for MT8188 VDOSYS1
|
|
Commit Message
Shawn Sung (宋孝謙)
June 14, 2023, 7:31 a.m. UTC
Add compatible name for MediaTek MT8188 ETHDR.
Signed-off-by: Hsiao Chien Sung <shawn.sung@mediatek.com>
---
.../bindings/display/mediatek/mediatek,ethdr.yaml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--
2.18.0
Comments
Il 14/06/23 09:31, Hsiao Chien Sung ha scritto: > Add compatible name for MediaTek MT8188 ETHDR. > > Signed-off-by: Hsiao Chien Sung <shawn.sung@mediatek.com> > --- > .../bindings/display/mediatek/mediatek,ethdr.yaml | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml > index 801fa66ae615..677882348ede 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml > @@ -23,7 +23,11 @@ description: > > properties: > compatible: > - const: mediatek,mt8195-disp-ethdr > + oneOf: > + - const: mediatek,mt8195-disp-ethdr > + - items: > + - const: mediatek,mt8188-disp-ethdr > + - const: mediatek,mt8195-disp-ethdr > Is MT8188's ETHDR fully compatible with MT8195's ETHDR? If it is, you're not adding a mt8188 specific compatible string in the driver and this means that the devicetree will look like: compatible = "mediatek,mt8195-disp-ethdr", "mediatek,mt8188-disp-ethdr" ...so the proposed doc change works. Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > reg: > maxItems: 7 > -- > 2.18.0 >
Hi Angelo, Yes, MT8188 ETHDR is fully compatible with MT8195, so we didn't add its compatible name to the driver but just listed it in dt-bindings. May I double check with you that I see there is a short description regarding "items" object: > # items is a list of possible values for the property. The number of > # values is determined by the number of elements in the list. > # Order in lists is significant, order in dicts is not in https://docs.kernel.org/devicetree/bindings/writing-schema.html So does the compatible has to be: "mediatek,mt8188-disp-ethdr", "mediatek,mt8195-disp- ethdr" rather than in reversed order? However, I couldn't find any description mentions the order in Documentation/devicetree/bindings/writing-schema.rst Not sure if the order in "items" object does not matter after then. Thanks, Hsiao Chien Sung On Wed, 2023-06-14 at 13:41 +0200, AngeloGioacchino Del Regno wrote: > > External email : Please do not click links or open attachments until > you have verified the sender or the content. > Il 14/06/23 09:31, Hsiao Chien Sung ha scritto: > > Add compatible name for MediaTek MT8188 ETHDR. > > > > Signed-off-by: Hsiao Chien Sung <shawn.sung@mediatek.com> > > --- > > .../bindings/display/mediatek/mediatek,ethdr.yaml | 6 > +++++- > > 1 file changed, 5 insertions(+), 1 deletion(-) > > > > diff --git > a/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y > aml > b/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y > aml > > index 801fa66ae615..677882348ede 100644 > > --- > a/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y > aml > > +++ > b/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y > aml > > @@ -23,7 +23,11 @@ description: > > > > properties: > > compatible: > > - const: mediatek,mt8195-disp-ethdr > > + oneOf: > > + - const: mediatek,mt8195-disp-ethdr > > + - items: > > + - const: mediatek,mt8188-disp-ethdr > > + - const: mediatek,mt8195-disp-ethdr > > > > Is MT8188's ETHDR fully compatible with MT8195's ETHDR? > > If it is, you're not adding a mt8188 specific compatible string in > the driver and > this means that the devicetree will look like: > > compatible = "mediatek,mt8195-disp-ethdr", "mediatek,mt8188-disp- > ethdr" > > ...so the proposed doc change works. > > Reviewed-by: AngeloGioacchino Del Regno < > angelogioacchino.delregno@collabora.com> > > > reg: > > maxItems: 7 > > -- > > 2.18.0 > > > >
Il 15/06/23 07:51, Shawn Sung (宋孝謙) ha scritto: > Hi Angelo, > > Yes, MT8188 ETHDR is fully compatible with MT8195, so we didn't add its > compatible name to the driver but just listed it in dt-bindings. > > May I double check with you that > I see there is a short description regarding "items" object: >> # items is a list of possible values for the property. The number of >> # values is determined by the number of elements in the list. >> # Order in lists is significant, order in dicts is not > in https://docs.kernel.org/devicetree/bindings/writing-schema.html > > So does the compatible has to be: > "mediatek,mt8188-disp-ethdr", "mediatek,mt8195-disp- > ethdr" rather than in reversed order? > > However, I couldn't find any description mentions the order in > Documentation/devicetree/bindings/writing-schema.rst > Not sure if the order in "items" object does not matter after then. > No the order doesn't matter in that sense. If you check the other bindings, you'll see that the rule is to order by name, which your change as well does. It's fine. P.S.: In case you didn't know, `make dt_binding_check` and `make dtbs_check` will validate your bindings and your devicetrees against the bindings. Regards, Angelo > Thanks, > Hsiao Chien Sung > > > On Wed, 2023-06-14 at 13:41 +0200, AngeloGioacchino Del Regno wrote: >> >> External email : Please do not click links or open attachments until >> you have verified the sender or the content. >> Il 14/06/23 09:31, Hsiao Chien Sung ha scritto: >>> Add compatible name for MediaTek MT8188 ETHDR. >>> >>> Signed-off-by: Hsiao Chien Sung <shawn.sung@mediatek.com> >>> --- >>> .../bindings/display/mediatek/mediatek,ethdr.yaml | 6 >> +++++- >>> 1 file changed, 5 insertions(+), 1 deletion(-) >>> >>> diff --git >> a/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y >> aml >> b/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y >> aml >>> index 801fa66ae615..677882348ede 100644 >>> --- >> a/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y >> aml >>> +++ >> b/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y >> aml >>> @@ -23,7 +23,11 @@ description: >>> >>> properties: >>> compatible: >>> - const: mediatek,mt8195-disp-ethdr >>> + oneOf: >>> + - const: mediatek,mt8195-disp-ethdr >>> + - items: >>> + - const: mediatek,mt8188-disp-ethdr >>> + - const: mediatek,mt8195-disp-ethdr >>> >> >> Is MT8188's ETHDR fully compatible with MT8195's ETHDR? >> >> If it is, you're not adding a mt8188 specific compatible string in >> the driver and >> this means that the devicetree will look like: >> >> compatible = "mediatek,mt8195-disp-ethdr", "mediatek,mt8188-disp- >> ethdr" >> >> ...so the proposed doc change works. >> >> Reviewed-by: AngeloGioacchino Del Regno < >> angelogioacchino.delregno@collabora.com> >> >>> reg: >>> maxItems: 7 >>> -- >>> 2.18.0 >>> >> >>
On 14/06/2023 09:31, Hsiao Chien Sung wrote: > Add compatible name for MediaTek MT8188 ETHDR. > > Signed-off-by: Hsiao Chien Sung <shawn.sung@mediatek.com> > --- > .../bindings/display/mediatek/mediatek,ethdr.yaml | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml index 801fa66ae615..677882348ede 100644 --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml @@ -23,7 +23,11 @@ description: properties: compatible: - const: mediatek,mt8195-disp-ethdr + oneOf: + - const: mediatek,mt8195-disp-ethdr + - items: + - const: mediatek,mt8188-disp-ethdr + - const: mediatek,mt8195-disp-ethdr reg: maxItems: 7