Message ID | 20230412112739.160376-3-angelogioacchino.delregno@collabora.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp249038vqo; Wed, 12 Apr 2023 04:29:13 -0700 (PDT) X-Google-Smtp-Source: AKy350Ytqf11jhHeHbW9JU914RD/oeCQzNl4rzSo3fcrtsA7xEb0jkLZhsEGbnaMZdkeOxy0iYNp X-Received: by 2002:a17:906:a2c3:b0:92f:b290:78c with SMTP id by3-20020a170906a2c300b0092fb290078cmr12688942ejb.21.1681298953531; Wed, 12 Apr 2023 04:29:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681298953; cv=none; d=google.com; s=arc-20160816; b=gNBa6jZ1Rd+Ce5jNJRAy2tpHDXM4XQIyoFeY/kznNDZPw84Tjg7iiXk7imn1gcDa46 CLRVBadDBLbQleCIlN8jXLi/sjOITP2VpilElr1kZnoHwiA4tNOBwegcy7JgQYH+tmAz 9zLONLNgtzKqSmG9GT72doWNZcjfa8/CwKKaKU6ojhLrxrdkGDRfpS8esJCOr6Y2orLy SqqulZqSfUmhH7MBBAI6JX+uYKgbB1/KINH/xdAIXrd8w0uNUjk0OY3IzLpul8rRZnNs L1ki+qx5MylgCc1QwJfhD1GQXWBnwqK8+7pScS2T5exbvbSUZ2RWARvJHlv/aO3Ivqnt F0xg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=sD3lBiiLUb06dq6C183mu1Eb+HlNCo2IoGiH8B3Vm6w=; b=RBuaW2M2JfOJgj9bJYNrSIbu8RjsH2MCrV2ufOhqLzKQaIWFEoBCUWmCeEXRPFUl3k D2aZ+pO87moSisMrw/VUlThix67EAfzM2HVuNuRoi+5UyHUAwnBPKrJ5169WfYPcZ9V7 0INByfeNfLbMxrE4S88AX07FrpIZajXvx0VY2mr2J7xeZ/FXvhQ10BqOWS52bnzVNBML n1O9nzG0+dPbN5SQE/XZed2NTO3ioV5nzVnnhfUKNmQJQBbSi13kulhvA5W22dWz81HF 8Lfx0qowzoE0zzJG4DzR9lGdK5uET3yYlA60GWBTj02R9RzqEGvGCmtUf3hxp3of6Vc8 8CyA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@collabora.com header.s=mail header.b=TaSKHO3s; 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=collabora.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ud24-20020a170907c61800b0094a44eda460si8892839ejc.87.2023.04.12.04.28.48; Wed, 12 Apr 2023 04:29:13 -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=@collabora.com header.s=mail header.b=TaSKHO3s; 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=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230340AbjDLL2M (ORCPT <rfc822;peter110.wang@gmail.com> + 99 others); Wed, 12 Apr 2023 07:28:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55716 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230224AbjDLL2D (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 12 Apr 2023 07:28:03 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [46.235.227.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 809002D40; Wed, 12 Apr 2023 04:27:49 -0700 (PDT) Received: from IcarusMOD.eternityproject.eu (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id D08DA660320D; Wed, 12 Apr 2023 12:27:46 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1681298868; bh=NzUsNWSsVvvmJv02n7djBLkN0Zq4SqWAI0O2gjnIL7g=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=TaSKHO3sqFHwQzFrGRDBpls+rHV/AP954ERZJw6yABDWUD5PIT4SKcKRFKQDqKDqF Cx57kdOJOjloHkvOGcyxZjFZa/CdgAJ9H8BYQ4L6FBhm7kjkcYJj4ToOTQQX/yxLag vc51ZMhp7l2xesHnA98ycICf28mCxFwhY02T9Qx/c4guG59O7y63UxwJ5B2Tc7XTr5 K9BdKBAVQujJ6o/z6dFYkN8P4arc0kpaB3BowYxcjqOiJ5ZbHmVf05YG38M06NytC3 /I9+60MfGHs92i3dGaXq3PgkHgi+hGUExGMNiNtDQwzHJft4thyWZE6LNM9VjPK4lQ zzCWvsYIj8CDw== From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> To: matthias.bgg@gmail.com Cc: p.zabel@pengutronix.de, airlied@gmail.com, daniel@ffwll.ch, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, jassisinghbrar@gmail.com, chunfeng.yun@mediatek.com, vkoul@kernel.org, kishon@kernel.org, thierry.reding@gmail.com, u.kleine-koenig@pengutronix.de, chunkuang.hu@kernel.org, angelogioacchino.delregno@collabora.com, ck.hu@mediatek.com, jitao.shi@mediatek.com, xinlei.lee@mediatek.com, houlong.wei@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-phy@lists.infradead.org, linux-pwm@vger.kernel.org, kernel@collabora.com, phone-devel@vger.kernel.org, ~postmarketos/upstreaming@lists.sr.ht Subject: [PATCH 02/27] dt-bindings: phy: mediatek,dsi-phy: Add compatible for MT6795 Helio X10 Date: Wed, 12 Apr 2023 13:27:14 +0200 Message-Id: <20230412112739.160376-3-angelogioacchino.delregno@collabora.com> X-Mailer: git-send-email 2.40.0 In-Reply-To: <20230412112739.160376-1-angelogioacchino.delregno@collabora.com> References: <20230412112739.160376-1-angelogioacchino.delregno@collabora.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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_NONE,SPF_PASS, 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?1762969731697890774?= X-GMAIL-MSGID: =?utf-8?q?1762969731697890774?= |
Series |
MediaTek Helio X10 - Mailbox, Display, MMC/SD/SDIO
|
|
Commit Message
AngeloGioacchino Del Regno
April 12, 2023, 11:27 a.m. UTC
Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses
the same DSI PHY as MT8173.
Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
---
Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++
1 file changed, 4 insertions(+)
Comments
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote: > Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses > the same DSI PHY as MT8173. > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > --- > Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml > index 26f2b887cfc1..a9f78344efdb 100644 > --- a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml > +++ b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml > @@ -24,6 +24,10 @@ properties: > - enum: > - mediatek,mt7623-mipi-tx > - const: mediatek,mt2701-mipi-tx > + - items: > + - enum: > + - mediatek,mt6795-mipi-tx > + - const: mediatek,mt8173-mipi-tx I suppose you expect more SoCs to share the same fallback in the future, apart from keeping in sync with other comaptibles described here, so: Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com> > - items: > - enum: > - mediatek,mt8365-mipi-tx
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote: > Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses > the same DSI PHY as MT8173. > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > --- > Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml > index 26f2b887cfc1..a9f78344efdb 100644 > --- a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml > +++ b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml > @@ -24,6 +24,10 @@ properties: > - enum: > - mediatek,mt7623-mipi-tx > - const: mediatek,mt2701-mipi-tx > + - items: > + - enum: > + - mediatek,mt6795-mipi-tx > + - const: mediatek,mt8173-mipi-tx AFAIK, it should be: - items: - const: mediatek,mt6795-mipi-tx - const: mediatek,mt8173-mipi-tx Since it isn't respected above for mt7623, it may be tolerated. Please, take this comment as a suggestion, isn't a NAK from me. > - items: > - enum: > - mediatek,mt8365-mipi-tx Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com>
Il 12/04/23 14:59, Alexandre Mergnat ha scritto: > On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote: >> Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses >> the same DSI PHY as MT8173. >> >> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> >> --- >> Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >> b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >> index 26f2b887cfc1..a9f78344efdb 100644 >> --- a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >> +++ b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >> @@ -24,6 +24,10 @@ properties: >> - enum: >> - mediatek,mt7623-mipi-tx >> - const: mediatek,mt2701-mipi-tx >> + - items: >> + - enum: >> + - mediatek,mt6795-mipi-tx >> + - const: mediatek,mt8173-mipi-tx > > AFAIK, it should be: > - items: > - const: mediatek,mt6795-mipi-tx > - const: mediatek,mt8173-mipi-tx > > Since it isn't respected above for mt7623, it may be tolerated. > Please, take this comment as a suggestion, isn't a NAK from me. > First of all, Thanks! I want to explain, though, the reason for that. If you check all the commits, on some I did it as you just proposed, while on some others I did it with an enum before const: that's simply because I *totally expect* some to grow, while others (const - const) I was either unsure, or totally *not* expecting them to grow soon! >> - items: >> - enum: >> - mediatek,mt8365-mipi-tx > > Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com> > Thanks again! Cheers, Angelo
On 12/04/2023 15:03, AngeloGioacchino Del Regno wrote: > Il 12/04/23 14:59, Alexandre Mergnat ha scritto: >> On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote: >>> Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses >>> the same DSI PHY as MT8173. >>> >>> Signed-off-by: AngeloGioacchino Del Regno >>> <angelogioacchino.delregno@collabora.com> >>> --- >>> Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++ >>> 1 file changed, 4 insertions(+) >>> >>> diff --git >>> a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>> b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>> index 26f2b887cfc1..a9f78344efdb 100644 >>> --- a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>> +++ b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>> @@ -24,6 +24,10 @@ properties: >>> - enum: >>> - mediatek,mt7623-mipi-tx >>> - const: mediatek,mt2701-mipi-tx >>> + - items: >>> + - enum: >>> + - mediatek,mt6795-mipi-tx >>> + - const: mediatek,mt8173-mipi-tx >> >> AFAIK, it should be: >> - items: >> - const: mediatek,mt6795-mipi-tx >> - const: mediatek,mt8173-mipi-tx >> >> Since it isn't respected above for mt7623, it may be tolerated. >> Please, take this comment as a suggestion, isn't a NAK from me. >> > > First of all, Thanks! > I want to explain, though, the reason for that. > > If you check all the commits, on some I did it as you just proposed, while > on some others I did it with an enum before const: that's simply because I > *totally expect* some to grow, while others (const - const) I was either > unsure, or totally *not* expecting them to grow soon! That's what I thought. IMHO, if someone add another compat later, he will be on charge to change the const by enum front of your "mediatek,mt6795-mipi-tx". But my opinion is probably not the most popular. I will not make the same feedback for the other patches in this series.
Il 12/04/23 15:12, Alexandre Mergnat ha scritto: > On 12/04/2023 15:03, AngeloGioacchino Del Regno wrote: >> Il 12/04/23 14:59, Alexandre Mergnat ha scritto: >>> On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote: >>>> Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses >>>> the same DSI PHY as MT8173. >>>> >>>> Signed-off-by: AngeloGioacchino Del Regno >>>> <angelogioacchino.delregno@collabora.com> >>>> --- >>>> Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++ >>>> 1 file changed, 4 insertions(+) >>>> >>>> diff --git a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>>> b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>>> index 26f2b887cfc1..a9f78344efdb 100644 >>>> --- a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>>> +++ b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>>> @@ -24,6 +24,10 @@ properties: >>>> - enum: >>>> - mediatek,mt7623-mipi-tx >>>> - const: mediatek,mt2701-mipi-tx >>>> + - items: >>>> + - enum: >>>> + - mediatek,mt6795-mipi-tx >>>> + - const: mediatek,mt8173-mipi-tx >>> >>> AFAIK, it should be: >>> - items: >>> - const: mediatek,mt6795-mipi-tx >>> - const: mediatek,mt8173-mipi-tx >>> >>> Since it isn't respected above for mt7623, it may be tolerated. >>> Please, take this comment as a suggestion, isn't a NAK from me. >>> >> >> First of all, Thanks! >> I want to explain, though, the reason for that. >> >> If you check all the commits, on some I did it as you just proposed, while >> on some others I did it with an enum before const: that's simply because I >> *totally expect* some to grow, while others (const - const) I was either >> unsure, or totally *not* expecting them to grow soon! > > > That's what I thought. IMHO, if someone add another compat later, he will be on > charge to change the const by enum front of your "mediatek,mt6795-mipi-tx". But my > opinion is probably not the most popular. > > I will not make the same feedback for the other patches in this series. > I honestly don't know what's the most popular opinion about that... but whatever, in any case... just want to make sure to communicate that I don't really have strong opinions about doing it one way or the other. The arguments in favor and against that are probably 1:1... :-D Cheers! Angelo
On 12/04/2023 15:17, AngeloGioacchino Del Regno wrote: > Il 12/04/23 15:12, Alexandre Mergnat ha scritto: >> On 12/04/2023 15:03, AngeloGioacchino Del Regno wrote: >>> Il 12/04/23 14:59, Alexandre Mergnat ha scritto: >>>> On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote: >>>>> Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses >>>>> the same DSI PHY as MT8173. >>>>> >>>>> Signed-off-by: AngeloGioacchino Del Regno >>>>> <angelogioacchino.delregno@collabora.com> >>>>> --- >>>>> Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++ >>>>> 1 file changed, 4 insertions(+) >>>>> >>>>> diff --git a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>>>> b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>>>> index 26f2b887cfc1..a9f78344efdb 100644 >>>>> --- a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>>>> +++ b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml >>>>> @@ -24,6 +24,10 @@ properties: >>>>> - enum: >>>>> - mediatek,mt7623-mipi-tx >>>>> - const: mediatek,mt2701-mipi-tx >>>>> + - items: >>>>> + - enum: >>>>> + - mediatek,mt6795-mipi-tx >>>>> + - const: mediatek,mt8173-mipi-tx >>>> >>>> AFAIK, it should be: >>>> - items: >>>> - const: mediatek,mt6795-mipi-tx >>>> - const: mediatek,mt8173-mipi-tx >>>> >>>> Since it isn't respected above for mt7623, it may be tolerated. >>>> Please, take this comment as a suggestion, isn't a NAK from me. >>>> >>> >>> First of all, Thanks! >>> I want to explain, though, the reason for that. >>> >>> If you check all the commits, on some I did it as you just proposed, while >>> on some others I did it with an enum before const: that's simply because I >>> *totally expect* some to grow, while others (const - const) I was either >>> unsure, or totally *not* expecting them to grow soon! >> >> >> That's what I thought. IMHO, if someone add another compat later, he will be >> on charge to change the const by enum front of your "mediatek,mt6795-mipi-tx". >> But my opinion is probably not the most popular. >> >> I will not make the same feedback for the other patches in this series. >> > > I honestly don't know what's the most popular opinion about that... but whatever, > in any case... just want to make sure to communicate that I don't really have > strong opinions about doing it one way or the other. > > The arguments in favor and against that are probably 1:1... :-D > Then let me throw in another one :) Take into account that if we expect the compatible to be added somtimes in the future (not the near future) this code will lay around for some time. People will take this code as an example for new code, then we will need to explain it... In that sense it would make more sense to have all made const: const: and change this to enum once a new compatible is added to the mix. Said all this, I leave it to the DT maintainers to decide :D Regards, Matthias
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote: > Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses > the same DSI PHY as MT8173. > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > --- > Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++ > 1 file changed, 4 insertions(+) Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
On 14/04/2023 10:22, Krzysztof Kozlowski wrote: > On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote: >> Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses >> the same DSI PHY as MT8173. >> >> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> >> --- >> Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4 ++++ >> 1 file changed, 4 insertions(+) > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > Best regards, > Krzysztof > Applied, thanks!
diff --git a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml index 26f2b887cfc1..a9f78344efdb 100644 --- a/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml +++ b/Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml @@ -24,6 +24,10 @@ properties: - enum: - mediatek,mt7623-mipi-tx - const: mediatek,mt2701-mipi-tx + - items: + - enum: + - mediatek,mt6795-mipi-tx + - const: mediatek,mt8173-mipi-tx - items: - enum: - mediatek,mt8365-mipi-tx