From: "Brandt, Todd E" <todd.e.brandt@intel.com>
To: "ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>
Cc: "xi.pardee@linux.intel.com" <xi.pardee@linux.intel.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] platform/x86/intel/pmc Fix Arrow Lake U/H support to intel_pmc_core driver
Date: Tue, 20 May 2025 11:04:33 +0000 [thread overview]
Message-ID: <ef7c13efe46aff5d23e2b4196b6dee608eb2603c.camel@intel.com> (raw)
In-Reply-To: <360ee90b-c83a-b4de-f864-88ec90cb0648@linux.intel.com>
On Tue, 2025-05-20 at 13:54 +0300, Ilpo Järvinen wrote:
> On Tue, 20 May 2025, Todd Brandt wrote:
>
> > The ARL requires that the GMA and NPU devices both be in D3Hot in
> > order
> > for PC10 and S0iX to be achieved in S2idle. The original ARL-H/U
> > addition
> > to the intel_pmc_core driver attempted to do this by switching them
> > to D3
> > in the init and resume calls of the intel_pmc_core driver.
> >
> > The problem is the ARL-H/U have a different NPU device and thus are
> > not
> > being properly set and thus S0iX does not work properly in ARL-H/U.
> > This
> > patch creates a new ARL-H specific device id that is correct and
> > also
> > adds the D3 fixup to the suspend callback. This way if the PCI
> > devies
> > drop from D3 to D0 after resume they can be corrected for the next
> > suspend. Thus there is no dropout in S0iX.
> >
> > [v2 changes]
> >
> > Added Fixes line
> >
> > [v3 changes]
> >
> > Xi asked that I see if adding the arl_h_suspend call actually made
> > any
> > difference in fixing the issue of S0iX not being achieved, as there
> > are
> > 4 other platforms that use this same fix in just the init and
> > resume
> > callbacks. Upon further testing I discovered it didn't matter. So I
> > just
> > simplified the D3 change and left the fixup call to init and
> > resume.
>
> Okay, I've replaced the commit in the review-ilpo-fixes branch with
> this
> v3 patch. Thanks.
>
> In future, put that patch vX history under --- line so I don't have
> to
> manually remove it (our tools cut the text below that triple dash
> line
> automatically).
>
Will do, sorry about that.
prev parent reply other threads:[~2025-05-20 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 10:45 [PATCH v3] platform/x86/intel/pmc Fix Arrow Lake U/H support to intel_pmc_core driver Todd Brandt
2025-05-20 10:54 ` Ilpo Järvinen
2025-05-20 11:04 ` Brandt, Todd E [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=ef7c13efe46aff5d23e2b4196b6dee608eb2603c.camel@intel.com \
--to=todd.e.brandt@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=xi.pardee@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