Searched refs:SVID (Results 1 – 12 of 12) sorted by relevance
10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for14 modes by using the SVID and the mode number.24 matching SVID and mode. Communication between the port driver and alternate mode28 alternate mode drivers, so the port drivers are only expected to pass the SVID30 partners to the alternate mode drivers. No direct SVID specific communication is47 will be used to deliver all the SVID specific commands from the partner to the49 the SVID specific commands to each other using :c:func:`typec_altmode_vdm()`.51 If the communication with the partner using the SVID specific commands results54 passes the negotiated SVID specific pin configuration value to the function as58 NOTE: The SVID specific pin configuration values must always start from[all …]
47 Alternate Mode SVID will have their own device describing them. Note that the146 Alternate Mode will have identifier called SVID, which is either a Standard ID147 given by USB-IF or vendor ID, and each supported SVID can have 1 - 6 modes. The148 class provides struct typec_mode_desc for describing individual mode of a SVID,151 Ports that support Alternate Modes need to register each SVID they support with158 Delivery Structured VDM Discover SVIDs message, each SVID needs to be
35 SVID:5, // 44:40 member
40 - Intel SVID protocol.49 - Intel SVID protocol.
36 - SVID interface.
29 - Intel SVID rev 1.93. protocol.
34 - Intel SVID rev 1.9. protocol.
37 - SVID interface.
43 The Standard or Vendor ID (SVID) assigned by USB-IF for this
8 The SVID (Standard or Vendor ID) assigned by USB-IF for this
24 OEM Product Name VID :DID :SVID:SSID
388 case SVID: in vivid_update_format_cap()1088 case SVID: in vidioc_enum_input()1160 if (dev->input_type[i] == TV || dev->input_type[i] == SVID) { in vidioc_s_input()1174 case SVID: in vidioc_s_input()