From: sean.wang@mediatek.com (Sean Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] dt-bindings: pwrap: mediatek: add MT6351 PMIC support for MT6797
Date: Tue, 23 Jan 2018 15:55:49 +0800 [thread overview]
Message-ID: <1516694149.12197.25.camel@mtkswgap22> (raw)
In-Reply-To: <20180123033659.11401-1-argus.lin@mediatek.com>
On Tue, 2018-01-23 at 11:36 +0800, argus.lin at mediatek.com wrote:
> From: Argus Lin <argus.lin@mediatek.com>
>
> We add MT6351 PMIC support for MT6797 SoCs.
>
> Change-Id: I362b2305f674813ffb03ce6f54f7fc4c378b8fd2
should remove change-id, also in the other patches
> Signed-off-by: Argus Lin <argus.lin@mediatek.com>
> ---
> Documentation/devicetree/bindings/soc/mediatek/pwrap.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt b/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
> index bf80e3f96f8c..dd573ba5d9a7 100644
> --- a/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
> +++ b/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
> @@ -22,6 +22,7 @@ Required properties in pwrap device node.
> "mediatek,mt7622-pwrap" for MT7622 SoCs
> "mediatek,mt8135-pwrap" for MT8135 SoCs
> "mediatek,mt8173-pwrap" for MT8173 SoCs
> + "mediatek,mt6797-pwrap" for MT6797 SoCs
should be better if add it in alphabetical order
> - interrupts: IRQ for pwrap in SOC
> - reg-names: Must include the following entries:
> "pwrap": Main registers base
next parent reply other threads:[~2018-01-23 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180123033659.11401-1-argus.lin@mediatek.com>
2018-01-23 7:55 ` Sean Wang [this message]
[not found] ` <20180123033659.11401-3-argus.lin@mediatek.com>
2018-01-24 15:12 ` [PATCH 3/3] soc: mediatek: pwrap: add mt6351 for mt6797 SoCs Matthias Brugger
[not found] ` <20180123033659.11401-2-argus.lin@mediatek.com>
2018-01-24 15:13 ` [PATCH 2/3] arm64: dts: mt6797: add pwrap support for mt6797 Matthias Brugger
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=1516694149.12197.25.camel@mtkswgap22 \
--to=sean.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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