From: Mario Limonciello <mario.limonciello@amd.com>
To: <heikki.krogerus@linux.intel.com>, <rafael@kernel.org>,
<ajayg@nvidia.com>, <andriy.shevchenko@linux.intel.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>,
"Mario Limonciello" <mario.limonciello@amd.com>
Subject: [PATCH 0/2] Adjust logic for power_supply_is_system_supplied()
Date: Tue, 16 May 2023 13:25:39 -0500 [thread overview]
Message-ID: <20230516182541.5836-1-mario.limonciello@amd.com> (raw)
Some systems don't provide any ACPI power supplies, but drivers use
the function power_supply_is_system_supplied() to make policy decisions.
This logic works fine until a new device is added to the system that
provides a UCSI power supply. This power supply doesn't power the system
but the logic assumes it does.
This series adjusts the logic so that these power supplies are not
considered when making these policy decisions.
Mario Limonciello (2):
power: supply: Use the scope of power supplies to tell if power is
system supplied
usb: typec: ucsi: Don't create power supplies for dGPUs
drivers/i2c/busses/i2c-designware-pcidrv.c | 13 ++++++++++++-
drivers/i2c/busses/i2c-nvidia-gpu.c | 3 +++
drivers/power/supply/power_supply_core.c | 8 ++++++--
drivers/usb/typec/ucsi/psy.c | 14 ++++++++++++++
4 files changed, 35 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2023-05-16 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 18:25 Mario Limonciello [this message]
2023-05-16 18:25 ` [PATCH 1/2] power: supply: Use the scope of power supplies to tell if power is system supplied Mario Limonciello
2023-05-16 20:41 ` Sebastian Reichel
2023-05-16 20:44 ` Limonciello, Mario
2023-05-16 21:54 ` Sebastian Reichel
2023-05-16 18:25 ` [PATCH 2/2] usb: typec: ucsi: Don't create power supplies for dGPUs Mario Limonciello
2023-05-17 17:14 ` Andy Shevchenko
2023-05-17 18:58 ` Greg KH
2023-05-17 19:14 ` Andy Shevchenko
2023-05-18 15:31 ` Limonciello, Mario
2023-05-17 1:22 ` [PATCH 0/2] Adjust logic for power_supply_is_system_supplied() Quan, Evan
2023-05-17 17:15 ` andriy.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=20230516182541.5836-1-mario.limonciello@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=rafael@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