Home
last modified time | relevance | path

Searched refs:Vendor (Results 1 – 25 of 62) sorted by relevance

123

/linux/drivers/gpu/nova-core/
H A Ddriver.rs14 Vendor, //
53 Vendor::NVIDIA
61 Vendor::NVIDIA
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-cdx18 Vendor ID for this CDX device, in hexadecimal. Vendor ID is
20 Combination of Vendor ID and Device ID identifies a device.
29 Combination of Vendor ID and Device ID identifies a device.
35 Subsystem Vendor ID for this CDX device, in hexadecimal.
36 Subsystem Vendor ID is 16 bit identifier specific to the
H A Dsysfs-firmware-lefi-boardinfo24 Vendor : Kunlun
H A Dsysfs-bus-typec43 The Standard or Vendor ID (SVID) assigned by USB-IF for this
H A Dsysfs-bus-pci43 VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID,
44 Device ID, Subsystem Vendor ID, Subsystem Device ID,
45 Class, Class Mask, and Private Driver Data. The Vendor ID
60 VVVV DDDD SVVV SDDD CCCC MMMM. That is Vendor ID, Device
61 ID, Subsystem Vendor ID, Subsystem Device ID, Class,
62 and Class Mask. The Vendor ID and Device ID fields are
593 The contents of each file is the raw Vendor ID and data
H A Dsysfs-bus-platform-devices-ampere-smpro5 (RO) Contains the 48-byte Ampere (Vendor-Specific) Error Record printed
174 For details, see section `3.3 Ampere (Vendor-Specific) Error Record Formats,
/linux/rust/kernel/
H A Dpci.rs41 Vendor, //
157 pub const fn from_id(vendor: Vendor, device: u32) -> Self { in from_id() argument
196 vendor: Vendor, in from_class_and_vendor() argument
354 pub fn vendor_id(&self) -> Vendor { in vendor_id() argument
357 Vendor::from_raw(vendor_id) in vendor_id()
/linux/rust/kernel/pci/
H A Did.rs129 pub struct Vendor(u16); struct
135 impl Vendor { impl
142 impl fmt::Display for Vendor {
156 impl Vendor { implementation
170 impl fmt::Debug for Vendor { implementation
/linux/Documentation/driver-api/
H A Dipmb.rst55 Name (_HID, "<Vendor-Specific HID>") // Vendor-Specific HID
/linux/Documentation/networking/devlink/
H A Dnfp.rst41 - Vendor of the board design
/linux/
H A DREADME39 * Hardware Vendor - Writing drivers for new hardware
122 Hardware Vendor
/linux/samples/rust/
H A Drust_driver_pci.rs41 pci::DeviceId::from_id(pci::Vendor::REDHAT, 0x5),
H A Drust_dma.rs51 [(pci::DeviceId::from_id(pci::Vendor::REDHAT, 0x5), ())]
H A Drust_driver_auxiliary.rs64 [(pci::DeviceId::from_id(pci::Vendor::REDHAT, 0x5), ())]
/linux/Documentation/driver-api/usb/
H A Dtypec_bus.rst8 Alternate modes require communication with the partner using Vendor Defined
10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for
/linux/drivers/firmware/arm_scmi/vendors/imx/
H A DKconfig2 menu "ARM SCMI NXP i.MX Vendor Protocols"
/linux/Documentation/usb/
H A Dgadget_printer.rst48 This is the Vendor ID used in the device descriptor. The default is
51 already have a Vendor ID please see www.usb.org for details on how to
65 A string containing the name of the Vendor.
H A Dacm.rst77 P: Vendor=0000 ProdID=0000 Rev= 0.00
85 P: Vendor=04c1 ProdID=008f Rev= 2.07
H A Dlinux-cdc-acm.inf80 ; Vendor and Product ID Definitions
H A Dmtouchusb.rst26 All controllers have the Vendor: 0x0596 & Product: 0x0001
/linux/Documentation/ABI/obsolete/
H A Dsysfs-class-typec8 The SVID (Standard or Vendor ID) assigned by USB-IF for this
/linux/arch/riscv/
H A DKconfig.vendor1 menu "Vendor extensions"
/linux/Documentation/admin-guide/perf/
H A Dcxl.rst62 Vendor specific events may also be available and if so can be used via
H A Ddwc_pcie_pmu.rst9 Port in a Vendor-Specific Extended Capability named RAS D.E.S (Debug, Error
/linux/drivers/staging/greybus/Documentation/
H A Dsysfs-bus-greybus138 Vendor ID of a Greybus interface.
167 Vendor ID string of a Greybus interface.

123