Home
last modified time | relevance | path

Searched refs:VID (Results 1 – 25 of 46) sorted by relevance

12

/Linux-v4.19/drivers/net/ethernet/mellanox/mlxsw/
Dspectrum_acl_flex_keys.c14 MLXSW_AFK_ELEMENT_INST_U32(VID, 0x08, 0, 12),
22 MLXSW_AFK_ELEMENT_INST_U32(VID, 0x08, 0, 12),
53 MLXSW_AFK_ELEMENT_INST_U32(VID, 0x00, 0, 12),
131 MLXSW_AFK_ELEMENT_INST_U32(VID, 0x04, 16, 12),
137 MLXSW_AFK_ELEMENT_INST_U32(VID, 0x04, 16, 12),
142 MLXSW_AFK_ELEMENT_INST_U32(VID, 0x04, 16, 12),
Dcore_acl_flex_keys.h82 MLXSW_AFK_ELEMENT_INFO_U32(VID, 0x10, 8, 12),
/Linux-v4.19/Documentation/devicetree/bindings/usb/
Dusb-device.txt21 - compatible: "usbVID,PID", where VID is the vendor id and PID the product id.
22 The textual representation of VID and PID shall be in lower case hexadecimal
36 - compatible: "usbifVID,PID.configCN.IN", where VID is the vendor id, PID is
38 number. The textual representation of VID, PID, CN and IN shall be in lower
50 - compatible: "usbVID,PID", where VID is the vendor id and PID the product id.
51 The textual representation of VID and PID shall be in lower case hexadecimal
/Linux-v4.19/drivers/gpu/drm/sti/
DNOTES11 - The video plug (VID) connects to the HQVDP output.
28 Vid >--+ HQVDP +--+VID Aux +---+ | :===========:
42 buffers) and to HQVDP+VID (video buffers)
56 +-> | HQVDP | |VID Aux |<+ | | | :===========: |
/Linux-v4.19/Documentation/hwmon/
Dadm102537 input, or as the a fifth digital entry for the VID reading (bit 4). It's
43 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
50 only in that it has "open-drain VID inputs while the ADM1025 has on-chip
51 100k pull-ups on the VID inputs". It doesn't make any difference for us.
Dw83627hf57 VID reading. However the two chips have the identical 128 pin package. So,
58 it is possible or even likely for a w83627thf to have the VID signals routed
60 the w83627thf driver interprets these as VID. If the VID on your board
62 doesn't help, you may just ignore the bogus VID reading with no harm done.
Dsmsc47m19225 as well as CPU voltage VID input.
42 a +12V voltage measurement or a 5 bit CPU VID, but not both.
43 The default setting is to use the pin as 12V input, and use only 4 bit VID.
100 vrm - CPU VID standard used for decoding CPU voltage
Dlm7826 the LM78 and LM78-J are exactly identical. The LM79 has one more VID line,
31 seven voltage sensors, VID lines, alarms, and some miscellaneous stuff.
55 The VID lines encode the core voltage value: the voltage level your processor
Dasb10025 sensors, four temperature sensors, VID lines and alarms. In addition to
38 The VID lines encode the core voltage value: the voltage level your
Dadm102690 The datasheet shows an example application with VID signals attached to
91 GPIO lines. Unfortunately, the chip may not be connected to the VID lines
93 get a VID voltage.
Dit87131 The IT8712F and IT8716F additionally feature VID inputs, used to report
132 the Vcore voltage of the processor. The early IT8712F have 5 VID pins,
136 The IT8718F and IT8720F also features VID inputs (up to 8 pins) but the value
139 the driver won't notice and report changes in the VID value. The two
140 upper VID bits share their pins with voltage inputs (in5 and in6) so you
201 The VID lines (IT8712F/IT8716F/IT8718F/IT8720F) encode the core voltage value:
Dw8379339 sets of 6-pin CPU VID input.
97 * VID and VRM
Dlm9331 VID" from the datasheet. It greatly simplifies the interface to allow
37 A "0" configures the VID pins for V(ih) = 2.1V min, V(il) = 0.8V max.
38 A "1" configures the VID pins for V(ih) = 0.8V min, V(il) = 0.4V max.
40 I.e. this parameter controls the VID pin input thresholds; if your VID
Dadt747535 measurement inputs and VID support. The ADT7490 also has additional
73 * VID support
Dadm9240143 VID Monitor
145 The chip has five inputs to read the 5-bit VID and reports the mV value
Df71805f43 6 VID inputs. The VID inputs are not yet supported by this driver.
Dpc87360153 When available, VID inputs are used to provide the nominal CPU Core voltage.
155 The chipsets can handle two sets of VID inputs (on dual-CPU systems), but
/Linux-v4.19/Documentation/usb/
Dlinux-cdc-acm.inf82 ; When developing your USB device, the VID and PID used in the PC side
84 ; Modify the below line to use your VID and PID. Use the format as shown
87 ; VID and PIDs. For each supported device, append
/Linux-v4.19/drivers/cpufreq/
Dpowernow-k7.h14 VID:5, // 12:8 member
Dpowernow-k7.c238 if (fidvidctl.bits.VID != vid) { in change_VID()
240 fidvidctl.bits.VID = vid; in change_VID()
/Linux-v4.19/include/uapi/linux/
Dif_vlan.h55 int VID; member
/Linux-v4.19/drivers/gpu/drm/radeon/
Dtrinityd.h41 # define VID(x) ((x) << 16) macro
/Linux-v4.19/drivers/scsi/megaraid/
DKconfig.megaraid23 OEM Product Name VID :DID :SVID:SSID
/Linux-v4.19/net/8021q/
Dvlan.c614 err = register_vlan_device(dev, args.u.VID); in vlan_ioctl_handler()
635 args.u.VID = vlan_dev_vlan_id(dev); in vlan_ioctl_handler()
/Linux-v4.19/Documentation/media/uapi/mediactl/
Dmedia-types.rst29 .. _MEDIA-ENT-F-IF-VID-DECODER:
42 .. _MEDIA-ENT-F-VID-MUX:
43 .. _MEDIA-ENT-F-VID-IF-BRIDGE:

12