Searched full:inbound (Results 1 – 25 of 34) sorted by relevance
12
| /Documentation/scsi/ |
| D | hptiop.rst | 23 0x10 Inbound Message Register 0
24 0x14 Inbound Message Register 1
27 0x20 Inbound Doorbell Register
28 0x24 Inbound Interrupt Status Register
29 0x28 Inbound Interrupt Mask Register
32 0x40 Inbound Queue Port
41 0x10 Inbound Message Register 0
42 0x14 Inbound Message Register 1
45 0x20 Inbound Doorbell Register
46 0x24 Inbound Interrupt Status Register
[all …]
|
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 90 state value into two parts (the "cluster" state and "inbound" state) and
222 as seen by a CPU tearing the cluster down. The "inbound side" is the
237 "inbound" state: The state of the cluster on the inbound side.
266 Transitions ===##> can only be made by the inbound CPU, and only
267 involve changes to the "inbound" state, except where there is no
280 The parallelism of the inbound and outbound CPUs is observed by
296 <cluster state>/<inbound state> (<transitioner>)
299 can occur; either the inbound or the outbound side.
304 CLUSTER_DOWN/INBOUND_COMING_UP (inbound)
317 In this state, an inbound CPU sets up the cluster, including
[all …]
|
| /Documentation/networking/ |
| D | xfrm_proc.rst | 19 Inbound errors
33 i.e. Either inbound SPI, address, or IPsec protocol at SA is wrong
58 e.g. Inbound SAs are correct but SP rule is wrong
62 e.g. Inbound SAs are correct but no SP is found
|
| D | secid.rst | 19 If this is an inbound flow, the label is derived from the IPSec security
|
| D | xfrm_sync.rst | 36 - the replay sequence for both inbound and outbound
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smp2p.yaml | 61 Two identifiers of the inbound and outbound smem items used for this edge.
67 Each SMP2P pair contain a set of inbound and outbound entries, these are
74 Marks the entry as inbound; the node should be specified as a two
84 The name of this entry, for inbound entries this will be used to
124 # inbound and one outbound entry.
|
| /Documentation/devicetree/bindings/pci/ |
| D | mobiveil-pcie.txt | 4 has up to 8 outbound and inbound windows for the address translation.
25 - ppio-wins : number of requested ppio inbound windows
26 default 1 inbound memory window is configured.
|
| D | cdns-pcie-host.yaml | 28 significant bits kept during inbound (PCIe -> AXI) address translations
|
| D | xgene-pci.txt | 15 - dma-ranges: ranges for the inbound memory regions.
|
| D | v3-v360epc-pci.txt | 21 - dma-ranges: three ranges for the inbound memory region. The ranges must
|
| D | ti-pci.txt | 52 - num-ib-windows : number of inbound address translation windows
|
| D | renesas,pci-rcar-gen2.yaml | 66 A single range for the inbound memory region. If not supplied,
|
| D | faraday,ftpci100.yaml | 83 three ranges for the inbound memory region. The ranges must
|
| /Documentation/trace/ |
| D | hisi-ptt.rst | 99 type. Rx means the inbound while Tx means outbound. The packets will
132 direction of inbound and traced data format of 8DW.
177 You can specify multiple types when tracing inbound TLP headers, but can only
185 This is optional and the default parameter is inbound. The parameter value
189 - 4'b0000: inbound TLPs (P, NP, CPL)
191 - 4'b0010: outbound TLPs (P, NP, CPL) and inbound TLPs (P, NP, CPL B)
192 - 4'b0011: outbound TLPs (P, NP, CPL) and inbound TLPs (CPL A)
199 - 4'b0010: inbound TLPs (P, NP, CPL B)
200 - 4'b0011: inbound TLPs (CPL A)
202 Inbound completions are classified into two types:
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-rpmsg | 23 inbound messages arrive to this address, the rpmsg core
41 inbound messages arrive to this address, the rpmsg core
49 and it is listening for inbound messages that may be sent
|
| D | sysfs-bus-event_source-devices-hisi_ptt | 45 Description: (RW) Control the allocated buffer watermark for inbound packets.
|
| /Documentation/driver-api/rapidio/ |
| D | tsi721.rst | 9 It supports maintenance read and write operations, inbound and outbound RapidIO
10 doorbells, inbound maintenance port-writes and RapidIO messaging.
17 For inbound messages this driver uses destination ID matching to forward messages
|
| D | mport_cdev.rst | 46 - Configure/Map mport's inbound requests window(s) for specific size,
|
| /Documentation/ABI/stable/ |
| D | firewire-cdev | 42 link layers, reception of inbound requests to such
44 to inbound requests
|
| D | sysfs-bus-vmbus | 160 Description: Number of guest to host interrupts caused by the inbound ring
|
| /Documentation/staging/ |
| D | rpmsg.rst | 60 a unique rpmsg local address (a 32-bit integer). This way when inbound messages
63 with the payload of the inbound message).
204 inbound messages arrive, they are dispatched by the rpmsg bus using the
218 relevant inbound messages arrive (i.e. messages which their dst address
|
| /Documentation/netlabel/ |
| D | cipso_ipv4.rst | 31 Inbound Packet Processing
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-enum-entities.rst | 103 - Total number of outbound links. Inbound links are not counted in
|
| /Documentation/driver-api/ |
| D | ntb.rst | 42 inbound translation configured on the local ntb port and outbound translation
46 Inbound translation:
|
| /Documentation/PCI/ |
| D | boot-interrupts.rst | 12 On PCI Express, interrupts are represented with either MSI or inbound
|
12