From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jon Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 2/2] memory: tegra: Add DLA clients for Tegra234
Date: Fri, 28 Oct 2022 08:46:03 -0400 [thread overview]
Message-ID: <ce3fdd20-248f-4fdd-fe83-2aa79fd297c5@linaro.org> (raw)
In-Reply-To: <20221028123741.134880-2-jonathanh@nvidia.com>
On 28/10/2022 08:37, Jon Hunter wrote:
> Add the memory clients on Tegra234 which are needed for initialising the
> SMMU for the Deep Learning Accelerator (DLA).
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> drivers/memory/tegra/tegra234.c | 160 ++++++++++++++++++++++++++++++++
> 1 file changed, 160 insertions(+)
>
> diff --git a/drivers/memory/tegra/tegra234.c b/drivers/memory/tegra/tegra234.c
> index a9e8fd99730f..9bdaf8af8c97 100644
> --- a/drivers/memory/tegra/tegra234.c
> +++ b/drivers/memory/tegra/tegra234.c
> @@ -170,6 +170,166 @@ static const struct tegra_mc_client tegra234_mc_clients[] = {
> .security = 0x504,
> },
> },
> + }, {
> + .id = TEGRA234_MEMORY_CLIENT_DLA0RDA,
> + .name = "dla0rda",
> + .sid = TEGRA234_SID_NVDLA0,
This is now not applicable because you sent dependencies separate, mixed
with other subsystems... Split pieces based on subsystems.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-28 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 12:37 [PATCH 1/2] dt-bindings: memory: Fix typos and definitions for Tegra Jon Hunter
2022-10-28 12:37 ` [PATCH 2/2] memory: tegra: Add DLA clients for Tegra234 Jon Hunter
2022-10-28 12:46 ` Krzysztof Kozlowski [this message]
2022-10-28 12:51 ` Jon Hunter
2022-10-28 12:52 ` Krzysztof Kozlowski
2022-10-28 13:05 ` Jon Hunter
2022-10-28 13:07 ` Krzysztof Kozlowski
2022-10-28 14:23 ` Thierry Reding
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=ce3fdd20-248f-4fdd-fe83-2aa79fd297c5@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@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