From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hansg@kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] platform/x86: ISST: Fix for write lock and suspend/resume
Date: Mon, 12 Jan 2026 17:33:57 +0200 [thread overview]
Message-ID: <176823203763.9723.5243670404691527685.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260107060256.1634188-1-srinivas.pandruvada@linux.intel.com>
On Tue, 06 Jan 2026 22:02:54 -0800, Srinivas Pandruvada wrote:
> There are two issues, which are not urgent as the current deployed systems
> don't support them, but need fixes:
> - Write lock- Even if the TPMI is write locked it will still write to MMIO
> - store-restore data during suspend/resume: Not storing and restoring data to
> all power domains.
>
> v2:
> One minor fix for new line
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/2] platform/x86: ISST: Add missing write block check
commit: 51bec3adb6006e070fefd43a3fabcd4446b910f2
[2/2] platform/x86: ISST: Store and restore all domains data
commit: c2cacb320ade6beca0e02d399a4385181409ebdd
--
i.
prev parent reply other threads:[~2026-01-12 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 6:02 Srinivas Pandruvada
2026-01-07 6:02 ` [PATCH v2 1/2] platform/x86: ISST: Add missing write block check Srinivas Pandruvada
2026-01-07 6:02 ` [PATCH v2 2/2] platform/x86: ISST: Store and restore all domains data Srinivas Pandruvada
2026-01-12 15:33 ` Ilpo Järvinen [this message]
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=176823203763.9723.5243670404691527685.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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®