From: Fabien Parent <fparent@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@mediatek.com>
Cc: Fabien Parent <fparent@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH 1/4] dt-bindings: arm64: dts: mediatek: Add mt8195-demo board
Date: Sun, 27 Mar 2022 18:58:34 +0200 [thread overview]
Message-ID: <20220327165837.3048639-2-fparent@baylibre.com> (raw)
In-Reply-To: <20220327165837.3048639-1-fparent@baylibre.com>
Add bindings for the MediaTek mt8195-demo board.
Signed-off-by: Fabien Parent <fparent@baylibre.com>
---
Documentation/devicetree/bindings/arm/mediatek.yaml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.yaml b/Documentation/devicetree/bindings/arm/mediatek.yaml
index ab0593c77321..1f68afb19d81 100644
--- a/Documentation/devicetree/bindings/arm/mediatek.yaml
+++ b/Documentation/devicetree/bindings/arm/mediatek.yaml
@@ -131,6 +131,10 @@ properties:
- enum:
- mediatek,mt8183-evb
- const: mediatek,mt8183
+ - items:
+ - enum:
+ - mediatek,mt8195-demo
+ - const: mediatek,mt8195
- items:
- enum:
- mediatek,mt8195-evb
--
2.35.1
next parent reply other threads:[~2022-03-27 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220327165837.3048639-1-fparent@baylibre.com>
2022-03-27 16:58 ` Fabien Parent [this message]
2022-03-27 18:44 ` [PATCH 1/4] dt-bindings: arm64: dts: mediatek: Add mt8195-demo board Krzysztof Kozlowski
2022-03-27 16:58 ` [PATCH 2/4] arm64: dts: mediatek: Add device-tree for MT8195 Demo board Fabien Parent
2022-03-27 18:52 ` Krzysztof Kozlowski
2022-03-27 19:31 ` Fabien Parent
2022-03-27 16:58 ` [PATCH 3/4] arm64: defconfig: enable MT6359 regulator driver Fabien Parent
2022-03-27 16:58 ` [PATCH 4/4] arm64: defconfig: enable some mt6360 PMIC drivers Fabien Parent
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=20220327165837.3048639-2-fparent@baylibre.com \
--to=fparent@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--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=sean.wang@mediatek.com \
/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