usb: typec: Add data structure for Enter_USB message
This data structure can be delivered to the mux drivers when Enter_USB Message is used exactly the same way as the Alternate Mode specific data structures are delivered to the mux drivers when Enter Mode Messages are used. The Enter_USB data structure shall have all details related to the Enter_USB Message, most importantly the Enter_USB Date Object that was used. Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> Link: https://lore.kernel.org/r/20200701115618.22482-3-heikki.krogerus@linux.intel.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
f470a65548
commit
ad8db94d68
|
@ -72,6 +72,20 @@ enum typec_orientation {
|
|||
TYPEC_ORIENTATION_REVERSE,
|
||||
};
|
||||
|
||||
/*
|
||||
* struct enter_usb_data - Enter_USB Message details
|
||||
* @eudo: Enter_USB Data Object
|
||||
* @active_link_training: Active Cable Plug Link Training
|
||||
*
|
||||
* @active_link_training is a flag that should be set with uni-directional SBRX
|
||||
* communication, and left 0 with passive cables and with bi-directional SBRX
|
||||
* communication.
|
||||
*/
|
||||
struct enter_usb_data {
|
||||
u32 eudo;
|
||||
unsigned char active_link_training:1;
|
||||
};
|
||||
|
||||
/*
|
||||
* struct usb_pd_identity - USB Power Delivery identity data
|
||||
* @id_header: ID Header VDO
|
||||
|
|
Loading…
Reference in a new issue