From: "Thierry Reding" <thierry.reding@gmail.com>
To: "Mikko Perttunen" <cyndis@kapsi.fi>
Cc: "Mikko Perttunen" <mperttunen@nvidia.com>,
<dri-devel@lists.freedesktop.org>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] gpu: host1x: Skip reset assert on Tegra186
Date: Mon, 19 Feb 2024 17:31:16 +0100 [thread overview]
Message-ID: <CZ976COWNF9P.9CWFVDV5ZKAY@gmail.com> (raw)
In-Reply-To: <cea93e4c-f6f0-4017-89b5-30e3d7b482dc@kapsi.fi>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On Mon Feb 19, 2024 at 3:18 AM CET, Mikko Perttunen wrote:
> On 2/16/24 19:02, Thierry Reding wrote:
> > On Wed Feb 14, 2024 at 12:40 PM CET, Mikko Perttunen wrote:
> >> From: Mikko Perttunen <mperttunen@nvidia.com>
> >>
> >> On Tegra186, other software components may rely on the kernel to
> >> keep Host1x operational even during suspend. As such, as a quirk,
> >> skip asserting Host1x's reset on Tegra186.
> >
> > This all sounds a bit vague. What other software components rely on the
> > kernel to keep host1x operational during suspend? And why do they do so?
> > Why is this not a problem elsewhere?
>
> My assumption is that it's due to a secure world application accessing
> NVDEC or display engines during suspend or resume. This happening
> without kernel knowledge is a bad thing, but it's hard to change at this
> point.
>
> The reset line (CAR vs BPMP vs non-accessible reset line), and the
> secure application code programming this stuff is slightly different in
> every chip generation, which is where I think the differences happen.
*sigh*
I guess it is what it is. Please add a bit more background information
to the commit message and also a comment for the skip_reset field so
that people (including myself) will remember down the road why this
exists.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-19 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 11:40 [PATCH] gpu: host1x: Skip reset assert on Tegra186 Mikko Perttunen
2024-02-15 11:07 ` Jon Hunter
2024-02-16 10:02 ` Thierry Reding
2024-02-19 2:18 ` Mikko Perttunen
2024-02-19 16:31 ` Thierry Reding [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-22 1:05 Mikko Perttunen
2024-02-22 18:06 ` Thierry Reding
2024-02-24 6:02 ` Mikko Perttunen
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=CZ976COWNF9P.9CWFVDV5ZKAY@gmail.com \
--to=thierry.reding@gmail.com \
--cc=cyndis@kapsi.fi \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.