From: Matthias Brugger <matthias.bgg@gmail.com>
To: Eddie Huang <eddie.huang@mediatek.com>
Cc: Henry Chen <henryc.chen@mediatek.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Sascha Hauer <kernel@pengutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: mt8173-evb: Add PMIC support
Date: Mon, 06 Jul 2015 18:39:59 +0200 [thread overview]
Message-ID: <1727643.5AqCaKisXT@ubix> (raw)
In-Reply-To: <1436168637.6986.6.camel@mtksdaap41>
On Monday, July 06, 2015 03:43:57 PM Eddie Huang wrote:
> Hi Matthias,
>
> On Mon, 2015-06-22 at 21:19 +0800, Henry Chen wrote:
> > From: Eddie Huang <eddie.huang@mediatek.com>
> >
> > The MT8173 eval board contains a MT6397 PMIC. This adds the
> > corresponding device node to the dts file.
> >
> > Signed-off-by: Henry Chen <henryc.chen@mediatek.com>
> > Signed-off-by: Eddie Huang <eddie.huang@mediatek.com>
> > ---
> > Base on 4.1-rc1 and commit as following,
> > ARM64: dts: Mediatek: MT8173 updates [1] and
> > clk: Add common clock support for Mediatek MT8135 and MT8173 [2] patch
> >
> > [1]
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-May/344751.htm
> > l [2]
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-April/338763.h
> > tml ---
> >
> > arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 174
> > ++++++++++++++++++++++++++++ 1 file changed, 174 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8173-evb.dts
> > b/arch/arm64/boot/dts/mediatek/mt8173-evb.dts index 43d5401..b967914
> > 100644
> > --- a/arch/arm64/boot/dts/mediatek/mt8173-evb.dts
> > +++ b/arch/arm64/boot/dts/mediatek/mt8173-evb.dts
> > @@ -33,6 +33,180 @@
> >
> > chosen { };
> >
> > };
> >
> > +&pwrap {
> > + pmic: mt6397 {
> > + compatible = "mediatek,mt6397";
> > + interrupt-parent = <&pio>;
> > + interrupts = <11 IRQ_TYPE_LEVEL_HIGH>;
> > + interrupt-controller;
> > + #interrupt-cells = <2>;
> > +
> > + mt6397regulator: mt6397regulator {
> > + compatible = "mediatek,mt6397-regulator";
> > + mt6397_vpca15_reg: buck_vpca15 {
> > + regulator-compatible = "buck_vpca15";
> > + regulator-name = "vpca15";
> > + regulator-min-microvolt = < 700000>;
> > + regulator-max-microvolt = <1350000>;
> > + regulator-ramp-delay = <12500>;
> > + regulator-always-on;
>
> I see you pull da9211 regulator dts patch, but not this one. How about
> this patch ?
I inserted some new-lines and added it to v4.2-next/arm64
Thanks,
Matthias
next prev parent reply other threads:[~2015-07-06 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 13:19 [PATCH] arm64: dts: mt8173-evb: Add PMIC support Henry Chen
[not found] ` <1434979177-7575-1-git-send-email-henryc.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-07-06 7:43 ` Eddie Huang
2015-07-06 16:39 ` Matthias Brugger [this message]
2015-07-07 3:09 ` Eddie Huang
2015-07-07 7:51 ` 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=1727643.5AqCaKisXT@ubix \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=eddie.huang@mediatek.com \
--cc=henryc.chen@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@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;
as well as URLs for NNTP newsgroup(s).