From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>,
Ashish Mhetre <amhetre@nvidia.com>,
thierry.reding@kernel.org
Cc: ketanp@nvidia.com, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V3 3/3] memory: tegra: Restore MC interrupt masks on resume
Date: Fri, 1 May 2026 11:26:29 +0200 [thread overview]
Message-ID: <090b5d44-c984-4653-9e03-f828467dca94@kernel.org> (raw)
In-Reply-To: <df25dd7a-1f59-4fd5-bdae-ba3a99e700f1@nvidia.com>
On 30/04/2026 13:42, Jon Hunter wrote:
>
> On 30/04/2026 10:52, Ashish Mhetre wrote:
>> The MC interrupt mask registers lose their state across SC7. Without
>
> SC7 may not mean anything to anyone that is not familiar with Tegra. I
> often refer to this as 'Tegra low power suspend state (aka. SC7)'. Or we
> can just simply say 'suspend' instead of 'SC7'.
>
> Krzysztof, do you want use to clarify this and update the commit message?
I can adjust it while applying.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-01 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 9:51 [PATCH V3 0/3] memory: tegra: Restore MC state on system resume Ashish Mhetre
2026-04-30 9:52 ` [PATCH V3 1/3] memory: tegra: Make ->resume() callback return void Ashish Mhetre
2026-04-30 9:52 ` [PATCH V3 2/3] memory: tegra: Wire up system sleep PM ops Ashish Mhetre
2026-04-30 9:52 ` [PATCH V3 3/3] memory: tegra: Restore MC interrupt masks on resume Ashish Mhetre
2026-04-30 11:42 ` Jon Hunter
2026-05-01 9:26 ` Krzysztof Kozlowski [this message]
2026-05-01 10:29 ` [PATCH V3 0/3] memory: tegra: Restore MC state on system resume Jon Hunter
2026-05-04 17:48 ` Krzysztof Kozlowski
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=090b5d44-c984-4653-9e03-f828467dca94@kernel.org \
--to=krzk@kernel.org \
--cc=amhetre@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=ketanp@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@kernel.org \
/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