From: Greg KH <gregkh@linuxfoundation.org>
To: "Limonciello, Mario" <mario.limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Pananchikkal, Renjith" <Renjith.Pananchikkal@amd.com>,
"Gong, Richard" <Richard.Gong@amd.com>
Subject: Re: Mark dGPUs as devices
Date: Sun, 16 Jul 2023 11:26:43 +0200 [thread overview]
Message-ID: <2023071635-profusely-latch-8f20@gregkh> (raw)
In-Reply-To: <050d87f7-5a77-571d-f5c9-f66f39ba2f2e@amd.com>
On Wed, Jul 12, 2023 at 04:51:24PM -0500, Limonciello, Mario wrote:
> Hi,
>
> A problem exists where dGPUs with type-C ports are considered power supplies
> that power the system.
> This leads to poor performance of the dGPU because graphics drivers like
> amdgpu use power_supply_is_system_supplied() to decide how to configure the
> dGPU.
> This has been fixed in 6.5-rc1 by marking dGPUs as "DEVICE".
>
> The logic to fix what to do when DEVICE is encountered was fixed in 6.4-rc4
> and already backported to stable:
> 95339f40a8b6 ("power: supply: Fix logic checking if system is running from
> battery")
>
> So to wrap up the fix in stable kernels can you please backport:
>
> 6.4.y:
> a7fbfd44c020 ("usb: typec: ucsi: Mark dGPUs as DEVICE scope")
>
> 6.1.y:
> f510b0a3565b ("i2c: nvidia-gpu: Add ACPI property to align with
> device-tree")
> 430b38764fbb ("i2c: nvidia-gpu: Remove ccgx,firmware-build property")
> a7fbfd44c020 ("usb: typec: ucsi: Mark dGPUs as DEVICE scope")
All now qeueud up, thanks.
greg k-h
prev parent reply other threads:[~2023-07-16 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 21:51 Mark dGPUs as devices Limonciello, Mario
2023-07-16 9:26 ` Greg KH [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=2023071635-profusely-latch-8f20@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Renjith.Pananchikkal@amd.com \
--cc=Richard.Gong@amd.com \
--cc=mario.limonciello@amd.com \
--cc=stable@vger.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