devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuldeep Singh <kuldeep.singh@nxp.com>
To: Michael Walle <michael@walle.cc>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Shawn Guo <shawnguo@kernel.org>, Leo Li <leoyang.li@nxp.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: RE: [EXT] [PATCH 3/4] arm64: dts: ls1028a: add FlexSPI node
Date: Mon, 2 Dec 2019 05:43:20 +0000	[thread overview]
Message-ID: <AM0PR0402MB35568D79CBFDC28B32561085E0430@AM0PR0402MB3556.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <afde04b888418e9e4f4fdb946a579e70@walle.cc>

Hi,

> -----Original Message-----
> From: Michael Walle <michael@walle.cc>
> Sent: Tuesday, November 26, 2019 3:38 PM
> To: Kuldeep Singh <kuldeep.singh@nxp.com>
> Cc: linux-arm-kernel@lists.infradead.org; devicetree@vger.kernel.org;
> linux-kernel@vger.kernel.org; Shawn Guo <shawnguo@kernel.org>; Leo Li
> <leoyang.li@nxp.com>; Rob Herring <robh+dt@kernel.org>; Mark Rutland
> <mark.rutland@arm.com>
> Subject: Re: [EXT] [PATCH 3/4] arm64: dts: ls1028a: add FlexSPI node
> 
> Caution: EXT Email
> 
> Hi Kuldeep,
> 
> Am 2019-11-26 07:40, schrieb Kuldeep Singh:
> > Hi Michael,
> >
> >> -----Original Message-----
> >> From: devicetree-owner@vger.kernel.org
> >> <devicetree-owner@vger.kernel.org>
> >> On Behalf Of Michael Walle
> >> Sent: Sunday, November 24, 2019 1:43 AM
> >> To: linux-arm-kernel@lists.infradead.org; devicetree@vger.kernel.org;
> >> linux-
> >> kernel@vger.kernel.org
> >> Cc: Shawn Guo <shawnguo@kernel.org>; Leo Li <leoyang.li@nxp.com>;
> Rob
> >> Herring <robh+dt@kernel.org>; Mark Rutland <mark.rutland@arm.com>;
> >> Michael Walle <michael@walle.cc>
> >> Subject: [EXT] [PATCH 3/4] arm64: dts: ls1028a: add FlexSPI node
> >
> > There's already a patch[1] sent upstream and is under review.
> > It includes dts(i) entries for LS1028. I will be sending the next
> > version
> 
> I've seen that, but there wasn't any reply for almost two months now.
> But
> if you're sending your next version, this patch can be dropped from this
> series.

Okay.

--Kuldeep
> 
> -michael
> 
> >
> > [1]
> >
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc
> >
> hwork.kernel.org%2Fpatch%2F11139365%2F&amp;data=02%7C01%7Ckuld
> eep.sing
> >
> h%40nxp.com%7C327363e5ba97483c9add08d77258875d%7C686ea1d3bc2
> b4c6fa92cd
> >
> 99c5c301635%7C0%7C0%7C637103596868168346&amp;sdata=yDJ1ggrIuR
> v1%2Br%2F
> > 9Ez1uvv0EpFB8Mns5%2Ffn%2F7zG5InA%3D&amp;reserved=0
> >>
> >> Caution: EXT Email
> >>
> >> Signed-off-by: Michael Walle <michael@walle.cc>
> >> ---
> >>  arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 13 +++++++++++++
> >>  1 file changed, 13 insertions(+)
> >>
> >> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
> >> b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
> >> index 6730922c2d47..650b277ddd66 100644
> >> --- a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
> >> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
> >> @@ -260,6 +260,19 @@
> >>                         status = "disabled";
> >>                 };
> >>
> >> +               fspi: spi@20c0000 {
> >> +                       compatible = "nxp,lx2160a-fspi";
> >> +                       #address-cells = <1>;
> >> +                       #size-cells = <0>;
> >> +                       reg = <0x0 0x20c0000 0x0 0x10000>,
> >> +                             <0x0 0x20000000 0x0 0x10000000>;
> >> +                       reg-names = "fspi_base", "fspi_mmap";
> >> +                       interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
> >> +                       clocks = <&clockgen 4 3>, <&clockgen 4 3>;
> >> +                       clock-names = "fspi_en", "fspi";
> >> +                       status = "disabled";
> >> +               };
> >> +
> >>                 esdhc: mmc@2140000 {
> >>                         compatible = "fsl,ls1028a-esdhc", "fsl,esdhc";
> >>                         reg = <0x0 0x2140000 0x0 0x10000>;
> >> --
> >> 2.20.1
> >
> > Regards
> > Kuldeep

  reply	other threads:[~2019-12-02  5:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 20:13 [PATCH 0/4] ls1028a: dts fixes and new board support Michael Walle
2019-11-23 20:13 ` [PATCH 1/4] arm64: dts: ls1028a: fix typo in TMU calibration data Michael Walle
2019-12-09  6:24   ` Shawn Guo
2019-12-09  6:39     ` [EXT] " Andy Tang
2019-12-09  8:41     ` Michael Walle
2019-11-23 20:13 ` [PATCH 2/4] arm64: dts: ls1028a: add missing sai nodes Michael Walle
2019-12-09  6:31   ` Shawn Guo
2019-11-23 20:13 ` [PATCH 3/4] arm64: dts: ls1028a: add FlexSPI node Michael Walle
2019-11-26  6:40   ` [EXT] " Kuldeep Singh
2019-11-26 10:08     ` Michael Walle
2019-12-02  5:43       ` Kuldeep Singh [this message]
2019-11-23 20:13 ` [PATCH 4/4] arm64: dts: freescale: add Kontron sl28 support Michael Walle
2019-12-09  6:43   ` Shawn Guo
2019-12-09  8:54     ` Michael Walle

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=AM0PR0402MB35568D79CBFDC28B32561085E0430@AM0PR0402MB3556.eurprd04.prod.outlook.com \
    --to=kuldeep.singh@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michael@walle.cc \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --subject='RE: [EXT] [PATCH 3/4] arm64: dts: ls1028a: add FlexSPI node' \
    /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

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).