| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
174 - :cspan:`2` Set of services applicable to 525 line systems.
177 - :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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/drivers/firmware/efi/ |
| D | riscv-runtime.c | 62 * Enable the UEFI Runtime Services if all prerequisites are in place, i.e.,
71 pr_info("EFI services will not be available.\n"); in riscv_enable_runtime_services()
109 pr_info("EFI runtime services will be disabled.\n"); in riscv_enable_runtime_services()
114 pr_info("EFI runtime services access via paravirt.\n"); in riscv_enable_runtime_services()
118 pr_info("Remapping and enabling EFI services.\n"); in riscv_enable_runtime_services()
121 pr_err("UEFI virtual mapping missing or invalid -- runtime services will not be available\n"); in riscv_enable_runtime_services()
125 /* Set up runtime services function pointers */ in riscv_enable_runtime_services()
|
| D | arm-runtime.c | 84 * Enable the UEFI Runtime Services if all prerequisites are in place, i.e.,
93 pr_info("EFI services will not be available.\n"); in arm_enable_runtime_services()
131 pr_info("EFI runtime services will be disabled.\n"); in arm_enable_runtime_services()
136 pr_info("EFI runtime services access via paravirt.\n"); in arm_enable_runtime_services()
140 pr_info("Remapping and enabling EFI services.\n"); in arm_enable_runtime_services()
143 pr_err("UEFI virtual mapping missing or invalid -- runtime services will not be available\n"); in arm_enable_runtime_services()
147 /* Set up runtime services function pointers */ in arm_enable_runtime_services()
|
| /kernel/linux/linux-6.6/drivers/firmware/efi/ |
| D | riscv-runtime.c | 62 * Enable the UEFI Runtime Services if all prerequisites are in place, i.e.,
71 pr_info("EFI services will not be available.\n"); in riscv_enable_runtime_services()
109 pr_info("EFI runtime services will be disabled.\n"); in riscv_enable_runtime_services()
114 pr_info("EFI runtime services access via paravirt.\n"); in riscv_enable_runtime_services()
118 pr_info("Remapping and enabling EFI services.\n"); in riscv_enable_runtime_services()
121 pr_err("UEFI virtual mapping missing or invalid -- runtime services will not be available\n"); in riscv_enable_runtime_services()
125 /* Set up runtime services function pointers */ in riscv_enable_runtime_services()
|
| D | arm-runtime.c | 84 * Enable the UEFI Runtime Services if all prerequisites are in place, i.e.,
93 pr_info("EFI services will not be available.\n"); in arm_enable_runtime_services()
131 pr_info("EFI runtime services will be disabled.\n"); in arm_enable_runtime_services()
136 pr_info("EFI runtime services access via paravirt.\n"); in arm_enable_runtime_services()
140 pr_info("Remapping and enabling EFI services.\n"); in arm_enable_runtime_services()
143 pr_err("UEFI virtual mapping missing or invalid -- runtime services will not be available\n"); in arm_enable_runtime_services()
147 /* Set up runtime services function pointers */ in arm_enable_runtime_services()
|
| /kernel/linux/linux-6.6/Documentation/virt/kvm/arm/ |
| D | hypercalls.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
|
| /kernel/linux/linux-5.10/drivers/pci/pcie/ |
| D | portdrv_core.c | 42 * services are enabled in "mask". Return the number of MSI/MSI-X vectors
158 * pcie_init_service_irqs - initialize irqs for PCI Express port services
209 int services = 0; in get_port_device_capability() local
213 services |= PCIE_PORT_SERVICE_HP; in get_port_device_capability()
226 services |= PCIE_PORT_SERVICE_AER; in get_port_device_capability()
243 services |= PCIE_PORT_SERVICE_PME; in get_port_device_capability()
259 (pcie_ports_dpc_native || (services & PCIE_PORT_SERVICE_AER))) in get_port_device_capability()
260 services |= PCIE_PORT_SERVICE_DPC; in get_port_device_capability()
268 services |= PCIE_PORT_SERVICE_BWNOTIF; in get_port_device_capability()
271 return services; in get_port_device_capability()
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/platform/efi/ |
| D | quirks.c | 227 * free to do whatever it wants with boot services code after
230 * services code (SetVirtualAddressMap). In order to work around such
231 * buggy implementations we reserve boot services region during EFI
235 * However, some boot services regions contain data that is required
276 pr_err("Could not allocate boot services memmap\n"); in efi_arch_mem_reserve()
283 pr_err("Failed to map new boot services memmap\n"); in efi_arch_mem_reserve()
345 * contain boot services code/data but is marked in efi_reserve_boot_services()
363 * Setting this bit for a boot services region really in efi_reserve_boot_services()
374 * Apart from having VA mappings for EFI boot services code/data regions,
386 * EFI runtime calls, hence don't unmap EFI boot services code/data in efi_unmap_pages()
[all …]
|
| /kernel/linux/linux-6.6/drivers/crypto/intel/qat/qat_common/ |
| D | adf_cfg_services.c | 27 char services[ADF_CFG_MAX_VAL_LEN_IN_BYTES] = {0}; in adf_get_service_enabled() local
31 ADF_SERVICES_ENABLED, services); in adf_get_service_enabled()
39 services); in adf_get_service_enabled()
43 services); in adf_get_service_enabled()
|
| /kernel/linux/linux-6.6/drivers/pci/pcie/ |
| D | portdrv.c | 53 * services are enabled in "mask". Return the number of MSI/MSI-X vectors
169 * pcie_init_service_irqs - initialize irqs for PCI Express port services
220 int services = 0; in get_port_device_capability() local
226 services |= PCIE_PORT_SERVICE_HP; in get_port_device_capability()
243 services |= PCIE_PORT_SERVICE_AER; in get_port_device_capability()
250 services |= PCIE_PORT_SERVICE_PME; in get_port_device_capability()
266 (pcie_ports_dpc_native || (services & PCIE_PORT_SERVICE_AER))) in get_port_device_capability()
267 services |= PCIE_PORT_SERVICE_DPC; in get_port_device_capability()
275 services |= PCIE_PORT_SERVICE_BWNOTIF; in get_port_device_capability()
278 return services; in get_port_device_capability()
[all …]
|
| /kernel/linux/linux-6.6/arch/x86/platform/efi/ |
| D | quirks.c | 235 * free to do whatever it wants with boot services code after
238 * services code (SetVirtualAddressMap). In order to work around such
239 * buggy implementations we reserve boot services region during EFI
243 * However, some boot services regions contain data that is required
284 pr_err("Could not allocate boot services memmap\n"); in efi_arch_mem_reserve()
291 pr_err("Failed to map new boot services memmap\n"); in efi_arch_mem_reserve()
353 * contain boot services code/data but is marked in efi_reserve_boot_services()
371 * Setting this bit for a boot services region really in efi_reserve_boot_services()
382 * Apart from having VA mappings for EFI boot services code/data regions,
394 * EFI runtime calls, hence don't unmap EFI boot services code/data in efi_unmap_pages()
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/Documentation/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/drivers/misc/mei/pxp/ |
| D | Kconfig | 6 tristate "Intel PXP services of ME Interface"
10 MEI Support for PXP Services on Intel platforms.
12 Enables the ME FW services required for PXP support through
|
| /kernel/linux/linux-5.10/drivers/misc/mei/hdcp/ |
| D | Kconfig | 6 tristate "Intel HDCP2.2 services of ME Interface"
10 MEI Support for HDCP2.2 Services on Intel platforms.
12 Enables the ME FW services required for HDCP2.2 support through
|
| /kernel/linux/linux-6.6/drivers/misc/mei/hdcp/ |
| D | Kconfig | 5 tristate "Intel HDCP2.2 services of ME Interface"
9 MEI Support for HDCP2.2 Services on Intel platforms.
11 Enables the ME FW services required for HDCP2.2 support through
|
| /kernel/linux/linux-6.6/drivers/misc/mei/gsc_proxy/ |
| D | Kconfig | 5 tristate "Intel GSC Proxy services of ME Interface"
9 MEI Support for GSC Proxy Services on Intel platforms.
12 Intel graphics card and services on CSE (MEI) firmware
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,apr.txt | 5 used for audio/voice services on the QDSP.
25 = APR SERVICES
29 - All APR services MUST contain the following property:
100 dependencies specified. Here some of the apr services are dependent on services
|
| /kernel/linux/linux-5.10/drivers/media/test-drivers/vidtv/ |
| D | vidtv_channel.c | 10 * Their services will be concatenated to populate the SDT.
206 /* Concatenate the services */ in vidtv_channel_sdt_serv_cat_into_new()
224 "No services found for channel %s\n", in vidtv_channel_sdt_serv_cat_into_new()
420 struct vidtv_psi_table_sdt_service *services = NULL; in vidtv_channel_si_init() local
435 services = vidtv_channel_sdt_serv_cat_into_new(m); in vidtv_channel_si_init()
436 if (!services) in vidtv_channel_si_init()
444 service_list = vidtv_channel_build_service_list(services); in vidtv_channel_si_init()
465 /* assemble all services and assign to SDT */ in vidtv_channel_si_init()
466 vidtv_psi_sdt_service_assign(m->si.sdt, services); in vidtv_channel_si_init()
493 vidtv_psi_sdt_service_destroy(services); in vidtv_channel_si_init()
|