From: Sascha Hauer <s.hauer@pengutronix.de>
To: "open list:BAREBOX" <barebox@lists.infradead.org>
Subject: [PATCH 0/4] K3: Add Asel support to the DMA driver
Date: Tue, 29 Apr 2025 16:14:19 +0200 [thread overview]
Message-ID: <20250429-k3-asel-v1-0-6f39afaa2dfe@pengutronix.de> (raw)
This adds Asel aka "Address select" handling to the K3 DMA driver.
Asel is a four bit field that has to be put in bits 48-51 of the DMA
addresses. This is needed once the DDR firewalls are enabled.
The DDR firewalls are needed to protect the OP-TEE memory from accesses
from the normal world. One would assume that upstream OP-TEE does this
by default, but apparently it doesn't and once they are enabled ethernet
in barebox stops working. This series fixes networking in barebox with
DDR firewalls enabled.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (4):
ti/k3-navss-ringacc: switch to Linux code base
firmware: ti_sci: pass struct to ti_sci_rm_ringacc_ops::config
firmware: ti_sci: handle Asel
dma: k3-udma: Handle Asel
drivers/dma/ti/k3-udma.c | 125 ++--
drivers/firmware/ti_sci.c | 29 +-
drivers/firmware/ti_sci.h | 5 +
drivers/soc/ti/k3-navss-ringacc.c | 1326 ++++++++++++++++++++++++-------------
include/soc/ti/k3-navss-ringacc.h | 211 +++---
include/soc/ti/ti_sci_protocol.h | 34 +-
6 files changed, 1088 insertions(+), 642 deletions(-)
---
base-commit: fe58b1f7d24ea2171d0761a26f2b5a74e61322e4
change-id: 20250429-k3-asel-c5bf1e14c267
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2025-04-29 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 14:14 Sascha Hauer [this message]
2025-04-29 14:14 ` [PATCH 1/4] ti/k3-navss-ringacc: switch to Linux code base Sascha Hauer
2025-04-29 14:14 ` [PATCH 2/4] firmware: ti_sci: pass struct to ti_sci_rm_ringacc_ops::config Sascha Hauer
2025-04-29 14:14 ` [PATCH 3/4] firmware: ti_sci: handle Asel Sascha Hauer
2025-04-29 14:14 ` [PATCH 4/4] dma: k3-udma: Handle Asel Sascha Hauer
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=20250429-k3-asel-v1-0-6f39afaa2dfe@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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