| /linux-6.14.4/Documentation/hwmon/ |
| D | isl68137.rst | 25 Publicly available (after August 2020 launch) at the Renesas website
35 Publicly available (after August 2020 launch) at the Renesas website
45 Publicly available (after August 2020 launch) at the Renesas website
55 Publicly available (after August 2020 launch) at the Renesas website
65 Publicly available (after August 2020 launch) at the Renesas website
75 Publicly available (after August 2020 launch) at the Renesas website
85 Publicly available (after August 2020 launch) at the Renesas website
95 Publicly available (after August 2020 launch) at the Renesas website
105 Publicly available (after August 2020 launch) at the Renesas website
115 Publicly available (after August 2020 launch) at the Renesas website
[all …]
|
| /linux-6.14.4/Documentation/networking/ |
| D | xsk-tx-metadata.rst | 54 packet for transmission at a pre-determined time called launch time. The
55 value of launch time is indicated by ``launch_time`` field of
72 Launch Time
75 The value of the requested launch time should be based on the device's PTP
81 packet reordering, a packet with a launch time request will block other
86 In scenarios where the launch time offload feature is disabled, the device
87 driver is expected to disregard the launch time request. For correct
88 interpretation and meaningful operation, the launch time should never be
91 launch time offload feature.
96 For stmmac, TSO and launch time (TBS) features are mutually exclusive for
[all …]
|
| /linux-6.14.4/arch/mips/include/asm/sn/ |
| D | launch.h | 16 * The launch data structure resides at a fixed place in each node's memory
20 * The master stores launch parameters in the launch structure
26 * There is an array of launch structures, one per CPU on the node. One
52 * The launch routine is called only if the complement address is correct.
82 * PROM entry points for launch routines are determined by IPxxprom/start.s
|
| D | nmi.h | 16 * The launch data structure resides at a fixed place in each node's memory
20 * The master stores launch parameters in the launch structure
27 * There is an array of launch structures, one per CPU on the node. One
|
| /linux-6.14.4/drivers/md/dm-vdo/ |
| D | completion.h | 48 * vdo_launch_completion() - Launch a completion with default priority.
102 * vdo_launch_completion_callback() - Set the callback for a completion and launch it immediately.
113 * vdo_prepare_completion() - Prepare a completion for launch.
129 * vdo_prepare_completion_for_requeue() - Prepare a completion for launch ensuring that it will
|
| /linux-6.14.4/drivers/staging/media/atomisp/ |
| D | TODO | 58 gst-launch-1.0 v4l2src ! videoconvert ! xvimagesink sync=false
62 gst-launch-1.0 v4l2src ! video/x-raw,format=YV12,width=640,height=480 ! \
67 gst-launch-1.0 v4l2src ! video/x-raw,format=YV12,width=640,height=480 ! \
|
| /linux-6.14.4/include/uapi/linux/ |
| D | if_xdp.h | 130 /* Request launch time hardware offload. The device will schedule the packet for
131 * transmission at a pre-determined time called launch time. The value of
132 * launch time is communicated via launch_time field of struct xsk_tx_metadata.
153 /* Launch time in nanosecond against the PTP HW Clock */
|
| /linux-6.14.4/tools/include/uapi/linux/ |
| D | if_xdp.h | 130 /* Request launch time hardware offload. The device will schedule the packet for
131 * transmission at a pre-determined time called launch time. The value of
132 * launch time is communicated via launch_time field of struct xsk_tx_metadata.
153 /* Launch time in nanosecond against the PTP HW Clock */
|
| /linux-6.14.4/Documentation/arch/x86/ |
| D | intel_txt.rst | 47 uses Intel TXT to perform a measured and verified launch of an OS
83 pre-launch components can be removed from the trust chain, DMA
105 incorrect), it will directly launch the kernel with no changes
126 - Tboot then applies an (optional) user-defined launch policy to
140 - As part of its launch, tboot DMA protects all of RAM (using the
160 launch, TXT must first be exited. This is to prevent attacks that
|
| D | sgx.rst | 167 Launch Control
170 SGX provides a launch control mechanism. After all enclave pages have been
181 kernel on launch control policy. Before calling EINIT function, the driver sets
|
| /linux-6.14.4/Documentation/security/secrets/ |
| D | coco.rst | 18 secret injection is performed early in the VM launch process, before the
35 During the VM's launch, the virtual machine manager may inject a secret to that
68 to which an EFI secret area with 4 secrets was injected during launch::
|
| /linux-6.14.4/tools/perf/pmu-events/arch/riscv/thead/c900-legacy/ |
| D | microarch.json | 10 "BriefDescription": "Instruction decode unit launch pipeline failed in RF state"
15 "BriefDescription": "Instruction decode unit launch register file fail in RF state"
|
| /linux-6.14.4/arch/x86/kernel/cpu/ |
| D | feat_ctl.c | 134 * use it. This happens if flexible Launch Control is not in init_ia32_feat_ctl()
207 pr_err_once("SGX Launch Control is locked. Disable SGX.\n"); in init_ia32_feat_ctl()
210 pr_err_once("SGX Launch Control is locked. Support SGX virtualization only.\n"); in init_ia32_feat_ctl()
|
| /linux-6.14.4/arch/x86/kvm/vmx/ |
| D | sgx.c | 406 * Use Intel's default value for Skylake hardware if Launch Control is in setup_default_sgx_lepubkeyhash()
408 * Launch Control is supported and enabled, i.e. mimic the reset value in setup_default_sgx_lepubkeyhash()
409 * and let the guest write the MSRs at will. If Launch Control is in setup_default_sgx_lepubkeyhash()
494 * Trap and execute EINIT if launch control is enabled in the in vmx_write_encls_bitmap()
495 * host using the guest's values for launch control MSRs, even in vmx_write_encls_bitmap()
|
| /linux-6.14.4/arch/mips/sgi-ip30/ |
| D | ip30-smp.c | 37 void *launch; member
123 mpc->launch = smp_bootstrap; in ip30_smp_boot_secondary()
|
| /linux-6.14.4/tools/testing/selftests/landlock/ |
| D | .gitignore | 2 /sandbox-and-launch
|
| D | Makefile | 13 TEST_GEN_PROGS_EXTENDED := true sandbox-and-launch wait-pipe
|
| /linux-6.14.4/arch/mips/sgi-ip27/ |
| D | ip27-smp.c | 23 #include <asm/sn/launch.h>
143 * Launch a slave into smp_bootstrap(). It doesn't take an argument, and we
|
| /linux-6.14.4/arch/hexagon/kernel/ |
| D | process.c | 21 * Program thread launch. Often defined as a macro in processor.h,
25 * The Hexagon ABI specifies that R28 is zero'ed before program launch,
|
| /linux-6.14.4/drivers/media/tuners/ |
| D | tda18271-common.c | 430 /* launch detector */ in tda18271_init_regs()
442 /* launch optimization algorithm */ in tda18271_init_regs()
457 /* launch detector */ in tda18271_init_regs()
469 /* launch optimization algorithm */ in tda18271_init_regs()
485 /* launch detector */ in tda18271_init_regs()
496 /* launch optimization algorithm */ in tda18271_init_regs()
|
| /linux-6.14.4/tools/perf/tests/shell/ |
| D | stat_metrics_values.sh | 17 echo "Launch python validation script $pythonvalidator"
|
| /linux-6.14.4/drivers/platform/x86/ |
| D | quickstart.c | 3 * ACPI Direct App Launch driver
244 MODULE_DESCRIPTION("ACPI Direct App Launch driver");
|
| /linux-6.14.4/tools/testing/selftests/net/rds/ |
| D | README.txt | 37 # launch the tests in a VM
|
| /linux-6.14.4/include/xen/interface/ |
| D | elfnote.h | 192 * 32bit entry point into the kernel. When requested to launch the
194 * launch the guest in 32bit protected mode with paging disabled.
|
| /linux-6.14.4/tools/testing/selftests/riscv/vector/ |
| D | v_helpers.c | 46 /* launch the program again to check inherit */ in launch_test()
|