From: <sean.wang@mediatek.com>
To: <robh+dt@kernel.org>, <matthias.bgg@gmail.com>,
<mark.rutland@arm.com>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <jamesjj.liao@mediatek.com>,
<henryc.chen@mediatek.com>, <devicetree@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>
Cc: <chen.zhong@mediatek.com>, <chenglin.xu@mediatek.com>,
<linux-kernel@vger.kernel.org>,
Sean Wang <sean.wang@mediatek.com>
Subject: [PATCH 1/9] dt-bindings: arm: mediatek: add MT7622 string to the PMIC wrapper doc
Date: Sat, 3 Jun 2017 01:55:42 +0800 [thread overview]
Message-ID: <1cbdf094f3084bef016d24a25799ad7561f44a9e.1496425268.git.sean.wang@mediatek.com> (raw)
In-Reply-To: <cover.1496425268.git.sean.wang@mediatek.com>
From: Sean Wang <sean.wang@mediatek.com>
Signed-off-by: Chenglin Xu <chenglin.xu@mediatek.com>
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
---
Documentation/devicetree/bindings/soc/mediatek/pwrap.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt b/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
index 107700d..2d6d4a9 100644
--- a/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
+++ b/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
@@ -35,6 +35,10 @@ Required properties in pwrap device node.
"wrap": Main module clock
- clocks: Must contain an entry for each entry in clock-names.
+Required properties in pwrap device node
+- compatible:
+ "mediatek,mt7622-pwrap" for MT7622 SoCs
+
Optional properities:
- pmic: Mediatek PMIC MFD is the child device of pwrap
See the following for child node definitions:
--
1.9.1
next prev parent reply other threads:[~2017-06-02 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 17:55 [PATCH 0/9] Add PMIC support to MediaTek MT7622 SoC sean.wang
2017-06-02 17:55 ` sean.wang [this message]
2017-06-08 21:58 ` [PATCH 1/9] dt-bindings: arm: mediatek: add MT7622 string to the PMIC wrapper doc Rob Herring
2017-06-02 17:55 ` [PATCH 2/9] dt-bindings: regulator: Add document for MediaTek MT6380 regulator sean.wang
2017-06-08 22:01 ` Rob Herring
2017-06-02 17:55 ` [PATCH 3/9] regulator: mt6380: Add support for MT6380 sean.wang
2017-06-06 18:22 ` Mark Brown
2017-06-23 15:56 ` Sean Wang
2017-06-23 16:14 ` Mark Brown
2017-06-23 16:43 ` Sean Wang
2017-07-14 15:06 ` Sean Wang
2017-07-14 15:14 ` Mark Brown
2017-06-02 17:55 ` [PATCH 4/9] soc: mediatek: pwrap: add pwrap_read32 for reading in 32-bit mode sean.wang
2017-06-02 17:55 ` [PATCH 5/9] soc: mediatek: pwrap: add pwrap_write32 for writing " sean.wang
2017-06-02 17:55 ` [PATCH 6/9] soc: mediatek: pwrap: add pwrap_init pointer decided by the actual PMIC sean.wang
2017-06-02 17:55 ` [PATCH 7/9] soc: mediatek: pwrap: add MediaTek MT6380 as one slave of pwrap sean.wang
2017-06-02 17:55 ` [PATCH 8/9] soc: mediatek: pwrap: add support for MT7622 SoC sean.wang
2017-06-02 17:55 ` [PATCH 9/9] soc: mediatek: pwrap: fixup warnings from coding style sean.wang
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=1cbdf094f3084bef016d24a25799ad7561f44a9e.1496425268.git.sean.wang@mediatek.com \
--to=sean.wang@mediatek.com \
--cc=broonie@kernel.org \
--cc=chen.zhong@mediatek.com \
--cc=chenglin.xu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=henryc.chen@mediatek.com \
--cc=jamesjj.liao@mediatek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.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).