From: Jon Hunter <jonathanh@nvidia.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Mikko Perttunen <cyndis@kapsi.fi>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Mikko Perttunen <mperttunen@nvidia.com>,
Ashish Mhetre <amhetre@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/8] memory: tegra: Add API for retrieving carveout bounds
Date: Fri, 4 Nov 2022 15:46:03 +0000 [thread overview]
Message-ID: <3a783b8d-4970-663f-816a-15aad5a66a48@nvidia.com> (raw)
In-Reply-To: <b9b20abc-d37f-f74a-a416-2e210bf944c4@linaro.org>
On 04/11/2022 15:35, Krzysztof Kozlowski wrote:
> On 04/11/2022 11:33, Jon Hunter wrote:
>> Hi Thierry, Krzysztof,
>>
>> On 24/10/2022 14:15, Thierry Reding wrote:
>>> On Tue, Sep 20, 2022 at 11:11:56AM +0300, Mikko Perttunen wrote:
>>>> From: Mikko Perttunen <mperttunen@nvidia.com>
>>>>
>>>> On Tegra234 NVDEC firmware is loaded from a secure carveout, where it
>>>> has been loaded by a bootloader. When booting NVDEC, we need to tell it
>>>> the address of this firmware, which we can determine by checking the
>>>> starting address of the carveout. As such, add an MC API to query the
>>>> bounds of carveouts, and add related information on Tegra234.
>>>>
>>>> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
>>>> ---
>>>> v2:
>>>> - Add check for 64-bit phys_addr_t. In practice phys_addr_t
>>>> is always 64 bits where this runs, but it avoids warnings in
>>>> compile test.
>>>> ---
>>>> drivers/memory/tegra/mc.c | 25 +++++++++++++++++++++++++
>>>> drivers/memory/tegra/tegra234.c | 5 +++++
>>>> include/soc/tegra/mc.h | 11 +++++++++++
>>>> 3 files changed, 41 insertions(+)
>>>
>>> Krzysztof,
>>>
>>> I've applied this to the same tree as the patch that uses it for now.
>>> Let me know if you want me to put this on a separate stable branch for
>>> you to pull in.
>>
>> Any update on this?
>
> What kind of update do you expect?
Ha! I guess I should be more explicit :-)
Well, I would like to see this change in -next and so I was hoping that
you would respond to the above to indicate how you would like to pull
this in.
Cheers!
Jon
--
nvpublic
next prev parent reply other threads:[~2022-11-04 15:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 8:11 [PATCH v3 0/8] Support for NVDEC on Tegra234 Mikko Perttunen
2022-09-20 8:11 ` [PATCH v3 1/8] memory: tegra: Add API for retrieving carveout bounds Mikko Perttunen
2022-09-21 7:28 ` Krzysztof Kozlowski
2022-09-21 18:37 ` Krzysztof Kozlowski
2022-09-21 18:54 ` Mikko Perttunen
2022-10-24 13:15 ` Thierry Reding
2022-11-04 15:33 ` Jon Hunter
2022-11-04 15:35 ` Krzysztof Kozlowski
2022-11-04 15:46 ` Jon Hunter [this message]
2022-11-04 15:48 ` Krzysztof Kozlowski
2022-11-04 16:01 ` Jon Hunter
2022-09-20 8:11 ` [PATCH v3 2/8] dt-bindings: Add headers for NVDEC on Tegra234 Mikko Perttunen
2022-09-20 8:11 ` [PATCH v3 3/8] dt-bindings: Add bindings for Tegra234 NVDEC Mikko Perttunen
2022-10-03 16:16 ` Rob Herring
2022-09-20 8:11 ` [PATCH v3 4/8] arm64: tegra: Add NVDEC on Tegra234 Mikko Perttunen
2022-09-20 8:12 ` [PATCH v3 5/8] gpu: host1x: Add stream ID register data for " Mikko Perttunen
2022-09-20 8:12 ` [PATCH v3 6/8] drm/tegra: nvdec: Support multiple clocks Mikko Perttunen
2022-09-20 8:12 ` [PATCH v3 7/8] drm/tegra: Add code for booting RISC-V based engines Mikko Perttunen
2022-09-20 8:12 ` [PATCH v3 8/8] drm/tegra: Add Tegra234 support to NVDEC driver Mikko Perttunen
2022-09-21 7:26 ` [PATCH v3 0/8] Support for NVDEC on Tegra234 Krzysztof Kozlowski
2022-09-21 7:50 ` Mikko Perttunen
2022-09-21 7:53 ` Krzysztof Kozlowski
2022-10-24 13:15 ` 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=3a783b8d-4970-663f-816a-15aad5a66a48@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=airlied@linux.ie \
--cc=amhetre@nvidia.com \
--cc=cyndis@kapsi.fi \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=spujar@nvidia.com \
--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®