Searched full:services (Results 1 – 25 of 149) sorted by relevance
123456
| /Documentation/tee/ |
| D | ts-tee.rst | 4 TS-TEE (Trusted Services project)
7 This driver provides access to secure services implemented by Trusted Services.
9 Trusted Services [1] is a TrustedFirmware.org project that provides a framework
10 for developing and deploying device Root of Trust services in FF-A [2] S-EL0
16 Services RPC protocol is used [5]. To use the driver from user space a reference
17 implementation is provided at [6], which is part of the Trusted Services client
20 All Trusted Services (TS) SPs have the same FF-A UUID; it identifies the TS RPC
21 protocol. A TS SP can host one or more services (e.g. PSA Crypto, PSA ITS, etc).
33 services. Opening a service corresponds to opening a session in the given
36 Overview of a system with Trusted Services components::
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-qat | 24 Write to the file to change the configured services.
29 services
31 * dc: the device is configured for running compression services
35 services
37 services
39 crypto services and compression services
42 services and compression services
49 a device configured for running crypto services in order to
117 * dc: the ring pair is configured for running compression services
119 services
[all …]
|
| D | sysfs-firmware-efi-runtime-map | 4 Description: Switching efi runtime services to virtual mode requires
8 The efi runtime services can only be switched to virtual
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-sliced-vbi-cap.rst | 34 To find out which data services are supported by a sliced VBI capture or
57 - :cspan:`2` A set of all data services supported by the driver.
63 services the hardware can look for or insert into a particular
64 scan line. Data services are defined in :ref:`vbi-services`.
95 output per frame, or the number of services it can identify on a
127 .. _vbi-services:
129 .. flat-table:: Sliced VBI services
168 - :cspan:`2` Set of services applicable to 525 line systems.
171 - :cspan:`2` Set of services applicable to 625 line systems.
|
| D | dev-sliced-vbi.rst | 56 To find out which data services are supported by the hardware
63 services it can identify on a given line are limited. For example on PAL
67 To determine the currently selected services applications set the
82 all services may be supported by the hardware on all lines (this is
84 other services can only be inserted in one specific line). In many
86 to the required services and let the driver fill the ``service_lines``
127 array will be filled by the driver according to the services
137 services than requested, perhaps just one, if the hardware cannot
138 handle more services simultaneously. It may be empty (zero) if
139 none of the requested services are supported by the hardware.
[all …]
|
| /Documentation/virt/kvm/arm/ |
| D | fw-pseudo-registers.rst | 7 KVM handles the hypercall services as requested by the guests. New hypercall
8 services are regularly made available by the ARM specification or by KVM (as
9 vendor services) if they make sense from a virtualization point of view.
27 specification in order to provide services such as CPU on/off, reset
82 hypercall services in the form of a feature-bitmap to the userspace. This
83 bitmap is translated to the services that are available to the guest.
89 hypercall services via GET_ONE_REG. The user-space can write-back the
106 The bit represents the services offered under v1.0 of ARM True Random
|
| /Documentation/arch/x86/x86_64/ |
| D | uefi.rst | 28 If EFI runtime services are expected, the following configuration should
44 - If some or all EFI runtime services don't work, you can try following
46 services.
49 turn off all EFI runtime services
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-io.rst | 5 Dm-io provides synchronous and asynchronous I/O services. There are three
6 types of I/O services available, and each type has a sync and an async
58 Callers of the asynchronous I/O services must include the name of a completion
68 Before using any of the dm-io services, the user should call dm_io_get()
73 When the user is finished using the dm-io services, they should call
|
| /Documentation/devicetree/bindings/soc/microchip/ |
| D | microchip,mpfs-sys-controller.yaml | 14 which provides "services" to the main processor and to the FPGA fabric. These
15 services include hardware rng, reprogramming of the FPGA and verification of the
16 eNVM contents etc. More information on these services can be found online, at
|
| /Documentation/misc-devices/ |
| D | mrvl_cn10k_dpi.rst | 14 DPI PF function is an administrative function which services the mailbox
18 mrvl_cn10k_dpi.ko misc driver loads on DPI PF device and services the
50 how applications use mailbox and ioctl services from DPI PF kernel driver.
|
| /Documentation/usb/ |
| D | linux.inf | 45 ; DDInstal.Services section
46 [RNDIS.NT.5.1.Services]
48 needs = Usb_Rndis.ndi.Services
|
| /Documentation/devicetree/bindings/soc/bcm/ |
| D | brcm,bcm2835-vchiq.yaml | 7 title: Broadcom VCHIQ firmware services
14 to communicate with the VPU-side OS services.
|
| /Documentation/networking/device_drivers/ethernet/amd/ |
| D | pds_vdpa.rst | 18 services. It depends on the ``pds_core`` driver and hardware for the PF
19 and VF PCI handling as well as for device configuration services.
47 # Find the vDPA services/devices available
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,apr-services.yaml | 4 $id: http://devicetree.org/schemas/soc/qcom/qcom,apr-services.yaml#
7 title: Qualcomm APR/GPR services shared parts
|
| D | qcom,apr.yaml | 15 used for audio/voice services on the QDSP.
94 $ref: /schemas/soc/qcom/qcom,apr-services.yaml
97 APR/GPR static port services.
|
| /Documentation/scsi/ |
| D | bfa.rst | 41 http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page
58 http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page
76 http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page
92 http://www.brocade.com/services-support/index.page
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 12 Chapter 36. Coprocessor services
66 Coprocessor services
120 Device interrupt services). Sysino interrupts are not available for DAX devices.
128 Coprocessor services
176 Coprocessor services
228 Coprocessor services
284 Coprocessor services
342 Coprocessor services
397 Coprocessor services
454 Coprocessor services
[all …]
|
| /Documentation/ABI/removed/ |
| D | sysfs-firmware-efi-vars | 6 see 'Variable Services' in the UEFI specification
|
| /Documentation/driver-api/ |
| D | sm501.rst | 17 The core driver in drivers/mfd provides common services for the
18 drivers which manage the specific hardware blocks. These services
|
| /Documentation/devicetree/bindings/iio/afe/ |
| D | voltage-divider.yaml | 44 In addition to consuming the measurement services of a voltage
46 measurement services to other devices. This is particularly
|
| /Documentation/arch/powerpc/ |
| D | cxlflash.rst | 18 On Linux, Coherent Accelerator (CXL) kernel services present CAPI
50 by special translation services provided by the Flash AFU.
119 The block library can be thought of as a 'user' of services,
135 device (LUN) via user space access need to use the services provided
136 by the cxlflash driver. As these services are implemented as ioctls,
154 kernel services. These services specify a context id (u16) by which
156 services additionally provide a second file descriptor (herein
160 this driver and not the CXL kernel services to allow for intermediary
|
| /Documentation/virt/acrn/ |
| D | introduction.rst | 13 hypervisor services to the ACRN userspace.
38 ioctls to communicate with the HSM. HSM implements hypervisor services by
|
| /Documentation/admin-guide/media/ |
| D | faq.rst | 12 channel on this FAQ, and *services* for the logical channel.
45 The first step is to get a list of services that are transmitted.
60 to scan for services. So, you don't need to use an external
87 Once you have a transponders list, you need to generate a services
|
| /Documentation/networking/ |
| D | cdc_mbim.rst | 150 Custom device services
153 services. This is fully supported by the cdc_mbim driver.
155 Support for new MBIM services, including vendor specified services, is
159 New services should be registered in the MBIM Registry [5].
236 service. Userspace applications supporting specific MBIM DSS services
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,q6core.yaml | 14 - $ref: /schemas/soc/qcom/qcom,apr-services.yaml#
|
123456