lkml.org 
[lkml]   [2021]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC PATCH 2/3] power: supply: Add support for PDOs props
Hi Prashant,

On Thu, Sep 02, 2021 at 02:35:00PM -0700, Prashant Malani wrote:
> Add support for reporting Source and Sink Capabilities
> Power Data Object (PDO) property. These are reported by USB
> Power Delivery (PD) capable power sources.
>
> Signed-off-by: Prashant Malani <pmalani@chromium.org>
> ---
> Documentation/ABI/testing/sysfs-class-power | 30 +++++++++++++++++++++
> drivers/power/supply/power_supply_sysfs.c | 18 ++++++++++++-
> include/linux/power_supply.h | 5 ++++
> 3 files changed, 52 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power
> index ca830c6cd809..90d4198e6dfb 100644
> --- a/Documentation/ABI/testing/sysfs-class-power
> +++ b/Documentation/ABI/testing/sysfs-class-power
> @@ -562,6 +562,36 @@ Description:
> "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
> "PD_DRP", "PD_PPS", "BrickID"
>
> +What: /sys/class/power_supply/<supply_name>/source_cap_pdos
> +Date: September 2021
> +Contact: linux-pm@vger.kernel.org
> +Description:
> + Reports the Source Capabilities Power Data Objects (PDO) reported by the USB
> + PD-capable power source. 13 PDOs are listed. PDOs 1-7 represent the Source Caps
> + for devices which only support Standard Power Range (SPR), whereas PDOs 8-13
> + are for Extended Power Range (EPR) capable sources.
> + NOTE: The EPR Source Caps message is a superset of the Source Cap message, so on
> + SPR-only sources, PDOs 8-13 will be 0.
> +
> + Access: Read-Only
> +
> + Valid values: Represented as a list of 13 32-bit PDO objects in hexadecimal format.
> +
> +What: /sys/class/power_supply/<supply_name>/sink_cap_pdos
> +Date: September 2021
> +Contact: linux-pm@vger.kernel.org
> +Description:
> + Reports the Sink Capabilities Power Data Objects (PDO) reported by the USB
> + PD-capable power source. 13 PDOs are listed. PDOs 1-7 represent the Sink Caps
> + for devices which only support Standard Power Range (SPR), whereas PDOs 8-13
> + are for Extended Power Range (EPR) capable sinks.
> + NOTE: The EPR Sink Caps message is a superset of the Sink Cap message, so on
> + SPR-only sinks, PDOs 8-13 will be 0.
> +
> + Access: Read-Only
> +
> + Valid values: Represented as a list of 13 32-bit PDO objects in hexadecimal format.

My plan is to register a separate power supply for each PDO. So for
every source PDO and every sink PDO a port has in its capabilities,
you'll have a separate power supply registered, and the same for the
partner when it's connected. With every connection there should always
be one active (online) source psy and active sink psy (if the port is
source, one of the port's source psys will be active and the partner
will have the active sink psy, or vise versa - depending on the role).

Each PDO represents a "Power Supply" so to me that approach just
makes the most sense. It will require a bit of work in kernel, however
in user space it should mean that we only have a single new attribute
file for the power supplies named "pdo" that returns a single PDO.

Let me know if you guys see any obvious problems with the idea.
Otherwise, that is how we really need to do this. That will make
things much more clear in user space. I have a feeling it will make
things easier in kernel as well in the long run.

Adding Adam and Guenter. It would be good if you guys could comment
the idea as well.

thanks,

--
heikki

\
 
 \ /
  Last update: 2021-09-13 16:07    [W:0.558 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site