Searched refs:ven (Results 1 – 11 of 11) sorted by relevance
| /linux/include/linux/ |
| A D | hid.h | 740 #define HID_DEVICE(b, g, ven, prod) \ argument
741 .bus = (b), .group = (g), .vendor = (ven), .product = (prod)
742 #define HID_USB_DEVICE(ven, prod) \ argument
743 .bus = BUS_USB, .vendor = (ven), .product = (prod)
744 #define HID_BLUETOOTH_DEVICE(ven, prod) \ argument
745 .bus = BUS_BLUETOOTH, .vendor = (ven), .product = (prod)
746 #define HID_I2C_DEVICE(ven, prod) \ argument
747 .bus = BUS_I2C, .vendor = (ven), .product = (prod)
|
| A D | rio_drv.h | 291 #define RIO_DEVICE(dev,ven) \ argument
292 .did = (dev), .vid = (ven), \
|
| /linux/include/scsi/ |
| A D | libfcoe.h | 288 #define MODULE_ALIAS_FCOE_PCI(ven, dev) \ argument
290 "v" __stringify(ven) \
|
| /linux/drivers/hid/bpf/progs/ |
| A D | hid_bpf_helpers.h | 100 #define HID_DEVICE(b, g, ven, prod) \ argument
105 __uint(vid, (ven)); \
|
| /linux/drivers/video/fbdev/matrox/ |
| A D | matroxfb_misc.c | 791 unsigned int ven = readb(b+0x64+0) | (readb(b+0x64+1) << 8); in matroxfb_read_pins() local
794 if (ven != pdev->vendor || dev != pdev->device) { in matroxfb_read_pins()
796 ven, dev, pdev->vendor, pdev->device); in matroxfb_read_pins()
|
| /linux/arch/arm64/boot/dts/mediatek/ |
| A D | mt6795-sony-xperia-m5.dts | 321 pins-fw-ven {
|
| /linux/arch/arm64/boot/dts/qcom/ |
| A D | msm8998-sony-xperia-yoshino.dtsi | 836 nfc_ven: nfc-ven-state {
|
| /linux/Documentation/translations/sp_SP/process/ |
| A D | 2.Process.rst | 105 que causan regresiones se ven con malos ojos y es bastante probable que
|
| A D | coding-style.rst | 1132 Vim interpreta los marcadores que se ven así:
|
| /linux/arch/arm/boot/dts/nvidia/ |
| A D | tegra30-lg-x3.dtsi | 394 nfc-ven {
|
| /linux/Documentation/translations/sp_SP/ |
| A D | memory-barriers.txt | 1325 Muchas CPU especulan con las cargas: es decir, ven que necesitarán cargar
2852 determinada, ya que las CPU siempre ven sus propias cargas y stores como si
|
Completed in 37 milliseconds