public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Gregor Riepl <onitake@gmail.com>
Cc: linux-i2c@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Evan.Quan@amd.com, Lijo.Lazar@amd.com, Sanket.Goswami@amd.com,
	heikki.krogerus@linux.intel.com, ajayg@nvidia.com,
	andriy.shevchenko@linux.intel.com
Subject: Re: [PATCH v2] usb: typec: ucsi: Mark dGPUs as DEVICE scope
Date: Sun, 21 May 2023 07:59:45 -0500	[thread overview]
Message-ID: <85845b5e-4c9d-4a2d-9d81-c49c82380177@amd.com> (raw)
In-Reply-To: <6f1e866b-a96a-3134-c735-c941681b0638@gmail.com>

On 5/21/23 04:23, Gregor Riepl wrote:
>> As the power supply for a dGPU is only for powering devices connected
>> to dGPU, create a device property to indicate that the UCSI endpoint
>> is only for the scope of `POWER_SUPPLY_SCOPE_DEVICE`.
> 
> Is this a given fact?

At least for today's eGPU enclosures; yes.

> 
> I could imagine that a dGPU device would be capable of feeding power 
> back into the system, for example when an external docking station or 
> display device has a power supply connected to it.
> 
> Although I don't think it's possible (or safe) with a desktop system, 
> maybe a portable computer with a discrete GPU would be able to do this?

If such a hardware design was created you should actually have two USCI 
power supplies.

The PD controller or TCPC for the portable computer should provide one 
to represent the connection to the eGPU and the dGPU should provide one
to represent the connection to the dGPU.

The one from the portable computer will be marked 'system' and the dGPU 
would be 'device.'

  reply	other threads:[~2023-05-21 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 16:11 [PATCH v2] usb: typec: ucsi: Mark dGPUs as DEVICE scope Mario Limonciello
2023-05-19  8:12 ` Heikki Krogerus
2023-05-20 17:24 ` Sebastian Reichel
2023-05-21  9:23 ` Gregor Riepl
2023-05-21 12:59   ` Mario Limonciello [this message]
2023-06-14  0:16 ` Andi Shyti
2023-06-14  8:47   ` Wolfram Sang

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=85845b5e-4c9d-4a2d-9d81-c49c82380177@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Evan.Quan@amd.com \
    --cc=Lijo.Lazar@amd.com \
    --cc=Sanket.Goswami@amd.com \
    --cc=ajayg@nvidia.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=onitake@gmail.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