This series is based on usb-next commit 252427037a36 ("typec: tcpm: Fix
incorrect 'and' operator").
In my work trying to adapt my project to the latest kernel I have ran into
a number of issues. Consider the following series an initial poll on the
acceptance of the solutions I have found.
In short the issues are as follows:
- TYPEC_MUX_ constants have a lot of prejudice in their names. E.g. other
alternate modes than DisplayPort may appear as well as other combinations.
- It should be possible to limit the configurations the mux driver is allowed
to set, in case the hardware does not support all possible modes of a
specific mux device/driver.
- Some devices may need a default mux mode after connection different than
2ch USBSS, e.g. if the port does not support USBSS but only AM, then the
default mode could be set to _NONE or if the port supports _4CH_USBSS maybe
that should be the default.
Mats Karrman (7):
usb: typec: Generalize mux mode names
usb: typec: Move mux mode type definition to limit dependency
usb: typec: Add API to find mux mode from its string representation
dt-bindings: usb: Add general documentation for USB Type-C muxes
usb: typec: mux: pi3usb30532: Add support for supported mode
properties
dt-bindings: usb: typec-mux: Add property for default mux mode
usb: typec: mux: Allow default mux mode to be specified
.../devicetree/bindings/usb/typec-mux.txt | 20 ++++++++
drivers/usb/typec/class.c | 22 ++++++++
drivers/usb/typec/mux/pi3usb30532.c | 60 +++++++++++++++++-----
drivers/usb/typec/tcpm.c | 4 +-
include/linux/usb/tcpm.h | 13 -----
include/linux/usb/typec.h | 13 +++++
include/linux/usb/typec_mux.h | 4 +-
7 files changed, 107 insertions(+), 29 deletions(-)
create mode 100644 Documentation/devicetree/bindings/usb/typec-mux.txt
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
