vendor\-specific (full) in projects: Documentation

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:vendor +full:- +full:specific (Results 1 – 25 of 168) sorted by relevance

12 3 4 5 6 7

/Documentation/devicetree/bindings/
D	example-schema.yaml	`1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 # All the top-level keys are standard json-schema keywords except for 10 $id: http://devicetree.org/schemas/example-schema.yaml# 11 # $schema is the meta-schema this schema should be validated with. 12 $schema: http://devicetree.org/meta-schemas/core.yaml# 17 - Rob Herring <robh@kernel.org> 20 A more detailed multi-line description of the binding. 44 - items: 51 - enum: [all …]`
D	writing-bindings.rst	1 .. SPDX-License-Identifier: GPL-2.0 11 Documentation/devicetree/bindings/submitting-patches.rst 17 - DO attempt to make bindings complete even if a driver doesn't support some 21 - DON'T refer to Linux or "device driver" in bindings. Bindings should be 24 - DO use node names matching the class of the device. Many standard names are 27 - DO check that the example matches the documentation especially after making 30 - DON'T create nodes just for the sake of instantiating drivers. Multi-function 34 - DON'T use 'syscon' alone without a specific compatible string. A 'syscon' 42 - DO make 'compatible' properties specific. DON'T use wildcards in compatible 47 - DO use a vendor prefix on device-specific property names. Consider if [all …]
/Documentation/ABI/obsolete/
D	sysfs-driver-hid-roccat-isku	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 4 Description: The integer value of this attribute ranges from 0-4. 12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 20 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 35 capslock key for a specific profile. Profile number is included 41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 45 easyzone keys for a specific profile. Profile number is included 51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 55 function keys for a specific profile. Profile number is included [all …]
D	sysfs-driver-hid-roccat-ryos	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 9 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 25 a specific profile. Profile index is included in written data. 31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 35 function keys for a specific profile. Profile index is included 41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 45 keys for a specific profile. Profile index is included in 51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 55 thumbster keys for a specific profile. Profile index is included [all …]
D	sysfs-driver-hid-roccat-arvo	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 4 Description: The integer value of this attribute ranges from 1-5. 11 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 16 When written, this file lets one set the sequence for a specific 17 button for a specific profile. Button and profile numbers are 22 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 37 The integer value of this attribute has bits 0-4 set depending 44 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 47 Description: The keyboard has a condensed layout without num-lock key. [all …]
D	sysfs-driver-hid-roccat-savu	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 17 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 25 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 40 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 48 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 52 keystrokes for a specific button for a specific profile. 59 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 74 Description: The mouse has a Avago ADNS-3090 sensor.
D	sysfs-driver-hid-roccat-konepure	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 13 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 29 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 34 When written, this file lets one set the sequence for a specific 35 button for a specific profile. Button and profile numbers are 40 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 55 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 74 Description: The mouse has a tracking- and a distance-control-unit. These [all …]
D	sysfs-driver-hid-roccat-koneplus	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 4 Description: The integer value of this attribute ranges from 0-4. 12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 15 Description: The integer value of this attribute ranges from 0-4. 24 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 36 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 44 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 49 When written, this file lets one set the sequence for a specific 50 button for a specific profile. Button and profile numbers are 55 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… [all …]
/Documentation/ABI/testing/
D	sysfs-bus-cdx	14 What: /sys/bus/cdx/devices/.../vendor 18 Vendor ID for this CDX device, in hexadecimal. Vendor ID is 19 16 bit identifier which is specific to the device manufacturer. 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 44 Subsystem Device ID is 16 bit identifier specific to the 117 - vXXXX contains the vendor ID; 118 - dXXXX contains the device ID; [all …]
D	sysfs-bus-vfio-mdev	8 vendor driver who registers with Mediated device framework. 11 string provided by the vendor driver. 13 What: /sys/.../<device>/mdev_supported_types/<type-id>/ 20 attributes to be provided by vendor driver. 'name', 21 'description' and other vendor driver specific attributes 24 What: /sys/.../mdev_supported_types/<type-id>/create 29 type <type-id> for parent device <device>. This is a 30 write-only file. 33 # echo "83b8f4f2-509f-382f-3c1e-e6bfe0fa1001" > \ 34 /sys/devices/foo/mdev_supported_types/foo-1/create [all …]
D	sysfs-bus-nfit	10 (RO) Serial number of the NVDIMM (non-volatile dual in-line 11 memory module), assigned by the module vendor. 28 (RO) Device id for the NVDIMM, assigned by the module vendor. 36 (RO) Revision of the NVDIMM, assigned by the module vendor. 54 (RO) The flags in the NFIT memory device sub-structure indicate 80 only expect one code per-dimm as they will ignore 84 What: /sys/bus/nd/devices/nmemX/nfit/vendor 89 (RO) Vendor id of the NVDIMM. 97 (RO) The bitmask indicates the supported device specific control 113 http://pmem.io/documents/NVDIMM_DSM_Interface-V1.6.pdf [all …]
/Documentation/devicetree/bindings/tpm/
D	tcg,tpm-tis-i2c.yaml	1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/tpm/tcg,tpm-tis-i2c.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: I²C-attached Trusted Platform Module conforming to TCG TIS specification 10 - Lukas Wunner <lukas@wunner.de> 13 The Trusted Computing Group (TCG) has defined a multi-vendor standard 16 TCG PC Client Specific TPM Interface Specification (TIS) 17 …tps://trustedcomputinggroup.org/resource/pc-client-work-group-pc-client-specific-tpm-interface-spe… 22 https://trustedcomputinggroup.org/resource/pc-client-platform-tpm-profile-ptp-specification/ [all …]
D	tcg,tpm-tis-mmio.yaml	1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/tpm/tcg,tpm-tis-mmio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: MMIO-accessed Trusted Platform Module conforming to TCG TIS specification 10 - Lukas Wunner <lukas@wunner.de> 13 The Trusted Computing Group (TCG) has defined a multi-vendor standard 16 TCG PC Client Specific TPM Interface Specification (TIS) 17 …tps://trustedcomputinggroup.org/resource/pc-client-work-group-pc-client-specific-tpm-interface-spe… 22 - enum: [all …]
/Documentation/devicetree/bindings/pci/
D	snps,dw-pcie-ep.yaml	`1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jingoo Han <jingoohan1@gmail.com> 11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com> 16 # Please create a separate DT-schema for your DWC PCIe Endpoint controller 17 # and make sure it's assigned with the vendor-specific compatible string. 21 const: snps,dw-pcie-ep 23 - compatible [all …]`
D	snps,dw-pcie.yaml	`1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jingoo Han <jingoohan1@gmail.com> 11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com> 16 # Please create a separate DT-schema for your DWC PCIe Root Port controller 17 # and make sure it's assigned with the vendor-specific compatible string. 21 const: snps,dw-pcie 23 - compatible [all …]`
/Documentation/usb/
D	mtouchusb.rst	8 - 0.3 - Created based off of scanner & INSTALL from the original touchscreen 10 - Amended for linux-2.4.18, then 2.4.19 12 - 0.5 - Complete rewrite using Linux Input in 2.6.3 15 - 1.4 - Multiple changes to support the EXII 5000UC and house cleaning 16 Changed reset from standard USB dev reset to vendor reset 18 Eliminated vendor/product module params 19 Performed multiple successful tests with an EXII-5010UC 26 All controllers have the Vendor: 0x0596 & Product: 0x0001 30 ------------------------------------------------------ 32 USB Capacitive - Pearl Case 14-205 (Discontinued) [all …]
/Documentation/process/
D	embargoed-hardware-issues.rst	7 ----- 23 ------- 31 Linux kernel security team (:ref:`Documentation/admin-guide/ 34 The team can be contacted by email at <hardware-security@kernel.org>. This 43 - PGP: https://www.kernel.org/static/files/hardware-security.asc 44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt 47 vendor, we welcome contact from researchers or individuals who have 55 - Linus Torvalds (Linux Foundation Fellow) 56 - Greg Kroah-Hartman (Linux Foundation Fellow) 57 - Thomas Gleixner (Linux Foundation Fellow) [all …]
D	maintainer-soc.rst	1 .. SPDX-License-Identifier: GPL-2.0 8 -------- 10 The SoC subsystem is a place of aggregation for SoC-specific code. 13 * devicetrees for 32- & 64-bit ARM and RISC-V 14 * 32-bit ARM board files (arch/arm/mach) 15 32- & 64-bit ARM defconfigs 16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit 17 ARM, RISC-V and Loongarch 19 These "SoC-specific drivers" do not include clock, GPIO etc drivers that have 20 other top-level maintainers. The drivers/soc/ directory is generally meant [all …]
/Documentation/admin-guide/perf/
D	cxl.rst	1 .. SPDX-License-Identifier: GPL-2.0 28 In common with other CXL bus devices, the id has no specific meaning and the 29 relationship to specific CXL device should be established via the device parent 34 The "format" directory describes all formats of the config (event vendor id, 58 ----------------------------------------------------------- 60 $# perf stat -a -e cxl_pmu_mem0.0/clock_ticks/ -e cxl_pmu_mem0.0/d2h_req_rdshared/ 62 Vendor specific events may also be available and if so can be used via 64 $# perf stat -a -e cxl_pmu_mem0.0/vid=VID,gid=GID,mask=MASK/ 67 It only supports system-wide counting so attaching to a task is
/Documentation/driver-api/virtio/
D	virtio.rst	1 .. SPDX-License-Identifier: GPL-2.0 24 Device - Driver communication: virtqueues 29 using a specific transport method -- PCI, MMIO or CCW -- that is 40 .. kernel-doc:: include/uapi/linux/virtio_ring.h 56 .. kernel-doc:: include/linux/virtio.h 63 a virtqueue during the virtqueue setup process (transport-specific). 65 .. kernel-doc:: drivers/virtio/virtio_ring.c 73 transport-specific drivers like `virtio-pci` and `virtio-mmio`. Then 74 there are individual virtio drivers for specific device types that are 78 the hypervisor defines it. Taking the `QEMU virtio-console [all …]
/Documentation/virt/kvm/
D	review-checklist.rst	1 .. SPDX-License-Identifier: GPL-2.0 7 1. The patch must follow Documentation/process/coding-style.rst and 8 Documentation/process/submitting-patches.rst. 13 - the API must be documented in Documentation/virt/kvm/api.rst 14 - the API must be discoverable using KVM_CHECK_EXTENSION 23 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git 26 8. Changes should be vendor neutral when possible. Changes to common code 27 are better than duplicating changes to vendor code. 32 10. User/kernel interfaces and guest/host interfaces must be 64-bit clean 33 (all variables and sizes naturally aligned on 64-bit; use specific types [all …]
/Documentation/devicetree/bindings/interrupt-controller/
D	msi.txt	`14 - The doorbell (the MMIO address written to). 19 - The payload (the value written to the doorbell). 24 - Sideband information accompanying the write. 38 -------------------- 40 - msi-controller: Identifies the node as an MSI controller. 43 -------------------- 45 - #msi-cells: The number of cells in an msi-specifier, required if not zero. 50 The meaning of the msi-specifier is defined by the device tree binding of 51 the specific MSI controller. 62 -------------------- [all …]`
/Documentation/devicetree/bindings/arm/
D	primecell.yaml	`1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Rob Herring <robh@kernel.org> 14 identify the peripheral type, vendor, and revision. This value can be used for 22 Should be a specific name for the peripheral followed by "arm,primecell". 23 The specific name will match the ARM engineering name for the logic block 26 arm,primecell-periphid: 32 clock-names:`
/Documentation/driver-api/usb/
D	typec_bus.rst	2 API for USB Type-C Alternate Mode drivers 6 ------------ 8 Alternate modes require communication with the partner using Vendor Defined 9 Messages (VDM) as defined in USB Type-C and USB Power Delivery Specifications. 10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for 13 USB Type-C bus allows binding a driver to the discovered partner alternate 16 :ref:`USB Type-C Connector Class <typec>` provides a device for every alternate 29 specific commands from the alternate mode drivers to the partner, and from the 30 partners to the alternate mode drivers. No direct SVID specific communication is 36 ------ [all …]
/Documentation/nvme/
D	feature-and-quirk-policy.rst	1 .. SPDX-License-Identifier: GPL-2.0 20 - the NVMe Base specification 21 - various Command Set specifications (e.g. NVM Command Set) 22 - various Transport specifications (e.g. PCIe, Fibre Channel, RDMA, TCP) 23 - the NVMe Management Interface specification 32 useful or suitable for specific use-cases. It is important to note that Linux 44 on-wire protocol, does not contradict any of the NVMe specifications. 47 3. Has a clear, indisputable value-proposition and a wide consensus across 50 Vendor specific extensions are generally not supported in the NVMe host 63 of the standards. Linux uses identifier-based quirks to work around such [all …]

12 3 4 5 6 7

Documentation
LICENSES
arch
block
certs
crypto
drivers
fs
gki
include
init
io_uring
ipc
kernel
lib
mm
net
rust
samples
scripts
security
sound
tools
usr
virt