From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: <sean.wang@mediatek.com>
Cc: <robh+dt@kernel.org>, <matthias.bgg@gmail.com>,
<mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <john@phrozen.org>
Subject: Re: [PATCH v5 03/10] arm: dts: mt7623: add mt6323.dtsi file
Date: Wed, 2 Aug 2017 09:47:57 +0800 [thread overview]
Message-ID: <1501638477.32089.20.camel@mtksdaap41> (raw)
In-Reply-To: <f92864cf04cc3ddde20f25d402d8e5d3d915b2a8.1501486190.git.sean.wang@mediatek.com>
On Mon, 2017-07-31 at 15:36 +0800, sean.wang@mediatek.com wrote:
<...>
> diff --git a/arch/arm/boot/dts/mt7623-evb.dts b/arch/arm/boot/dts/mt7623-evb.dts
> index b60b41c..0686ad7 100644
> --- a/arch/arm/boot/dts/mt7623-evb.dts
> +++ b/arch/arm/boot/dts/mt7623-evb.dts
> @@ -14,6 +14,7 @@
>
> /dts-v1/;
> #include "mt7623.dtsi"
> +#include "mt6323.dtsi"
>
> / {
> model = "MediaTek MT7623 evaluation board";
> @@ -23,6 +24,24 @@
> stdout-path = &uart2;
> };
>
> + cpus {
> + cpu0 {
> + proc-supply = <&mt6323_vproc_reg>;
> + };
> +
> + cpu1 {
> + proc-supply = <&mt6323_vproc_reg>;
> + };
> +
> + cpu2 {
> + proc-supply = <&mt6323_vproc_reg>;
> + };
> +
> + cpu3 {
> + proc-supply = <&mt6323_vproc_reg>;
> + };
> + };
> +
> memory {
> reg = <0 0x80000000 0 0x40000000>;
> };
> @@ -31,3 +50,13 @@
> &uart2 {
> status = "okay";
> };
> +
> +&mmc0 {
> + vmmc-supply = <&mt6323_vemc3v3_reg>;
> + vqmmc-supply = <&mt6323_vio18_reg>;
> +};
> +
> +&mmc1 {
> + vmmc-supply = <&mt6323_vmch_reg>;
> + vqmmc-supply = <&mt6323_vmc_reg>;
> +};
Please keep nodes sorted.
Joe.C
next prev parent reply other threads:[~2017-08-02 1:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 7:36 [PATCH v5 00/10] arm: dts: extend mt7623 support sean.wang
2017-07-31 7:36 ` [PATCH v5 01/10] dt-bindings: arm: mediatek: update for MT7623n SoC and relevant boards sean.wang
2017-07-31 7:36 ` [PATCH v5 02/10] dt-bindings: arm: mediatek: add bindings for mediatek MT7623a SoC Platform sean.wang
2017-07-31 7:36 ` [PATCH v5 03/10] arm: dts: mt7623: add mt6323.dtsi file sean.wang
2017-08-02 1:47 ` Yingjoe Chen [this message]
2017-08-02 2:02 ` Sean Wang
2017-07-31 7:36 ` [PATCH v5 04/10] arm: dts: mt7623: rename mt7623-evb.dts to arch/arm/boot/dts/mt7623n-rfb.dtsi sean.wang
2017-07-31 7:36 ` [PATCH v5 05/10] ARM: mediatek: add MT7623a smp bringup code sean.wang
2017-07-31 7:36 ` [PATCH v5 06/10] arm: dts: mt7623: cleanup the mt7623n rfb uart nodes sean.wang
2017-07-31 7:36 ` [PATCH v5 07/10] arm: dts: mt7623: enable the usb device on the mt7623n rfb sean.wang
2017-07-31 7:36 ` [PATCH v5 08/10] arm: dts: mt7623: enable the nand device on the mt7623n nand rfb sean.wang
2017-07-31 7:36 ` [PATCH v5 09/10] arm: dts: mt7623: add support for Bananapi R2 (BPI-R2) board sean.wang
2017-07-31 7:36 ` [PATCH v5 10/10] arm: dts: mt7623: add clock-frequency to CPU nodes sean.wang
2017-08-01 12:05 ` [PATCH v5 00/10] arm: dts: extend mt7623 support 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=1501638477.32089.20.camel@mtksdaap41 \
--to=yingjoe.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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 \
--cc=sean.wang@mediatek.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