From: Sameer Pujar <spujar@nvidia.com>
To: <krzysztof.kozlowski@canonical.com>, <thierry.reding@gmail.com>
Cc: <jonathanh@nvidia.com>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, Sameer Pujar <spujar@nvidia.com>
Subject: [PATCH] memory: tegra: Add APE memory clients for Tegra234
Date: Fri, 18 Feb 2022 17:46:29 +0530 [thread overview]
Message-ID: <1645186589-25118-1-git-send-email-spujar@nvidia.com> (raw)
Add the memory clients on Tegra234 which are needed for APE
DMA to properly use the SMMU.
Signed-off-by: Sameer Pujar <spujar@nvidia.com>
---
Please note that this patch depends on the DT binding patches of series
https://patchwork.kernel.org/project/alsa-devel/list/?series=609494&state=*.
So please consider this patch once Thierry picks up DT binding patches and
provides ACK on this.
drivers/memory/tegra/tegra234.c | 22 +++++++++++++++++++++-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/drivers/memory/tegra/tegra234.c b/drivers/memory/tegra/tegra234.c
index f7b24ba..1d19cb9 100644
--- a/drivers/memory/tegra/tegra234.c
+++ b/drivers/memory/tegra/tegra234.c
@@ -1,6 +1,6 @@
// SPDX-License-Identifier: GPL-2.0-only
/*
- * Copyright (C) 2021 NVIDIA CORPORATION. All rights reserved.
+ * Copyright (C) 2021-2022, NVIDIA CORPORATION. All rights reserved.
*/
#include <soc/tegra/mc.h>
@@ -170,6 +170,26 @@ static const struct tegra_mc_client tegra234_mc_clients[] = {
.security = 0x4b4,
},
},
+ }, {
+ .id = TEGRA234_MEMORY_CLIENT_APEDMAR,
+ .name = "apedmar",
+ .sid = TEGRA234_SID_APE,
+ .regs = {
+ .sid = {
+ .override = 0x4f8,
+ .security = 0x4fc,
+ },
+ },
+ }, {
+ .id = TEGRA234_MEMORY_CLIENT_APEDMAW,
+ .name = "apedmaw",
+ .sid = TEGRA234_SID_APE,
+ .regs = {
+ .sid = {
+ .override = 0x500,
+ .security = 0x504,
+ },
+ },
},
};
--
2.7.4
next reply other threads:[~2022-02-18 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 12:16 Sameer Pujar [this message]
2022-02-18 13:04 ` [PATCH] memory: tegra: Add APE memory clients for Tegra234 Krzysztof Kozlowski
2022-02-18 13:25 ` Thierry Reding
2022-02-21 15:41 ` kernel test robot
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=1645186589-25118-1-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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