Searched full:applied (Results 1 – 25 of 297) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/ |
| D | changesets.rst | 9 will be applied, or none of them will be. If an error occurs partway
12 applied.
14 When a changeset is applied, all of the changes get applied to the tree
31 entire changeset will get applied, or if there is an error the tree will
36 If a successfully applied changeset needs to be removed, it can be done
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-dac-ad5766 | 11 Inverts the dither applied to the selected DAC channel. Dither is not
24 Scales the dither before it is applied to the selected channel.
30 Selects dither source applied to the selected channel. Write "0" to
|
| D | sysfs-bus-iio-thermocouple | 6 is protected from excessive voltages applied to the thermocouple
|
| D | sysfs-kernel-mm-damon | 361 not be applied to.
367 of the scheme has tried to be applied.
373 action of the scheme has tried to be applied in bytes.
379 of the scheme has successfully applied.
385 action of the scheme has successfully applied in bytes.
398 to be applied.
405 tried to be applied.
412 tried to be applied.
419 tried to be applied.
426 to be applied.
|
| /Documentation/devicetree/bindings/firmware/ |
| D | nxp,imx95-scmi-pinctrl.yaml | 44 "mux_val" indicates the mux value to be applied.
46 "input_val" indicates the select input value to be applied.
48 "pad_setting" indicates the pad configuration value to be applied.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imxrt1170.yaml | 51 "mux_val" indicates the mux value to be applied.
53 "input_val" indicates the select input value to be applied.
55 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imxrt1050.yaml | 51 "mux_val" indicates the mux value to be applied.
53 "input_val" indicates the select input value to be applied.
55 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx8ulp-pinctrl.yaml | 48 "mux_mode" indicates the mux value to be applied.
50 "input_val" indicates the select input value to be applied.
52 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx8m-pinctrl.yaml | 55 "mux_val" indicates the mux value to be applied.
57 "input_val" indicates the select input value to be applied.
60 applied.
|
| D | fsl,imx9-pinctrl.yaml | 55 "mux_val" indicates the mux value to be applied.
57 "input_val" indicates the select input value to be applied.
59 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx7d-pinctrl.yaml | 59 "mux_val" indicates the mux value to be applied.
61 "input_val" indicates the select input value to be applied.
63 "pad_setting" indicates the pad configuration value to be applied.
|
| D | fsl,imx6ul-pinctrl.yaml | 55 "mux_val" indicates the mux value to be applied.
57 "input_val" indicates the select input value to be applied.
59 "pad_setting" indicates the pad configuration value to be applied:
|
| D | fsl,scu-pinctrl.yaml | 49 "mux_val" indicates the mux value to be applied.
51 "pad_setting" indicates the pad configuration value to be applied.
|
| D | samsung,pinctrl-pins-cfg.yaml | 39 The pin function selection that should be applied on the pins listed in the
41 of this property that should be applied to each of the pins listed in the
|
| /Documentation/arch/riscv/ |
| D | patch-acceptance.rst | 27 likely either requested changes, or expect it to be applied to another tree.
33 The exact commit to which a series has been applied will be noted on patchwork.
34 Patches for which any of the checks fail are unlikely to be applied and in most
|
| /Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 12 calls instead of the actual protection applied by the kernel.
23 check the actual protections being applied upon mmap/mprotect calls.
|
| /Documentation/process/ |
| D | applying-patches.rst | 16 one of the many trees/branches should be applied to. Hopefully this document
57 To revert a previously applied patch, use the -R argument to patch.
58 So, if you applied a patch like this::
134 it'll tell you about it by saying the patch applied with **fuzz**.
141 read this file to see exactly what change couldn't be applied, so you can
144 If you don't have any third-party patches applied to your kernel source, but
158 applied with ``-p0`` instead of ``-p1`` (reading the patch file should reveal if
174 patch could not be applied correctly and the patch program was unable to
179 If you get ``Reversed (or previously applied) patch detected! Assume -R? [n]``
183 If you actually did apply this patch previously and you just re-applied it
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 13 Another is support of stateless codecs, which require controls to be applied
30 applied when needed to get the expected result. Configuration values at the time
56 fact that the ioctl is part of said request, and is not to be applied
59 instead of being immediately applied, and buffers queued to a request do not
76 may synchronize so the requested pipeline's topology is applied before the
89 Controls can still be set without a request and are applied immediately,
134 be applied by the driver for the OUTPUT buffer, allowing user-space
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-rx.rst | 44 being broadcasted. RDS Radio Text can be applied when broadcaster
72 is applied to the broadcast to accentuate the high audio
84 - No de-emphasis is applied.
|
| D | ext-ctrls-fm-tx.rst | 51 applied when broadcaster wishes to transmit longer PS names,
151 filter is applied to the broadcast to accentuate the high audio
163 - No pre-emphasis is applied.
|
| /Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 51 The processor is vulnerable and no mitigations have been applied.
56 functionality to address the vulnerability has been applied.
60 The "Safe RET" mitigation (see below) has been applied to protect the
61 kernel, but the IBPB-extending microcode has not been applied. User
66 Extended IBPB functionality microcode patch has been applied. It does
151 an indirect branch prediction barrier after having applied the required
|
| D | vmscape.rst | 44 from a malicious guest. This is because Spectre-v2 mitigations are applied at
48 Vulnerability enumeration and mitigation is not applied inside a guest. This is
81 The processor is vulnerable and no mitigation has been applied.
|
| /Documentation/translations/ |
| D | index.rst | 45 applied to the English documents first. Afterwards and when possible, the
46 same change should be applied to translations. Translations' maintainers
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | upisemi,us5182.yaml | 37 applied when light > threshold.
44 applied when light < threshold.
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-v2-get-line-ioctl.rst | 87 be applied to lines with ``GPIO_V2_LINE_FLAG_INPUT`` set. When set, debounce
109 The approach applied depends on whether the feature can reasonably be emulated
112 The approach applied for each feature is as follows:
|
12345678910>>...12