usb: typec: Expose the partner USB PD product type to the userspace
Subsystems (2)
Heikki Krogerus
maintainercover usb: typec: Expose the partner USB PD product type to the userspace
Hi,
I think this was OK to everybody. The original RFC:
https://lore.kernel.org/lkml/[email protected]/
thanks,
Heikki Krogerus (2):
usb: pd: DFP product types
usb: typec: Add type sysfs attribute file for partners
Documentation/ABI/testing/sysfs-class-typec | 53 ++++++- drivers/usb/typec/class.c | 147 +++++++++++++++++--- include/linux/usb/pd_vdo.h | 15 +- 3 files changed, 193 insertions(+), 22 deletions(-)
Signature · 1 line
2.29.2
Heikki Krogerus
maintainerPATCH 1/2 usb: pd: DFP product types
USB Power Delivery Specification R3.0 introduced separate field for the DFP product type to the ID Header VDO.
--- include/linux/usb/pd_vdo.h | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
include/linux/usb/pd_vdo.h +12 -3
@@ -103,17 +103,25 @@* -------------------- * <31> :: data capable as a USB host * <30> :: data capable as a USB device -* <29:27> :: product type +* <29:27> :: product type (UFP / Cable) * <26> :: modal operation supported (1b == yes) -* <25:16> :: Reserved, Shall be set to zero +* <25:16> :: product type (DFP) * <15:0> :: USB-IF assigned VID for this cable vendor */ #define IDH_PTYPE_UNDEF 0#define IDH_PTYPE_HUB 1#define IDH_PTYPE_PERIPH 2 +#define IDH_PTYPE_PSD 3 +#define IDH_PTYPE_AMA 5 +#define IDH_PTYPE_PCABLE 3#define IDH_PTYPE_ACABLE 4 -#define IDH_PTYPE_AMA 5 + +#define IDH_PTYPE_DFP_UNDEF 0 +#define IDH_PTYPE_DFP_HUB 1 +#define IDH_PTYPE_DFP_HOST 2 +#define IDH_PTYPE_DFP_PB 3 +#define IDH_PTYPE_DFP_AMC 4#define VDO_IDH (usbh, usbd, ptype, is_modal, vid) \ ((usbh) << 31 | (usbd) << 30 | ((ptype) & 0x7) << 27 \
@@ -122,6 +130,7 @@#define PD_IDH_PTYPE (vdo) (((vdo) >> 27) & 0x7)#define PD_IDH_VID (vdo) ((vdo) & 0xffff)#define PD_IDH_MODAL_SUPP (vdo) ((vdo) & (1 << 26)) +#define PD_IDH_DFP_PTYPE (vdo) (((vdo) >> 23) & 0x7)/* * Cert Stat VDO
Signature · 1 line
2.29.2
Heikki Krogerus
maintainerPATCH 2/2 usb: typec: Add type sysfs attribute file for partners
In reply to Heikki KrogerusUSB Power Delivery Specification defines a set of product types for partners and cables. The product type can be read from the ID Header VDO which is the first object in the response to the Discover Identity command. This attribute will display the product type of the partner. The cables already have the attribute.
This sysfs attribute file is only created for the partners and cables if the product type is really known in the driver. Some interfaces do not give access to the Discover Identity response from the partner or cable, but they may still supply the product type separately in some cases.
When the product type of the partner or cable is detected, uevent is also raised with PRODUCT_TYPE set to show the actual product type (for example PRODUCT_TYPE=host).
--- Documentation/ABI/testing/sysfs-class-typec | 53 ++++++- drivers/usb/typec/class.c | 147 +++++++++++++++++--- 2 files changed, 181 insertions(+), 19 deletions(-)
Documentation/ABI/testing/sysfs-class-typec +50 -3
@@ -139,6 +139,41 @@ Description: Shows if the partner supports USB Power Delivery communication: Valid values: yes, no +What: /sys/class/typec/<port>-partner/type +Date: December 2020 +Contact: Heikki Krogerus <[email protected]> +Description: USB Power Delivery Specification defines a set of product types + for the partner devices. This file will show the product type of + the partner if it is known. Dual-role capable partners will have + both UFP and DFP product types defined, but only one that + matches the current role will be active at the time. If the + product type of the partner is not visible to the device driver, + this file will not exist. + + When the partner product type is detected, or changed with role + swap, uvevent is also raised that contains PRODUCT_TYPE=<product + type> (for example PRODUCT_TYPE=hub). + + Valid values: + + UFP / device role + ====================== ========================== + undefined - + hub PDUSB Hub + peripheral PDUSB Peripheral + psd Power Bank + ama Alternate Mode Adapter + ====================== ========================== + + DFP / host role + ====================== ========================== + undefined - + hub PDUSB Hub + host PDUSB Host + power_brick Power Brick + amc Alternate Mode Controller + ====================== ========================== + What: /sys/class/typec/<port>-partner>/identity/ Date: April 2017 Contact: Heikki Krogerus <[email protected]>
@@ -187,9 +222,21 @@ described in USB Type-C and USB Power Delivery specifications. What: /sys/class/typec/<port>-cable/type Date: April 2017 Contact: Heikki Krogerus <[email protected]> -Description: - Shows if the cable is active. - Valid values: active, passive +Description: USB Power Delivery Specification defines a set of product types + for the cables. This file will show the product type of the + cable if it is known. If the product type of the cable is not + visible to the device driver, this file will not exist. + + When the cable product type is detected, uvevent is also raised + with PRODUCT_TYPE showing the product type of the cable. + + Valid values: + + ====================== ========================== + undefined - + active Active Cable + passive Passive Cable + ====================== ========================== What: /sys/class/typec/<port>-cable/plug_type Date: April 2017
drivers/usb/typec/class.c +131 -16
220 lines not on this page · raw message
Signature · 1 line
2.29.2
Greg Kroah-Hartman
maintainerRe: [PATCH 2/2] usb: typec: Add type sysfs attribute file for partners
Quoted 17 lines · Heikki Krogerus
USB Power Delivery Specification defines a set of product types for partners and cables. The product type can be read from the ID Header VDO which is the first object in the response to the Discover Identity command. This attribute will display the product type of the partner. The cables already have the attribute.
This sysfs attribute file is only created for the partners and cables if the product type is really known in the driver. Some interfaces do not give access to the Discover Identity response from the partner or cable, but they may still supply the product type separately in some cases.
When the product type of the partner or cable is detected, uevent is also raised with
PRODUCT_TYPEset to show the actual product type (for example PRODUCT_TYPE=host).
Quoted 5 lines
Signed-off-by Heikki Krogerus <[email protected]>--- Documentation/ABI/testing/sysfs-class-typec | 53 ++++++- drivers/usb/typec/class.c | 147 +++++++++++++++++--- 2 files changed, 181 insertions(+), 19 deletions(-)
This patch doesn't apply against my usb-next branch (but patch 1/2 did). Can you rebase this and resend it?
thanks,
greg k-h
Heikki Krogerus
maintainerRe: [PATCH 2/2] usb: typec: Add type sysfs attribute file for partners
Quoted 18 lines · Greg Kroah-Hartman
Quoted 17 lines · Heikki Krogerus
USB Power Delivery Specification defines a set of product types for partners and cables. The product type can be read from the ID Header VDO which is the first object in the response to the Discover Identity command. This attribute will display the product type of the partner. The cables already have the attribute.
This sysfs attribute file is only created for the partners and cables if the product type is really known in the driver. Some interfaces do not give access to the Discover Identity response from the partner or cable, but they may still supply the product type separately in some cases.
When the product type of the partner or cable is detected, uevent is also raised with
PRODUCT_TYPEset to show the actual product type (for example PRODUCT_TYPE=host).
Quoted 8 lines
Quoted 5 lines
Signed-off-by Heikki Krogerus <[email protected]>--- Documentation/ABI/testing/sysfs-class-typec | 53 ++++++- drivers/usb/typec/class.c | 147 +++++++++++++++++--- 2 files changed, 181 insertions(+), 19 deletions(-)This patch doesn't apply against my usb-next branch (but patch 1/2 did). Can you rebase this and resend it?
OK.
Signature · 1 line
heikki