From: Mario Limonciello <mario.limonciello@amd.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, Iain Lane <iain@orangesquash.org.uk>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: Re: [PATCH v8 2/2] PCI/ACPI: Use device constraints instead of dates to opt devices into D3
Date: Fri, 4 Aug 2023 07:59:39 -0500 [thread overview]
Message-ID: <b1db4846-9da1-9af4-4b3f-53ebf2e527a2@amd.com> (raw)
In-Reply-To: <ZMyWt4JD1TjoLk8w@smile.fi.intel.com>
On 8/4/23 01:12, Andy Shevchenko wrote:
> On Fri, Aug 04, 2023 at 09:07:43AM +0300, Mika Westerberg wrote:
>> On Thu, Aug 03, 2023 at 10:18:07AM -0500, Mario Limonciello wrote:
>
> ...
>
>> Some of them, at least the Apollo Lake ones were used in IVI systems
>> that did not run Windows IIRC.
>
> And if it matters, they even don't have EFI complaint BIOS.
>
Thanks. I agree then; to avoid causing regressions or building a
monster list we should at least try to work in the confines of improving
the situation with an extra optional check that doesn't fail if not present.
Hopefully the approach from my v9 series works for this.
next prev parent reply other threads:[~2023-08-04 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 20:10 [PATCH v8 0/2] Fix wakeup problems on some AMD platforms Mario Limonciello
2023-08-02 20:10 ` [PATCH v8 1/2] ACPI: Add comments to clarify some #ifdef statements Mario Limonciello
2023-08-02 20:10 ` [PATCH v8 2/2] PCI/ACPI: Use device constraints instead of dates to opt devices into D3 Mario Limonciello
2023-08-03 5:01 ` Mika Westerberg
2023-08-03 11:38 ` Mario Limonciello
2023-08-03 15:14 ` Mika Westerberg
2023-08-03 15:18 ` Mario Limonciello
2023-08-04 6:07 ` Mika Westerberg
2023-08-04 6:12 ` Andy Shevchenko
2023-08-04 12:59 ` Mario Limonciello [this message]
2023-08-04 2:32 ` Mario Limonciello
2023-08-03 5:04 ` kernel test robot
2023-08-03 9:40 ` kernel test robot
2023-08-03 11:49 ` Andy Shevchenko
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=b1db4846-9da1-9af4-4b3f-53ebf2e527a2@amd.com \
--to=mario.limonciello@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=iain@orangesquash.org.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=sathyanarayanan.kuppuswamy@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