linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Qiang Zhao <qiang.zhao@nxp.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	leoyang.li@nxp.com, Chuanhua Han <chuanhua.han@nxp.com>
Subject: Re: [RESEND PATCH 1/2] arm64: dts: lx2160a: add dspi controller DT nodes
Date: Sat, 11 Jul 2020 22:23:23 +0800	[thread overview]
Message-ID: <20200711142322.GI21277@dragon> (raw)
In-Reply-To: <20200622083109.3441-1-qiang.zhao@nxp.com>

On Mon, Jun 22, 2020 at 04:31:08PM +0800, Qiang Zhao wrote:
> From: Chuanhua Han <chuanhua.han@nxp.com>
> 
> Add the dspi support on lx2160
> 
> Signed-off-by: Chuanhua Han <chuanhua.han@nxp.com>
> Signed-off-by: Bao Xiaowei <xiaowei.bao@nxp.com>
> Signed-off-by: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
> Signed-off-by: Zhao Qiang <qiang.zhao@nxp.com>

When you resend patches, please state why.  Should I drop the patches
I just applied and pick up this version instead?

Shawn

> ---
>  arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 39 ++++++++++++++++++++++++++
>  1 file changed, 39 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi b/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
> index abaeb58..f56172f 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
> +++ b/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
> @@ -777,6 +777,45 @@
>  			status = "disabled";
>  		};
>  
> +		dspi0: spi@2100000 {
> +			compatible = "fsl,lx2160a-dspi", "fsl,ls2085a-dspi";
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +			reg = <0x0 0x2100000 0x0 0x10000>;
> +			interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clockgen 4 7>;
> +			clock-names = "dspi";
> +			spi-num-chipselects = <5>;
> +			bus-num = <0>;
> +			status = "disabled";
> +		};
> +
> +		dspi1: spi@2110000 {
> +			compatible = "fsl,lx2160a-dspi", "fsl,ls2085a-dspi";
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +			reg = <0x0 0x2110000 0x0 0x10000>;
> +			interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clockgen 4 7>;
> +			clock-names = "dspi";
> +			spi-num-chipselects = <5>;
> +			bus-num = <1>;
> +			status = "disabled";
> +		};
> +
> +		dspi2: spi@2120000 {
> +			compatible = "fsl,lx2160a-dspi", "fsl,ls2085a-dspi";
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +			reg = <0x0 0x2120000 0x0 0x10000>;
> +			interrupts = <GIC_SPI 241 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clockgen 4 7>;
> +			clock-names = "dspi";
> +			spi-num-chipselects = <5>;
> +			bus-num = <2>;
> +			status = "disabled";
> +		};
> +
>  		esdhc0: esdhc@2140000 {
>  			compatible = "fsl,esdhc";
>  			reg = <0x0 0x2140000 0x0 0x10000>;
> -- 
> 2.7.4
> 

  parent reply	other threads:[~2020-07-11 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  8:31 [RESEND PATCH 1/2] arm64: dts: lx2160a: add dspi controller DT nodes Qiang Zhao
2020-06-22  8:31 ` [RESEND PATCH 2/2] arm64: dts: lx2160a: add DT node for all DSPI controller Qiang Zhao
2020-07-11 14:23 ` Shawn Guo [this message]
2020-07-13  2:43   ` [RESEND PATCH 1/2] arm64: dts: lx2160a: add dspi controller DT nodes Qiang Zhao

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=20200711142322.GI21277@dragon \
    --to=shawnguo@kernel.org \
    --cc=chuanhua.han@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiang.zhao@nxp.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).