Searched refs:validation (Results 1 – 25 of 77) sorted by relevance
1234
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | evm | 23 0 Enable HMAC validation and creation
24 1 Enable digital signature validation
26 runtime. Not supported if HMAC validation and
35 will enable HMAC validation and creation
41 will enable HMAC and digital signature validation and
48 will enable digital signature validation, permit
|
| D | sysfs-bus-thunderbolt | 199 - Writing "2" will run some basic validation on the image
302 - Writing "2" will run some basic validation on the image
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | sht15.rst | 57 * If a CRC validation fails, a soft reset command is sent, which resets
65 set it to true to enable CRC validation of the readings (default to false).
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 253 control, or the validation step failed (see below), then
257 Before controls are read from/written to hardware a validation
270 came from the validation step (meaning that the hardware was not
275 ``error_idx`` to ``count`` if the validation failed. This has the
277 control failed the validation. If the validation was successful
284 also no need to handle the validation step in this special way, so
286 validation step instead of to ``count``. This means that if
289 actual control that failed the validation step. Unfortunately,
|
| /Linux-v5.10/Documentation/devicetree/ |
| D | writing-schema.rst | 83 validation of DT files.
96 validation. There are currently 2 transformations the tools perform.
145 In order to perform validation of DT source files, use the ``dtbs_check`` target::
150 necessary to use ``dt_binding_check`` to get all the validation errors in the
|
| /Linux-v5.10/Documentation/x86/ |
| D | orc-unwinder.rst | 18 stack metadata validation (CONFIG_STACK_VALIDATION). After analyzing
94 stack metadata validation feature, objtool already follows all code
97 validation to ORC data generation.
142 stack metadata validation feature, which is described in detail in
143 tools/objtool/Documentation/stack-validation.txt. After analyzing all
|
| /Linux-v5.10/scripts/dtc/ |
| D | Makefile | 16 $(error dtc needs libyaml for DT schema validation support. \
|
| /Linux-v5.10/tools/perf/Documentation/ |
| D | perf-buildid-list.txt | 32 Don't do ownership validation.
|
| D | perf-kmem.txt | 30 Don't do ownership validation
|
| D | perf-mem.txt | 37 Don't do ownership validation
|
| D | perf-annotate.txt | 36 Don't do ownership validation.
|
| /Linux-v5.10/drivers/gpu/drm/amd/pm/inc/ |
| D | power_state.h | 156 struct PP_StateValidationBlock validation; member
|
| /Linux-v5.10/tools/objtool/Documentation/ |
| D | stack-validation.txt | 1 Compile-time stack metadata validation
28 Why do we need stack metadata validation?
119 To achieve the validation, objtool enforces the following rules:
345 - To skip validation of a function, use the STACK_FRAME_NON_STANDARD
348 - To skip validation of a file, add
354 - To skip validation of a directory, add
|
| /Linux-v5.10/Documentation/leds/ |
| D | leds-class.rst | 102 meets the requirements pointed out here. It performs validation of the LED class
104 the validation fails for it. So far the script supports validation
|
| /Linux-v5.10/Documentation/gpu/ |
| D | vc4.rst | 68 V3D binner command list (BCL) validation
|
| /Linux-v5.10/sound/usb/ |
| D | clock.c | 593 goto validation; in set_sample_rate_v2v3()
650 validation: in set_sample_rate_v2v3()
|
| /Linux-v5.10/Documentation/security/tpm/ |
| D | tpm_event_log.rst | 28 contents. The PCR contents are used to provide the validation of the
|
| /Linux-v5.10/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 43 excluded from the irq-tracing [and lock validation] mechanism via
|
| /Linux-v5.10/Documentation/driver-api/media/ |
| D | mc-core.rst | 247 Link validation
250 Link validation is performed by :c:func:`media_pipeline_start()`
258 Subsystems should facilitate link validation by providing subsystem specific
|
| /Linux-v5.10/Documentation/networking/ |
| D | vxlan.rst | 72 perform protocol-aware offloads, like checksum validation offload of
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| D | submitting-patches.rst | 23 vocabulary and YAML file format. The DT binding files must pass validation
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 81 integrity check, and this is done by adding CRC32c validation to the metadata
112 owner field in the metadata object, we can immediately do top down validation to
162 body, but in general most of the per-field validation is handled by the
178 object specific metadata validation. If any of these checks fail, then the
|
| D | mount_api.rst | 54 parameter description for validation at registration time and querying by a
387 the parameter parsing and validation hooks.
737 struct as this will provide validation on registration (if
783 This performs some validation checks on a parameter description. It
785 log errors to dmesg if validation fails.
|
| /Linux-v5.10/tools/testing/selftests/tc-testing/creating-plugins/ |
| D | AddingPlugins.txt | 100 The check_args method is so that the plugin can do validation on
|
| /Linux-v5.10/kernel/time/ |
| D | Kconfig | 20 # Clocksources require validation of the clocksource against the last
|
1234
