From: Matthias Brugger <matthias.bgg@gmail.com>
To: Erin Lo <erin.lo@mediatek.com>
Cc: srv_heupstream@mediatek.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Zhiyong Tao <zhiyong.tao@mediatek.com>
Subject: Re: [PATCH v2 4/6] arm: dts: mt2701: Add auxadc device node.
Date: Fri, 13 Jan 2017 16:29:25 +0100 [thread overview]
Message-ID: <341850d0-6f32-9288-4399-96f0d2d00c6f@gmail.com> (raw)
In-Reply-To: <1484296978-18572-5-git-send-email-erin.lo@mediatek.com>
On 13/01/17 09:42, Erin Lo wrote:
> From: Zhiyong Tao <zhiyong.tao@mediatek.com>
>
> Add auxadc device node for MT2701.
>
> Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
> Signed-off-by: Erin Lo <erin.lo@mediatek.com>
> ---
> arch/arm/boot/dts/mt2701-evb.dts | 4 ++++
> arch/arm/boot/dts/mt2701.dtsi | 9 +++++++++
> 2 files changed, 13 insertions(+)
>
Applied to v4.10-next/dts32
> diff --git a/arch/arm/boot/dts/mt2701-evb.dts b/arch/arm/boot/dts/mt2701-evb.dts
> index 879f1eb..a483798 100644
> --- a/arch/arm/boot/dts/mt2701-evb.dts
> +++ b/arch/arm/boot/dts/mt2701-evb.dts
> @@ -24,6 +24,10 @@
> };
> };
>
> +&auxadc {
> + status = "okay";
> +};
> +
> &pio {
> spi_pins_a: spi0@0 {
> pins_spi {
> diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
> index 1182c43..4f52019 100644
> --- a/arch/arm/boot/dts/mt2701.dtsi
> +++ b/arch/arm/boot/dts/mt2701.dtsi
> @@ -208,6 +208,15 @@
> <0 0x10216000 0 0x2000>;
> };
>
> + auxadc: adc@11001000 {
> + compatible = "mediatek,mt2701-auxadc";
> + reg = <0 0x11001000 0 0x1000>;
> + clocks = <&pericfg CLK_PERI_AUXADC>;
> + clock-names = "main";
> + #io-channel-cells = <1>;
> + status = "disabled";
> + };
> +
> uart0: serial@11002000 {
> compatible = "mediatek,mt2701-uart",
> "mediatek,mt6577-uart";
>
next prev parent reply other threads:[~2017-01-13 15:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 8:42 [PATCH v2 0/6] Add some DT nodes for Mediatek MT2701 Erin Lo
[not found] ` <1484296978-18572-1-git-send-email-erin.lo-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-01-13 8:42 ` [PATCH v2 1/6] arm: dts: mt2701: Add spi device node Erin Lo
[not found] ` <1484296978-18572-2-git-send-email-erin.lo-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-01-13 15:29 ` Matthias Brugger
2017-01-13 8:42 ` [PATCH v2 2/6] arm: dts: mt2701: Add iommu/smi " Erin Lo
2017-01-13 15:05 ` Matthias Brugger
2017-01-16 2:54 ` Honghui Zhang
2017-01-13 8:42 ` [PATCH v2 4/6] arm: dts: mt2701: Add auxadc " Erin Lo
2017-01-13 15:29 ` Matthias Brugger [this message]
2017-01-13 8:42 ` [PATCH v2 5/6] arm: dts: mt2701: Add ethernet " Erin Lo
[not found] ` <1484296978-18572-6-git-send-email-erin.lo-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-01-14 10:32 ` John Crispin
2017-01-14 16:10 ` Sean Wang
2017-01-13 8:42 ` [PATCH v2 3/6] arm: dts: mt2701: Add nand " Erin Lo
2017-01-13 15:29 ` Matthias Brugger
2017-01-13 8:42 ` [PATCH v2 6/6] arm: dts: mt2701: Add thermal " Erin Lo
2017-01-13 15:27 ` Matthias Brugger
2017-01-16 3:44 ` Dawei Chien
2017-01-16 3:46 ` Dawei Chien
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=341850d0-6f32-9288-4399-96f0d2d00c6f@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=erin.lo@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=srv_heupstream@mediatek.com \
--cc=zhiyong.tao@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