From: Nina Wu <nina-cm.wu@mediatek.com>
To: Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Zhen Lei <thunder.leizhen@huawei.com>,
Nina Wu <Nina-CM.Wu@mediatek.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<srv_heupstream@mediatek.com>, <Jackson-kt.Chang@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: [PATCH v4 1/7] dt-bindings: devapc: Add 'vio-idx-num' field to support mt8192
Date: Tue, 25 May 2021 13:53:00 +0800 [thread overview]
Message-ID: <1621921986-20578-1-git-send-email-nina-cm.wu@mediatek.com> (raw)
From: Nina Wu <Nina-CM.Wu@mediatek.com>
For new ICs, there are multiple devapc HWs for different subsys.
We add a field 'vio-idx-num' in DT to indicate the number of
devices controlled by each devapc.
To be backward compatible with old ICs which have only one devapc
HW, this field is not required. The 'vio-idx-num' info will be set
in compatible data instead.
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Nina Wu <Nina-CM.Wu@mediatek.com>
---
Documentation/devicetree/bindings/soc/mediatek/devapc.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml b/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
index 31e4d3c..69abd03 100644
--- a/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
+++ b/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
@@ -20,11 +20,16 @@ properties:
compatible:
enum:
- mediatek,mt6779-devapc
+ - mediatek,mt8192-devapc
reg:
description: The base address of devapc register bank
maxItems: 1
+ mediatek,vio-idx-num:
+ description: The number of the devices controlled by devapc
+ $ref: /schemas/types.yaml#/definitions/uint32
+
interrupts:
description: A single interrupt specifier
maxItems: 1
--
2.6.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-05-25 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 5:53 Nina Wu [this message]
2021-05-25 5:53 ` [PATCH v4 2/7] soc: mediatek: devapc: get 'vio_idx_num' info from DT Nina Wu
2021-05-25 5:53 ` [PATCH v4 3/7] soc: mediatek: devapc: add shared flag to IRQ Nina Wu
2021-05-25 5:53 ` [PATCH v4 4/7] soc: mediatek: devapc: rename register variable infra_base Nina Wu
2021-05-25 5:53 ` [PATCH v4 5/7] soc: mediatek: devapc: add debug register for new IC support Nina Wu
2021-05-25 5:53 ` [PATCH v4 6/7] soc: mediatek: devapc: support mt8192 Nina Wu
2021-05-25 5:53 ` [PATCH v4 7/7] arm64: dts: mt8192: Add devapc node Nina Wu
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=1621921986-20578-1-git-send-email-nina-cm.wu@mediatek.com \
--to=nina-cm.wu@mediatek.com \
--cc=Jackson-kt.Chang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.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=srv_heupstream@mediatek.com \
--cc=thunder.leizhen@huawei.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;
as well as URLs for NNTP newsgroup(s).