From: Vignesh Raghavendra <vigneshr@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>, <u-boot@lists.denx.de>
Subject: [PATCH v2 0/7] J72xx: R5 SPL DMA support post HSM Rearch
Date: Mon, 7 Jun 2021 19:47:46 +0530 [thread overview]
Message-ID: <20210607141753.28796-1-vigneshr@ti.com> (raw)
This series add DMA support for R5 SPL on J721e/J7200 SoCs post HSM
Rearch.
Depends on Tero's base HSM rearch support series.
v2:
Use IS_ENABLED() consistentially instead of #ifdef
Reword commit msg for 5/7 as suggested by Lokesh
Rebase on Tero's latest HSM base series.
Vignesh Raghavendra (7):
mailbox: k3-sec-proxy: Add DM to DMSC communication thread
firmware: ti_sci: Implement GET_RANGE with static data
firmware: ti_sci: Add support for Resoure Management at R5 SPL stage.
ARM: dts: j72xx-r5-common-proc-board: Add DM firmware node
ARM: dts: k3: Add cfg register space for ringacc and udmap
soc: ti: k3-navss-ringacc: Add support for native configuration of
rings
dma: ti: k3-udma: Add support for native configuration of chan/flow
arch/arm/dts/k3-am654-base-board-u-boot.dtsi | 14 ++
.../k3-j7200-common-proc-board-u-boot.dtsi | 26 +++
.../arm/dts/k3-j7200-r5-common-proc-board.dts | 17 ++
.../k3-j721e-common-proc-board-u-boot.dtsi | 14 ++
.../arm/dts/k3-j721e-r5-common-proc-board.dts | 18 ++
.../firmware/ti,j721e-dm-sci.txt | 32 ++++
drivers/dma/ti/k3-udma-u-boot.c | 177 ++++++++++++++++++
drivers/dma/ti/k3-udma.c | 42 ++++-
drivers/firmware/ti_sci.c | 107 +++++++++++
drivers/firmware/ti_sci_static_data.h | 92 +++++++++
drivers/mailbox/k3-sec-proxy.c | 2 +-
drivers/soc/ti/k3-navss-ringacc-u-boot.c | 61 ++++++
drivers/soc/ti/k3-navss-ringacc.c | 36 +++-
13 files changed, 630 insertions(+), 8 deletions(-)
create mode 100644 doc/device-tree-bindings/firmware/ti,j721e-dm-sci.txt
create mode 100644 drivers/dma/ti/k3-udma-u-boot.c
create mode 100644 drivers/firmware/ti_sci_static_data.h
create mode 100644 drivers/soc/ti/k3-navss-ringacc-u-boot.c
--
2.31.1
next reply other threads:[~2021-06-07 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 14:17 Vignesh Raghavendra [this message]
2021-06-07 14:17 ` [PATCH v2 1/7] mailbox: k3-sec-proxy: Add DM to DMSC communication thread Vignesh Raghavendra
2021-06-07 14:17 ` [PATCH v2 2/7] firmware: ti_sci: Implement GET_RANGE with static data Vignesh Raghavendra
2021-06-07 14:17 ` [PATCH v2 3/7] firmware: ti_sci: Add support for Resoure Management at R5 SPL stage Vignesh Raghavendra
2021-06-07 14:17 ` [PATCH v2 4/7] ARM: dts: j72xx-r5-common-proc-board: Add DM firmware node Vignesh Raghavendra
2021-06-07 14:17 ` [PATCH v2 5/7] ARM: dts: k3: Add cfg register space for ringacc and udmap Vignesh Raghavendra
2021-06-07 14:17 ` [PATCH v2 6/7] soc: ti: k3-navss-ringacc: Add support for native configuration of rings Vignesh Raghavendra
2021-06-07 14:17 ` [PATCH v2 7/7] dma: ti: k3-udma: Add support for native configuration of chan/flow Vignesh Raghavendra
2021-06-08 7:05 ` [PATCH v2 0/7] J72xx: R5 SPL DMA support post HSM Rearch Lokesh Vutla
2021-06-08 7:27 ` Vignesh Raghavendra
2021-06-09 16:55 ` 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=20210607141753.28796-1-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=lokeshvutla@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).