linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	Xiaolei Li <xiaolei.li@mediatek.com>
Subject: Re: [PATCH v2 3/6] arm: dts: mt2701: Add nand device node
Date: Fri, 13 Jan 2017 16:29:17 +0100	[thread overview]
Message-ID: <eedd5138-049e-419e-edb4-51be7f75be97@gmail.com> (raw)
In-Reply-To: <1484296978-18572-4-git-send-email-erin.lo@mediatek.com>



On 13/01/17 09:42, Erin Lo wrote:
> From: Xiaolei Li <xiaolei.li@mediatek.com>
>
> Add mt2701 nand device node, include nfi and bch ecc.
>
> Signed-off-by: Xiaolei Li <xiaolei.li@mediatek.com>
> Signed-off-by: Erin Lo <erin.lo@mediatek.com>
> ---
>  arch/arm/boot/dts/mt2701.dtsi | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
>

Applied to v4.10-next/dts32

> diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
> index 87be52c..1182c43 100644
> --- a/arch/arm/boot/dts/mt2701.dtsi
> +++ b/arch/arm/boot/dts/mt2701.dtsi
> @@ -261,6 +261,28 @@
>  		status = "disabled";
>  	};
>
> +	nandc: nfi@1100d000 {
> +		compatible = "mediatek,mt2701-nfc";
> +		reg = <0 0x1100d000 0 0x1000>;
> +		interrupts = <GIC_SPI 56 IRQ_TYPE_LEVEL_LOW>;
> +		clocks = <&pericfg CLK_PERI_NFI>,
> +			 <&pericfg CLK_PERI_NFI_PAD>;
> +		clock-names = "nfi_clk", "pad_clk";
> +		status = "disabled";
> +		ecc-engine = <&bch>;
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +	};
> +
> +	bch: ecc@1100e000 {
> +		compatible = "mediatek,mt2701-ecc";
> +		reg = <0 0x1100e000 0 0x1000>;
> +		interrupts = <GIC_SPI 55 IRQ_TYPE_LEVEL_LOW>;
> +		clocks = <&pericfg CLK_PERI_NFI_ECC>;
> +		clock-names = "nfiecc_clk";
> +		status = "disabled";
> +	};
> +
>  	spi1: spi@11016000 {
>  		compatible = "mediatek,mt2701-spi";
>  		#address-cells = <1>;
>

  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
2017-01-13  8:42 ` [PATCH v2 1/6] arm: dts: mt2701: Add spi device node Erin Lo
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 3/6] arm: dts: mt2701: Add nand " Erin Lo
2017-01-13 15:29   ` Matthias Brugger [this message]
2017-01-13  8:42 ` [PATCH v2 4/6] arm: dts: mt2701: Add auxadc " Erin Lo
2017-01-13 15:29   ` Matthias Brugger
2017-01-13  8:42 ` [PATCH v2 5/6] arm: dts: mt2701: Add ethernet " Erin Lo
2017-01-14 10:32   ` John Crispin
2017-01-14 16:10     ` Sean Wang
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=eedd5138-049e-419e-edb4-51be7f75be97@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=xiaolei.li@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;
as well as URLs for NNTP newsgroup(s).