From: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>
Cc: Lala Lin <lala.lin@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
"Chen-Yu Tsai" <wenst@chromium.org>,
Allen-kh Cheng <allen-kh.cheng@mediatek.corp-partner.google.com>,
Allen-KH Cheng <allen-kh.cheng@mediatek.com>
Subject: [PATCH v4 2/3] dt-bindings: nvmem: mediatek: document deprecated efuse property
Date: Tue, 10 May 2022 21:26:36 +0800 [thread overview]
Message-ID: <20220510132637.5864-3-allen-kh.cheng@mediatek.com> (raw)
In-Reply-To: <20220510132637.5864-1-allen-kh.cheng@mediatek.com>
From: Allen-kh Cheng <allen-kh.cheng@mediatek.corp-partner.google.com>
We mark mediatek,mt8173-efuse and mediatek,efuse as deprecated to
prevent them from being the single compatible in the future.
The mediatek,efuse compatible should be used as generic fallback for
all MediaTek chipsets.
Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
---
.../devicetree/bindings/nvmem/mediatek,efuse.yaml | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml b/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
index 529f5888d93f..04ecf5980b2e 100644
--- a/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
+++ b/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
@@ -16,16 +16,18 @@ allOf:
properties:
compatible:
oneOf:
- - enum:
- - mediatek,mt8173-efuse
- - mediatek,efuse
+ - const: mediatek,mt8173-efuse # Don't use this in new dts files
+ deprecated: true
+ - const: mediatek,efuse
+ deprecated: true
description:
- Only mt8173 SoC-specific compatible with generic fallback should be
- used
+ Please use mediatek,efuse as generic fallback to enable the MediaTek
+ eFuse support.
- items:
- enum:
- mediatek,mt7622-efuse
- mediatek,mt7623-efuse
+ - mediatek,mt8173-efuse
- mediatek,mt8183-efuse
- mediatek,mt8192-efuse
- mediatek,mt8195-efuse
@@ -44,7 +46,8 @@ unevaluatedProperties: false
examples:
- |
efuse: efuse@10206000 {
- compatible = "mediatek,mt8173-efuse";
+ compatible = "mediatek,mt8173-efuse",
+ "mediatek,efuse";
reg = <0x10206000 0x1000>;
#address-cells = <1>;
#size-cells = <1>;
--
2.18.0
next prev parent reply other threads:[~2022-05-10 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 13:26 [PATCH v4 0/3] dt-bindings: nvmem: mediatek: Convert efuse binding to YAML Allen-KH Cheng
2022-05-10 13:26 ` [PATCH v4 1/3] " Allen-KH Cheng
2022-05-11 15:16 ` Krzysztof Kozlowski
2022-05-10 13:26 ` Allen-KH Cheng [this message]
2022-05-11 15:20 ` [PATCH v4 2/3] dt-bindings: nvmem: mediatek: document deprecated efuse property Krzysztof Kozlowski
2022-05-10 13:26 ` [PATCH v4 3/3] arm64: dts: mediatek: update efuse compatible fallbacks Allen-KH Cheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220510132637.5864-3-allen-kh.cheng@mediatek.com \
--to=allen-kh.cheng@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.corp-partner.google.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lala.lin@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=wenst@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®