linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Peng Ma <peng.ma@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Leo Li <leoyang.li@nxp.com>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [EXT] Re: [PATCH 2/4] arm64: dts: fsl: ls1028a: Add eDMA node
Date: Wed, 19 Jun 2019 01:47:03 +0000	[thread overview]
Message-ID: <VI1PR04MB4431D32CF8F6F430B58A56D9EDE50@VI1PR04MB4431.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190618131319.GC1959@dragon>



>-----Original Message-----
>From: Shawn Guo <shawnguo@kernel.org>
>Sent: 2019年6月18日 21:13
>To: Peng Ma <peng.ma@nxp.com>
>Cc: vkoul@kernel.org; robh+dt@kernel.org; mark.rutland@arm.com; Leo Li
><leoyang.li@nxp.com>; dan.j.williams@intel.com; dmaengine@vger.kernel.org;
>devicetree@vger.kernel.org; linux-kernel@vger.kernel.org;
>linux-arm-kernel@lists.infradead.org
>Subject: [EXT] Re: [PATCH 2/4] arm64: dts: fsl: ls1028a: Add eDMA node
>
>Caution: EXT Email
>
>On Mon, May 06, 2019 at 09:03:42AM +0000, Peng Ma wrote:
>> Add the eDMA device tree nodes for LS1028A devices
>>
>> Signed-off-by: Peng Ma <peng.ma@nxp.com>
>> ---
>>  arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi |   15 +++++++++++++++
>>  1 files changed, 15 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> index 8116fb3..71b87cb 100644
>> --- a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> @@ -235,6 +235,21 @@
>>                       status = "disabled";
>>               };
>>
>> +             edma0: edma@22c0000 {
>> +                     #dma-cells = <2>;
>> +                     compatible = "fsl,vf610-edma";
>> +                     reg = <0x0 0x22c0000 0x0 0x10000>,
>> +                           <0x0 0x22d0000 0x0 0x10000>,
>> +                           <0x0 0x22e0000 0x0 0x10000>;
>> +                     interrupts = <GIC_SPI 56
>IRQ_TYPE_LEVEL_HIGH>,
>> +                                  <GIC_SPI 56
>IRQ_TYPE_LEVEL_HIGH>;
>> +                     interrupt-names = "edma-tx", "edma-err";
>> +                     dma-channels = <32>;
>> +                     clock-names = "dmamux0", "dmamux1";
>> +                     clocks = <&clockgen 4 1>,
>> +                              <&clockgen 4 1>;
>> +             };
>> +
>
>The edma@22c0000 node had already been added by commit below:
>
>  f54f7be5c5ac ("arm64: dts: ls1028a: Add Audio DT nodes")
>
[Peng Ma] OK, got it, thanks.

Best Regards,
Peng
>Shawn
>
>>               gpio1: gpio@2300000 {
>>                       compatible = "fsl,qoriq-gpio";
>>                       reg = <0x0 0x2300000 0x0 0x10000>;
>> --
>> 1.7.1
>>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-06-19  1:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06  9:03 [PATCH 1/4] arm64: dts: fsl: ls1028a: Add qDMA node Peng Ma
2019-05-06  9:03 ` [PATCH 2/4] arm64: dts: fsl: ls1028a: Add eDMA node Peng Ma
2019-06-18 13:13   ` Shawn Guo
2019-06-19  1:47     ` Peng Ma [this message]
2019-05-06  9:03 ` [PATCH 3/4] dmaengine: fsl-edma: support little endian for edma driver Peng Ma
2019-05-21  4:38   ` Vinod Koul
2019-05-22  6:33     ` [EXT] " Peng Ma
2019-05-06  9:03 ` [PATCH 4/4] dt-bindings: fsl-qdma: Add LS1028A qDMA bindings Peng Ma
2019-06-13 18:07   ` Rob Herring
2019-06-18 13:08   ` Shawn Guo
2019-06-18 13:06 ` [PATCH 1/4] arm64: dts: fsl: ls1028a: Add qDMA node Shawn Guo

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=VI1PR04MB4431D32CF8F6F430B58A56D9EDE50@VI1PR04MB4431.eurprd04.prod.outlook.com \
    --to=peng.ma@nxp.com \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@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=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=vkoul@kernel.org \
    /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).