From: Akhil R <akhilrajeev@nvidia.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<linux-tegra@vger.kernel.org>
Cc: Akhil R <akhilrajeev@nvidia.com>
Subject: [PATCH 2/5] gpu: host1x: Add Tegra SE to SID table
Date: Wed, 13 Dec 2023 17:50:27 +0530 [thread overview]
Message-ID: <20231213122030.11734-3-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <20231213122030.11734-1-akhilrajeev@nvidia.com>
Add Tegra Security Engine details to the SID table in host1x driver.
These will be referred when registering the SE as host1x device.
Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
---
drivers/gpu/host1x/dev.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/drivers/gpu/host1x/dev.c b/drivers/gpu/host1x/dev.c
index 42fd504abbcd..b564c7042235 100644
--- a/drivers/gpu/host1x/dev.c
+++ b/drivers/gpu/host1x/dev.c
@@ -214,6 +214,30 @@ static const struct host1x_info host1x07_info = {
* and firmware stream ID in the MMIO path table.
*/
static const struct host1x_sid_entry tegra234_sid_table[] = {
+ {
+ /* SE2 MMIO */
+ .base = 0x1658,
+ .offset = 0x90,
+ .limit = 0x90
+ },
+ {
+ /* SE4 MMIO */
+ .base = 0x1660,
+ .offset = 0x90,
+ .limit = 0x90
+ },
+ {
+ /* SE2 channel */
+ .base = 0x1738,
+ .offset = 0x90,
+ .limit = 0x90
+ },
+ {
+ /* SE4 channel */
+ .base = 0x1740,
+ .offset = 0x90,
+ .limit = 0x90
+ },
{
/* VIC channel */
.base = 0x17b8,
--
2.17.1
next prev parent reply other threads:[~2023-12-13 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 12:20 [PATCH 0/5] Add Tegra Security Engine driver Akhil R
2023-12-13 12:20 ` [PATCH 1/5] dt-bindings: crypto: Add Tegra SE DT binding doc Akhil R
2023-12-13 19:45 ` Krzysztof Kozlowski
2023-12-13 12:20 ` Akhil R [this message]
2023-12-13 12:20 ` [PATCH 3/5] crypto: tegra: Add Tegra Security Engine driver Akhil R
2023-12-13 19:53 ` Krzysztof Kozlowski
2023-12-19 12:59 ` Akhil R
2023-12-14 2:50 ` kernel test robot
2023-12-14 5:19 ` kernel test robot
2023-12-14 7:12 ` kernel test robot
2023-12-14 18:08 ` kernel test robot
2023-12-13 12:20 ` [PATCH 4/5] arm64: defconfig: Enable Tegra Security Engine Akhil R
2023-12-13 12:20 ` [PATCH 5/5] arm64: tegra: Add Tegra Security Engine DT nodes Akhil R
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=20231213122030.11734-3-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jonathanh@nvidia.com \
--cc=linux-crypto@vger.kernel.org \
--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
all inboxes | Powered by JetHome®