Searched full:requester (Results 1 – 21 of 21) sorted by relevance
| /Documentation/devicetree/bindings/pci/ |
| D | pci-iommu.txt | 4 Each PCI(e) device under a root complex is uniquely identified by its Requester
5 ID (AKA RID). A Requester ID is a triplet of a Bus number, Device number, and
17 Requester ID. While a given PCI device can only master through one IOMMU, a
35 - iommu-map: Maps a Requester ID to an IOMMU and associated IOMMU specifier
44 - iommu-map-mask: A mask to be applied to each Requester ID prior to being
|
| D | pci-msi.txt | 4 Each PCI device under a root complex is uniquely identified by its Requester ID
5 (AKA RID). A Requester ID is a triplet of a Bus number, Device number, and
18 Requester ID. A mechanism is required to associate a device with both the MSI
32 - msi-map: Maps a Requester ID to an MSI controller and associated
49 - msi-map-mask: A mask to be applied to each Requester ID prior to being mapped
|
| D | xilinx-versal-cpm.yaml | 40 Maps a Requester ID to an MSI controller and associated MSI sideband data.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-iommu | 20 filter_requester_en = "config1:0" - Enable Requester ID filter
25 filter_requester_id = "config1:16-31" - Requester ID filter
|
| D | sysfs-bus-event_source-devices-hisi_ptt | 93 Description: This directory contains the files providing the PCIe Requester filters
112 Description: (Read) Indicates the filter value of this Requester filter, which
|
| /Documentation/trace/ |
| D | hisi-ptt.rst | 115 Link. You can choose to filter the traced headers by either Requester ID,
137 The TLP headers to trace can be filtered by the Root Ports or the Requester ID
141 1 for Root Port filter and 0 for Requester filter. Bit[15:0] indicates the
143 calculated from its PCI Slot ID as (slotid & 7) * 2. The value for a Requester
144 is the Requester ID (Device ID of the PCIe function). Bit[18:16] is currently
151 The driver also presents every supported Root Port and Requester filter through
154 under $(PTT PMU dir)/root_port_filters and files of Requester filters
|
| /Documentation/driver-api/tty/ |
| D | n_gsm.rst | 119 Config Requester
169 /* we are requester and need encoding 0 (basic) */
|
| /Documentation/PCI/ |
| D | pcieaer-howto.rst | 79 …0:00.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, id=0500(Requester ID)
84 In the example, 'Requester ID' means the ID of the device that sent
|
| /Documentation/networking/ |
| D | nfc.rst | 93 the requester of STOP_POLL is the same of START_POLL.
|
| /Documentation/firmware-guide/acpi/apei/ |
| D | output_format.rst | 128 Receiver ID | Requester ID | Completer ID | Transmitter ID
|
| /Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.yaml | 28 the requester.
|
| /Documentation/filesystems/ |
| D | autofs.rst | 464 struct args_requester requester;
504 On successful return, `requester.uid` and `requester.gid` will be
|
| D | autofs-mount-control.rst | 193 struct args_requester requester;
|
| /Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 17 the physical memory read back to the requester.
|
| /Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 39 Typically a requester wants the VCPU to perform the activity as soon
|
| /Documentation/translations/zh_CN/process/ |
| D | coding-style.rst | 308 '{initiator,requester} / {target,responder}'
|
| /Documentation/translations/zh_TW/process/ |
| D | coding-style.rst | 311 '{initiator,requester} / {target,responder}'
|
| /Documentation/security/keys/ |
| D | core.rst | 767 requester's keyrings using the requester's security label, UID, GID and
|
| /Documentation/process/ |
| D | coding-style.rst | 344 '{initiator,requester} / {target,responder}'
|
| /Documentation/translations/sp_SP/process/ |
| D | coding-style.rst | 355 '{initiator,requester} / {target,responder}'
|
| /Documentation/power/ |
| D | pci.rst | 254 The PCI Express Requester ID of the device that sent the PME message is then
|