From: Vignesh Raghavendra <vigneshr@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 00/10] dma: ti: k3-udma: Add support for J721e
Date: Mon, 9 Dec 2019 10:25:30 +0530 [thread overview]
Message-ID: <20191209045540.10702-1-vigneshr@ti.com> (raw)
This series adds DMA support for J721e using exist K3 UDMA driver.
One main change is thati, on J721e, DMA resources such as DMA channels are
shared between different entities running on different cores of the SoC.
Therefore, U-Boot running on A72 core should request range of resources
allocated to it from centralized resource management core (DMSC) and use
only the allocated resource.
First two patches adds support for dynamically querying and using
allocated resources. Remaining patches fix issues when using UDMA driver
on a 32 bit core like R5. Last patch adds a new compatible for J721e
v4:
Rebase onto latest master and fix a compliation error due to recent
changes in master.
v3:
Address comments by Grygorii and add R-by
Vignesh Raghavendra (10):
lib: Import few bitmap functions from Linux
dma: ti: k3-udma: Query DMA channels allocated from Resource Manager
soc: ti: k3-navss-ringacc: Flush/invalidate caches on ring push/pop
soc: ti: k3-navss-ringacc: Get SYSFW reference from DT phandle
dma: ti: k3-udma: Remove coherency check for cache ops
dma: ti: k3-udma: Fix debug prints during enabling MEM_TO_DEV
transfers
dma: ti: k3-udma: Switch to exposed ring mode
dma: ti: k3-udma: Fix ring push operation for 32 bit cores
dma: ti: k3-udma: Fix build warnings when building for 32 bit
platforms
dma: ti: k3-udma: Add new compatible to J721e
drivers/dma/ti/k3-udma.c | 365 ++++++++++++++++++++----------
drivers/soc/ti/k3-navss-ringacc.c | 14 +-
include/linux/bitmap.h | 133 +++++++++++
include/linux/bitops.h | 12 +
4 files changed, 404 insertions(+), 120 deletions(-)
--
2.24.0
next reply other threads:[~2019-12-09 4:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 4:55 Vignesh Raghavendra [this message]
2019-12-09 4:55 ` [PATCH v4 01/10] lib: Import few bitmap functions from Linux Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 02/10] dma: ti: k3-udma: Query DMA channels allocated from Resource Manager Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 03/10] soc: ti: k3-navss-ringacc: Flush/invalidate caches on ring push/pop Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 04/10] soc: ti: k3-navss-ringacc: Get SYSFW reference from DT phandle Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 05/10] dma: ti: k3-udma: Remove coherency check for cache ops Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 06/10] dma: ti: k3-udma: Fix debug prints during enabling MEM_TO_DEV transfers Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 07/10] dma: ti: k3-udma: Switch to exposed ring mode Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 08/10] dma: ti: k3-udma: Fix ring push operation for 32 bit cores Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 09/10] dma: ti: k3-udma: Fix build warnings when building for 32 bit platforms Vignesh Raghavendra
2019-12-09 4:55 ` [PATCH v4 10/10] dma: ti: k3-udma: Add new compatible to J721e Vignesh Raghavendra
2020-01-20 5:58 ` [PATCH v4 00/10] dma: ti: k3-udma: Add support for J721e Lokesh Vutla
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=20191209045540.10702-1-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=u-boot@lists.denx.de \
/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