Home
last modified time | relevance | path

Searched full:vid (Results 1 – 25 of 65) sorted by relevance

123

/Documentation/networking/device_drivers/ethernet/ti/
Dam65_nuss_cpsw_switchdev.rst65 [*] bridge vlan add dev br0 vid 1 pvid untagged self
84 bridge vlan add dev br0 vid 1 pvid untagged self <---- add cpu port to VLAN 1
93 bridge vlan add dev sw0p1 vid 100 pvid untagged master
94 bridge vlan add dev sw0p2 vid 100 pvid untagged master
95 bridge vlan add dev br0 vid 100 pvid untagged self <---- Add cpu port to VLAN100
99 bridge vlan add dev sw0p1 vid 100 master
100 bridge vlan add dev sw0p2 vid 100 master
101 bridge vlan add dev br0 vid 100 pvid tagged self <---- Add cpu port to VLAN100
120 bridge mdb add dev br0 port sw0p1 grp 239.1.1.1 permanent vid 100
135 bridge vlan add dev sw0p1 vid 100 pvid untagged master
[all …]
Dcpsw_switchdev.rst115 [*] bridge vlan add dev br0 vid 1 pvid untagged self
134 bridge vlan add dev br0 vid 1 pvid untagged self <---- add cpu port to VLAN 1
143 bridge vlan add dev sw0p1 vid 100 pvid untagged master
144 bridge vlan add dev sw0p2 vid 100 pvid untagged master
145 bridge vlan add dev br0 vid 100 pvid untagged self <---- Add cpu port to VLAN100
149 bridge vlan add dev sw0p1 vid 100 master
150 bridge vlan add dev sw0p2 vid 100 master
151 bridge vlan add dev br0 vid 100 pvid tagged self <---- Add cpu port to VLAN100
170 bridge mdb add dev br0 port sw0p1 grp 239.1.1.1 permanent vid 100
185 bridge vlan add dev sw0p1 vid 100 pvid untagged master
[all …]
/Documentation/ABI/testing/
Dsysfs-driver-wacom1 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed
6 The /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed file
12 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/led
23 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status0_luminance
33 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status1_luminance
42 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status_led0_select
52 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status_led1_select
61 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/buttons_luminance
68 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/button<n>_rawimg
87 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_remote/unpair_remote
[all …]
/Documentation/devicetree/bindings/extcon/
Dextcon-palmas.txt6 * "ti,palmas-usb-vid".
7 * "ti,twl6035-usb-vid".
8 * "ti,palmas-usb" (DEPRECATED - use "ti,palmas-usb-vid").
9 * "ti,twl6035-usb" (DEPRECATED - use "ti,twl6035-usb-vid").
/Documentation/hwmon/
Dw83627hf.rst57 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
61 doesn't work, first see doc/vid in the lm_sensors package[1]. If that still
62 doesn't help, you may just ignore the bogus VID reading with no harm done.
66 [1] http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/vid
Dadm1025.rst46 input, or as the a fifth digital entry for the VID reading (bit 4). It's
52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
59 only in that it has "open-drain VID inputs while the ADM1025 has on-chip
60 100k pull-ups on the VID inputs". It doesn't make any difference for us.
Dmp2856.rst30 - Can configured VOUT readout in direct or VID format and allows
31 setting of different formats on rails 1 and 2. For VID the following
46 Device supports VID and direct formats for reading output voltage.
47 The below VID modes are supported: AMD SVI3.
Dmp2975.rst30 - Can configured VOUT readout in direct or VID format and allows
31 setting of different formats on rails 1 and 2. For VID the following
47 Device supports VID and direct formats for reading output voltage.
48 The below VID modes are supported: VR12, VR13, IMVP9.
Dsmsc47m192.rst36 as well as CPU voltage VID input.
53 a +12V voltage measurement or a 5 bit CPU VID, but not both.
54 The default setting is to use the pin as 12V input, and use only 4 bit VID.
112 vrm CPU VID standard used for decoding CPU voltage
Dlm78.rst38 the LM78 and LM78-J are exactly identical. The LM79 has one more VID line,
43 seven voltage sensors, VID lines, alarms, and some miscellaneous stuff.
67 The VID lines encode the core voltage value: the voltage level your processor
Dasb100.rst29 sensors, four temperature sensors, VID lines and alarms. In addition to
42 The VID lines encode the core voltage value: the voltage level your
Dadm1026.rst98 The datasheet shows an example application with VID signals attached to
99 GPIO lines. Unfortunately, the chip may not be connected to the VID lines
101 get a VID voltage.
Dit87.rst241 The IT8712F and IT8716F additionally feature VID inputs, used to report
242 the Vcore voltage of the processor. The early IT8712F have 5 VID pins,
246 The IT8718F and IT8720F also features VID inputs (up to 8 pins) but the value
249 the driver won't notice and report changes in the VID value. The two
250 upper VID bits share their pins with voltage inputs (in5 and in6) so you
312 The VID lines (IT8712F/IT8716F/IT8718F/IT8720F) encode the core voltage value:
Dw83793.rst44 sets of 6-pin CPU VID input.
104 * VID and VRM
/Documentation/networking/dsa/
Db53.rst62 By default packages are tagged with vid 1:
94 bridge vlan add dev lan1 vid 2 pvid untagged
95 bridge vlan del dev lan1 vid 1
96 bridge vlan add dev lan2 vid 3 pvid untagged
97 bridge vlan del dev lan2 vid 1
175 bridge vlan add dev wan vid 2 pvid untagged
176 bridge vlan del dev wan vid 1
Dconfiguration.rst205 bridge vlan add dev lan1 vid 1 pvid untagged
206 bridge vlan add dev lan2 vid 2 pvid untagged
207 bridge vlan add dev lan3 vid 3 pvid untagged
247 bridge vlan add dev lan1 vid 1 pvid untagged
248 bridge vlan add dev lan2 vid 1 pvid untagged
249 bridge vlan add dev lan3 vid 1 pvid untagged
288 bridge vlan add dev lan1 vid 1 pvid untagged
289 bridge vlan add dev lan2 vid 1 pvid untagged
290 bridge vlan add dev wan vid 2 pvid untagged
/Documentation/devicetree/bindings/usb/
Dusb-device.yaml33 "usbVID,PID", where VID is the vendor id and PID the product id.
34 The textual representation of VID and PID shall be in lower case
64 "usbifVID,PID.configCN.IN", where VID is the vendor id, PID is
66 number. The textual representation of VID, PID, CN and IN shall be
/Documentation/devicetree/bindings/input/touchscreen/
Dhideep.txt11 - vid-supply : It is the controller supply for controlling
35 vid-supply = <&ldo18_reg>;
/Documentation/devicetree/bindings/display/ti/
Dti,am65x-dss.yaml35 - description: VID video plane
46 - const: vid
148 <0x04a06000 0x1000>, /* vid */
154 reg-names = "common", "vidl1", "vid",
/Documentation/devicetree/bindings/iio/magnetometer/
Dasahi-kasei,ak8975.yaml51 vid-supply:
53 an optional regulator that needs to be on to provide VID power to
/Documentation/networking/
Dswitchdev.rst189 bridge fdb add dev DEV ADDRESS [vlan VID] [self] static
202 bridge fdb add dev DEV ADDRESS [vlan VID] master static
440 of a VLAN-aware bridge doing ingress VID checking). See below for details.
465 device with a VID that is not programmed into the bridge/switch's VLAN table
469 the device with a VID that is not programmed into the bridges/switch's VLAN
470 table must be dropped (strict VID checking).
485 configured to map all traffic, except the packets tagged with a VID
486 belonging to a VLAN upper interface, to an internal VID corresponding to
487 untagged packets. This internal VID spans all ports of the VLAN-unaware
488 bridge. The VID corresponding to the VLAN upper interface spans the
[all …]
/Documentation/admin-guide/perf/
Dcxl.rst64 $# perf stat -a -e cxl_pmu_mem0.0/vid=VID,gid=GID,mask=MASK/
/Documentation/devicetree/bindings/regulator/
Dmaxim,max8952.yaml67 max8952,vid-gpios:
95 max8952,vid-gpios = <&gpx0 3 GPIO_ACTIVE_HIGH>,
/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/
Dtracepoints.rst59 …: mlx5_esw_bridge_fdb_entry_init: net_device=enp8s0f0_0 addr=e4:fd:05:08:00:02 vid=0 flags=0 used=0
66 …x5_esw_bridge_fdb_entry_cleanup: net_device=enp8s0f0_1 addr=e4:fd:05:08:00:03 vid=0 flags=0 used=16
74 …lx5_esw_bridge_fdb_entry_refresh: net_device=enp8s0f0_0 addr=e4:fd:05:08:00:02 vid=3 flags=0 used=0
82 ip-2560 [007] ...1 318.460258: mlx5_esw_bridge_vlan_create: vid=1 flags=6
90 bridge-2582 [007] ...1 318.653496: mlx5_esw_bridge_vlan_cleanup: vid=2 flags=8
/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

123