From: Tinghan Shen <tinghan.shen@mediatek.com>
To: Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"Tinghan Shen" <tinghan.shen@mediatek.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Sean Christopherson" <seanjc@google.com>,
<maciej.szmigiero@oracle.com>,
"David Matlack" <dmatlack@google.com>,
Jing Zhang <jingzhangos@google.com>,
"Marc Zyngier" <maz@kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Sean Wang <sean.wang@mediatek.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<ryder.lee@kernel.org>, <wenst@chromium.org>,
<chunfeng.yun@mediatek.com>
Subject: [PATCH v9 1/3] dt-bindings: arm: mediatek: Add mt8195 pericfg compatible
Date: Wed, 12 Jan 2022 19:47:22 +0800 [thread overview]
Message-ID: <20220112114724.1953-2-tinghan.shen@mediatek.com> (raw)
In-Reply-To: <20220112114724.1953-1-tinghan.shen@mediatek.com>
Add mt8195 pericfg compatible to binding document.
Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
---
.../devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
index 8723dfe34bab..611f666f359d 100644
--- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
+++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
@@ -26,6 +26,7 @@ properties:
- mediatek,mt8135-pericfg
- mediatek,mt8173-pericfg
- mediatek,mt8183-pericfg
+ - mediatek,mt8195-pericfg
- mediatek,mt8516-pericfg
- const: syscon
- items:
--
2.18.0
next prev parent reply other threads:[~2022-01-12 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:47 [PATCH v9 0/3] Add basic SoC support for mediatek mt8195 Tinghan Shen
2022-01-12 11:47 ` Tinghan Shen [this message]
2022-01-12 11:47 ` [PATCH v9 2/3] dt-bindings: pinctrl: mt8195: Add mediatek,drive-strength-adv property Tinghan Shen
2022-01-13 16:31 ` Matthias Brugger
2022-01-25 6:21 ` Tinghan Shen
2022-01-30 0:38 ` Linus Walleij
2022-02-22 9:18 ` Tinghan Shen
2022-01-12 11:47 ` [PATCH v9 3/3] arm64: dts: Add mediatek SoC mt8195 and evaluation board Tinghan Shen
2022-01-12 14:54 ` [PATCH v9 0/3] Add basic SoC support for mediatek mt8195 Maciej S. Szmigiero
2022-01-13 2:17 ` Tinghan Shen
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=20220112114724.1953-2-tinghan.shen@mediatek.com \
--to=tinghan.shen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bgolaszewski@baylibre.com \
--cc=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmatlack@google.com \
--cc=jingzhangos@google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maciej.szmigiero@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=seanjc@google.com \
--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;
as well as URLs for NNTP newsgroup(s).