Searched full:service (Results 1 – 25 of 250) sorted by relevance
12345678910
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,apr-services.yaml | 13 Common parts of a static service in Qualcomm APR/GPR (Asynchronous/Generic
21 APR Service ID
22 3 = DSP Core Service
23 4 = Audio Front End Service.
24 5 = Voice Stream Manager Service.
26 7 = Audio Stream Manager Service.
27 8 = Audio Device Manager Service.
33 GPR Service ID
34 1 = Audio Process Manager Service
35 2 = Proxy Resource Manager Service.
[all …]
|
| D | qcom,apr.yaml | 92 "^service@[1-9a-d]$":
158 q6core: service@3 {
164 service@4 {
195 service@1 {
|
| /Documentation/PCI/ |
| D | pciebus-howto.rst | 15 and provides information on how to enable the service drivers to
38 and handled by corresponding service drivers.
46 services. To maintain a clean and simple solution each service
47 may have its own software service driver. In this case several
48 service drivers will compete for a single PCI-PCI Bridge device.
49 For example, if the PCI Express Root Port native hotplug service
51 kernel therefore does not load other service drivers for that Root
52 Port. In other words, it is impossible to have multiple service
56 To enable multiple service drivers running simultaneously requires
58 PCI Express Ports and distributes all provided service requests
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-service-time.rst | 2 dm-service-time
5 dm-service-time is a path selector module for device-mapper targets,
6 which selects a path with the shortest estimated service time for
9 The service time for each path is estimated by dividing the total size
14 The path selector name is 'service-time'.
49 dm-service-time adds the I/O size to 'in-flight-size' when the I/O is
51 Basically, dm-service-time selects a path having minimum service time
69 If such optimizations can't be applied, calculate service time, and
70 compare service time.
71 If calculated service time is equal, the path having maximum
[all …]
|
| D | dm-io.rst | 22 The first I/O service type takes a list of memory pages as the data buffer for
37 The second I/O service type takes an array of bio vectors as the data buffer
38 for the I/O. This service can be handy if the caller has a pre-assembled bio,
48 The third I/O service type takes a pointer to a vmalloc'd memory buffer as the
49 data buffer for the I/O. This service can be handy if the caller needs to do
|
| /Documentation/ABI/testing/ |
| D | configfs-tsm | 102 supports the concept of attestation reports from a service
104 Specifying the service provider via this attribute will create
105 an attestation report as specified by the service provider.
106 The only currently supported service provider is "svsm".
108 For the "svsm" service provider, see the Secure VM Service Module
110 "site:amd.com "Secure VM Service Module for SEV-SNP
119 supports the concept of attestation reports from a service
122 requests all active services within the service provider be
124 an attestation report of just the specified service using the
129 service guid.
[all …]
|
| D | debugfs-driver-qat_telemetry | 129 service_type service associated to the RP
192 The service provided on a ring-pair varies depending on the
201 PCI BDF/VF RP0/service RP1/service RP2/service RP3/service
216 PCI BDF/VF RP0/service RP1/service RP2/service RP3/service
224 The mapping of a RP to a service can be retrieved using
|
| D | sysfs-driver-qat_rl | 49 Selected ring pairs must to be assigned to a single service,
50 i.e. the one provided with the srv attribute. The service
114 throughput for a selected service.
179 (RW) Service (SRV). Represents the service (sym, asym, dc)
183 an SLA. After an SLA is configured, reports the service
213 particular service/sla. This is the remaining value that a new
|
| D | sysfs-bus-thunderbolt | 246 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/key
251 service exposes. This entry describes the protocol in
261 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/modalias
266 the XDomain service. Format: tbtsvc:kSpNvNrN
268 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/prtcid
273 service supports.
275 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/prtcvers
280 service supports.
282 What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/prtcrevs
287 service supports.
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | intel,stratix10-svc.txt | 1 Intel Service Layer Driver for Stratix10 SoC
13 service from SDM.
15 Intel Stratix10 service layer driver, running at privileged exception level
16 (EL1, Exception Layer 1), interfaces with the service providers and provides
17 the services for FPGA configuration, QSPI, Crypto and warm reset. Service layer
|
| /Documentation/networking/ |
| D | tipc.rst | 20 - Cluster wide IPC service
29 Welcome to the Transparent Inter Process Communication service, TIPC in short,
32 - Service Addressing
34 A fundamental concept in TIPC is that of Service Addressing which makes it
38 - Service Tracking
40 A client wanting to wait for the availability of a server, uses the Service
42 sockets with the associated service address.
44 The service tracking mechanism can also be used for Cluster Topology Tracking,
47 Likewise, the service tracking mechanism can be used for Cluster Connectivity
53 Using a service address, a client can send datagram messages to a server socket.
[all …]
|
| D | rxrpc.rst | 102 (#) Each connection goes to a particular "service". A connection may not go
103 to multiple services. A service may be considered the RxRPC equivalent of
111 local transport endpoint and one service on one remote endpoint. An RxRPC
120 Service ID
127 which the service receives; then the service transmits the reply data
135 (#) The first four bytes of the request data are the service operation ID.
175 make multiple simultaneous calls to the same service. One server socket
209 non-zero service ID.
412 This is used to make a client call to probe if the specified service ID
414 recvmsg() for the service ID actually in use. The operation probed must
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | hisilicon-hns-nic.txt | 22 debug service
32 | | service| port(2)
43 In NIC mode of DSAF, all 6 PHYs of service DSAF are taken as ethernet ports
49 debug debug service
53 In Switch mode of DSAF, all 6 PHYs of service DSAF are taken as physical
60 | | service| port(0)
|
| /Documentation/virt/kvm/arm/ |
| D | fw-pseudo-registers.rst | 13 is tied to a particular version of a hypercall service, or if a migration
84 There is a register defined per service call owner and can be accessed via
101 Controls the bitmap of the ARM Standard Secure Service Calls.
110 Controls the bitmap of the ARM Standard Hypervisor Service Calls.
115 The bit represents the Paravirtualized Time service as represented by
119 Controls the bitmap of the Vendor specific Hypervisor Service Calls.
128 The bit represents the Precision Time Protocol KVM service.
|
| /Documentation/virt/acrn/ |
| D | introduction.rst | 7 hardware. It has a privileged management VM, called Service VM, to manage User
10 ACRN userspace is an application running in the Service VM that emulates
12 Service Module (HSM) is a kernel module in the Service VM which provides
19 Service VM User VM
|
| D | io-request.rst | 7 distributed by the ACRN Hypervisor Service Module to an I/O client
15 communication between the hypervisor and Service VM. An I/O request is a
18 VM. ACRN userspace in the Service VM first allocates a 4-KByte page and passes
39 | Service VM |
90 the Service VM.
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 13 Log entries may be purged by the service processor
19 the service processor needs more room for log entries,
26 The service processor may be able to store more log
57 the service processor, if applicable).
|
| /Documentation/tee/ |
| D | ts-tee.rst | 22 A service is identified by its service UUID; the same type of service cannot be
23 present twice in the same SP. During SP boot each service in the SP is assigned
33 services. Opening a service corresponds to opening a session in the given
67 [5] https://trusted-services.readthedocs.io/en/v1.0.0/developer/service-access-protocols.html#abi
|
| /Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | dpio-driver.rst | 43 DPIO service-- provides APIs to other Linux drivers for services
51 |DPIO obj| |DPIO service|
78 | (DPRC) | . . |DPIO obj| |DPIO service|
105 registers the probed DPIO with dpio-service.
107 DPIO service (dpio-service.c, dpaa2-io.h)
110 The dpio service component provides queuing, notification, and buffers
153 only used by dpio-service.
|
| /Documentation/block/ |
| D | bfq-iosched.rst | 70 4-1 Service guarantees provided
133 guarantees by a simple formula. If not configured for strict service
140 Most benefits for server systems follow from the same service
165 (process) at a time, and implements this service model by
173 - The in-service queue is expired, i.e., its service is suspended,
193 - With respect to idling for service guarantees, if several
203 only when strictly needed for service guarantees, i.e., for
206 provide both strong service guarantees and optimal throughput
244 perfectly fair, and smooth service. In particular, B-WF2Q+
255 deviation with respect to an ideal service is proportional to
[all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ibm,occ-hwmon.yaml | 7 title: IBM On-Chip Controller (OCC) accessed from a service processor
14 thermals for the system. A service processor or baseboard management
|
| /Documentation/scsi/ |
| D | ufs.rst | 87 the higher layers through Service Access Points. UTP defines 3
88 service access points for higher layers.
90 * UDM_SAP: Device manager service access point is exposed to device
93 * UTP_CMD_SAP: Command service access point is exposed to UFS command
95 * UTP_TM_SAP: Task management service access point is exposed to task
105 MIPI UniPro and MIPI M-PHY. UIC provides 2 service access points
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-rx.rst | 31 Gets the Programme Service name (PS_NAME). It is intended for
33 programme service identification and selection. In Annex E of
35 description of the correct character encoding for Programme Service
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,sc8180x-pas.yaml | 7 title: Qualcomm SC8180X Peripheral Authentication Service
13 Qualcomm SC8180X SoC Peripheral Authentication Service loads and boots
|
| D | qcom,pas-common.yaml | 7 title: Qualcomm Peripheral Authentication Service Common Properties
13 Common properties of Qualcomm SoCs Peripheral Authentication Service.
|
12345678910