From: Vinod Koul <vkoul@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Rob Herring <robh+dt@kernel.org>,
list@opendingux.net, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 0/6] dmaengine: jz4780: Driver updates v2
Date: Mon, 13 Dec 2021 11:52:32 +0530 [thread overview]
Message-ID: <YbbmqI6MHSwZTfIc@matsya> (raw)
In-Reply-To: <20211206174259.68133-1-paul@crapouillou.net>
On 06-12-21, 17:42, Paul Cercueil wrote:
> Hi Vinod,
>
> A small set of updates to the dma-jz4780 driver.
>
> It adds support for the MDMA/BDMA engines in the JZ4760(B) and JZ4770
> SoCs, which are just regular cores with less channels.
>
> It also adds support for bidirectional channels, so that devices that
> only do half-duplex transfers can request a single DMA channel for both
> directions.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2021-12-13 6:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 17:42 [PATCH v2 0/6] dmaengine: jz4780: Driver updates v2 Paul Cercueil
2021-12-06 17:42 ` [PATCH v2 1/6] dt-bindings: dma: ingenic: Add compatible strings for MDMA and BDMA Paul Cercueil
2021-12-06 17:42 ` [PATCH v2 2/6] dt-bindings: dma: ingenic: Support #dma-cells = <3> Paul Cercueil
2021-12-06 17:42 ` [PATCH v2 3/6] dmaengine: jz4780: Work around hardware bug on JZ4760 SoCs Paul Cercueil
2021-12-06 17:42 ` [PATCH v2 4/6] dmaengine: jz4780: Add support for the MDMA and BDMA in the JZ4760(B) Paul Cercueil
2021-12-06 17:42 ` [PATCH v2 5/6] dmaengine: jz4780: Replace uint32_t with u32 Paul Cercueil
2021-12-06 17:42 ` [PATCH v2 6/6] dmaengine: jz4780: Support bidirectional I/O on one channel Paul Cercueil
2021-12-13 6:22 ` Vinod Koul [this message]
2021-12-13 14:43 ` [PATCH v2 0/6] dmaengine: jz4780: Driver updates v2 Paul Cercueil
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=YbbmqI6MHSwZTfIc@matsya \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=list@opendingux.net \
--cc=paul@crapouillou.net \
--cc=robh+dt@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).