From: "Reddy, MallikarjunaX" <mallikarjunax.reddy@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
andriy.shevchenko@intel.com, chuanhua.lei@linux.intel.com,
cheol.yong.kim@intel.com, qi-ming.wu@intel.com,
malliamireddy009@gmail.com, rtanwar@maxlinear.com,
lchuanhua@maxlinear.com
Subject: Re: [PATCH v11 0/2] Add Intel LGM SoC DMA support
Date: Wed, 20 Jan 2021 10:37:23 +0800 [thread overview]
Message-ID: <f624ed42-f1e8-6309-2439-09f1e496015d@linux.intel.com> (raw)
In-Reply-To: <20210117055714.GJ2771@vkoul-mobl>
Ok Vinod.
Thanks,
Mallikarjuna reddy A
On 1/17/2021 1:57 PM, Vinod Koul wrote:
> On 15-01-21, 17:56, Amireddy Mallikarjuna reddy wrote:
>> Add DMA controller driver for Lightning Mountain (LGM) family of SoCs.
>>
>> The main function of the DMA controller is the transfer of data from/to any
>> peripheral to/from the memory. A memory to memory copy capability can also
>> be configured. This ldma driver is used for configure the device and channnels
>> for data and control paths.
>>
>> These controllers provide DMA capabilities for a variety of on-chip
>> devices such as SSC, HSNAND and GSWIP (Gigabit Switch IP).
>>
>> -------------
>> Future Plans:
>> -------------
>> LGM SOC also supports Hardware Memory Copy engine.
>> The role of the HW Memory copy engine is to offload memory copy operations
>> from the CPU.
> ??
>
> Please send updates against already applied patches and not an updated
> series!
>
prev parent reply other threads:[~2021-01-20 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 9:56 [PATCH v11 0/2] Add Intel LGM SoC DMA support Amireddy Mallikarjuna reddy
2021-01-15 9:56 ` [PATCH v11 1/2] dt-bindings: dma: Add bindings for Intel LGM SoC Amireddy Mallikarjuna reddy
2021-01-15 9:56 ` [PATCH v11 2/2] Add Intel LGM SoC DMA support Amireddy Mallikarjuna reddy
2021-01-17 5:57 ` [PATCH v11 0/2] " Vinod Koul
2021-01-20 2:37 ` Reddy, MallikarjunaX [this message]
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=f624ed42-f1e8-6309-2439-09f1e496015d@linux.intel.com \
--to=mallikarjunax.reddy@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=lchuanhua@maxlinear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malliamireddy009@gmail.com \
--cc=qi-ming.wu@intel.com \
--cc=robh+dt@kernel.org \
--cc=rtanwar@maxlinear.com \
--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).