| /linux-6.15/scripts/gcc-plugins/ |
| H A D | arm_ssp_per_task_plugin.c | 51 static bool no(void) in no() function
58 targetm.have_stack_protect_combined_set = no; in arm_pertask_ssp_start_unit()
59 targetm.have_stack_protect_combined_test = no; in arm_pertask_ssp_start_unit()
77 if (!strcmp(argv[i].key, "disable")) in plugin_init()
83 plugin_name, argv[i].key); in plugin_init()
87 if (!strcmp(argv[i].key, "offset")) { in plugin_init()
92 plugin_name, argv[i].key); in plugin_init()
|
| /linux-6.15/Documentation/staging/ |
| H A D | static-keys.rst | 19 DEFINE_STATIC_KEY_TRUE(key);
62 tracepoints are often dormant (disabled) and provide no direct kernel
86 consist of a single atomic 'no-op' instruction (5 bytes on x86), in the
88 'no-op' in the straight-line codepath with a 'jump' instruction to the
170 you really know that you're in the above context, and no other.
184 to take advantage of this optimization. If there is no architecture support, we
273 vs. the jump label case just has a 'no-op' or 'jmp 0'. (The jmp 0, is patched
274 to a 5 byte atomic no-op instruction at boot-time.) Thus, the disabled jump
282 footprint. We can in fact improve this even further, since the 5-byte no-op
283 really can be a 2-byte no-op since we can reach the branch with a 2-byte jmp.
[all …]
|
| /linux-6.15/Documentation/devicetree/bindings/input/ |
| H A D | samsung,s3c6410-keypad.yaml | 12 A key can be placed at each intersection of a unique row and a unique column.
13 The keypad controller can sense a key-press and key-release and report the
40 linux,input-no-autorepeat:
43 Do no enable autorepeat feature.
60 '^key-[0-9a-z]+$':
65 Each key connected to the keypad controller is represented as a child
71 description: The column number to which the key is connected.
75 description: The row number to which the key is connected.
107 linux,input-no-autorepeat;
110 key-1 {
[all …]
|
| H A D | omap-keypad.txt | 5 A key can be placed at each intersection of a unique row and a unique column.
6 The keypad controller can sense a key-press and key-release and report the
20 - linux,keypad-no-autorepeat: do no enable autorepeat feature.
27 linux,keypad-no-autorepeat;
|
| H A D | adc-keys.yaml | 38 Each button (key) is represented as a sub-node.
47 Voltage above or equal to which this key is considered pressed. No
68 // | 2.000.000 <= value | no key pressed |
76 // | value < 500.000 | no key pressed |
|
| /linux-6.15/arch/arm64/boot/dts/exynos/ |
| H A D | exynos990-x1s-common.dtsi | 37 no-map;
42 no-map;
52 power-key {
59 voldown-key {
65 volup-key {
78 key_power: key-power-pins {
85 key_voldown: key-voldown-pins {
92 key_volup: key-volup-pins {
|
| H A D | exynos990-c1s.dts | 54 no-map;
59 no-map;
69 power-key {
76 voldown-key {
82 volup-key {
95 key_power: key-power-pins {
102 key_voldown: key-voldown-pins {
109 key_volup: key-volup-pins {
|
| H A D | exynos990-r8s.dts | 54 no-map;
59 no-map;
69 power-key {
76 voldown-key {
82 volup-key {
95 key_power: key-power-pins {
102 key_voldown: key-voldown-pins {
109 key_volup: key-volup-pins {
|
| H A D | exynos9810-starlte.dts | 40 power-key {
47 voldown-key {
53 volup-key {
60 wink-key {
82 no-map;
92 key_power: key-power-pins {
99 key_voldown: key-voldown-pins {
106 key_volup: key-volup-pins {
113 key_wink: key-wink-pins {
|
| /linux-6.15/arch/arm/boot/dts/qcom/ |
| H A D | qcom-msm8926-htc-memul.dts | 26 key-power {
33 key-volume-down {
40 key-volume-up {
51 no-map;
56 no-map;
61 no-map;
66 no-map;
71 no-map;
76 no-map;
81 no-map;
[all …]
|
| H A D | qcom-msm8226-samsung-matisse-common.dtsi | 55 key-home {
62 key-volume-down {
69 key-volume-up {
145 no-map;
150 no-map;
155 no-map;
160 no-map;
165 no-map;
170 no-map;
175 no-map;
[all …]
|
| H A D | qcom-apq8026-samsung-milletwifi.dts | 63 key-home {
70 key-volume-down {
77 key-volume-up {
183 no-map;
188 no-map;
193 no-map;
198 no-map;
203 no-map;
208 no-map;
213 no-map;
[all …]
|
| /linux-6.15/arch/arm/boot/dts/nxp/imx/ |
| H A D | imx6dl-prtmvt.dts | 61 key-f1 {
67 key-f2 {
73 key-f3 {
79 key-f4 {
85 key-f5 {
589 no-1-8-v;
592 no-mmc;
593 no-sdio;
601 no-1-8-v;
603 no-sd;
[all …]
|
| /linux-6.15/arch/arm64/boot/dts/freescale/ |
| H A D | imx93-var-som-symphony.dts | 72 no-map;
77 no-map;
82 no-map;
87 no-map;
92 no-map;
98 no-map;
104 no-map;
111 key-back {
117 key-home {
123 key-menu {
[all …]
|
| /linux-6.15/arch/arm/boot/dts/samsung/ |
| H A D | s5pv210-smdkv210.dts | 48 davicom,no-eeprom;
74 linux,input-no-autorepeat;
87 key-1 {
93 key-2 {
99 key-3 {
105 key-4 {
111 key-5 {
118 key-6 {
123 key-7 {
129 key-8 {
[all …]
|
| H A D | exynos4412-smdk4412.dts | 72 linux,input-no-autorepeat;
78 key-1 {
84 key-2 {
90 key-3 {
96 key-4 {
102 key-5 {
108 key-a {
114 key-b {
120 key-c {
126 key-d {
[all …]
|
| /linux-6.15/Documentation/networking/ |
| H A D | tcp_ao.rst | 85 to ensure that no one uses such MKT before trying to remove it.
89 A: It can, it's a key management task to decide when to remove an old key [6.1]::
93 to be removed. TCP-AO provides no mechanism to coordinate their removal,
99 when it is no longer considered permitted.
108 still requesting it. There are no guarantees for force-delete as the peer
112 Q: What happens when a packet is received on a new connection with no known
123 i. If there is no matching MKT, remove TCP-AO from the segment.
151 key changes is [7.3]::
159 A: It should not, no action needs to be performed [7.5.2.e]::
164 is not available, no action is required (RNextKeyID of a received
[all …]
|
| /linux-6.15/Documentation/crypto/ |
| H A D | api-samples.rst | 22 u8 key[64]; /* AES-256-XTS takes a 64-byte key */
26 * Allocate a tfm (a transformation object) and set the key.
28 * In real-world use, a tfm and key are typically used for many
39 get_random_bytes(key, sizeof(key));
40 err = crypto_skcipher_setkey(tfm, key, sizeof(key));
42 pr_err("Error setting key: %d\n", err);
162 char *drbg = "drbg_nopr_sha256"; /* Hash DRBG with SHA-256, no PR */
180 pr_debug("RNG returned no data");
|
| /linux-6.15/Documentation/devicetree/bindings/nvmem/ |
| H A D | rmem.yaml | 21 - raspberrypi,bootloader-public-key
27 no-map:
35 - no-map
50 no-map;
|
| /linux-6.15/Documentation/driver-api/nvdimm/ |
| H A D | security.rst | 29 disable <keyid> - disable enabled security and remove key.
31 erase <keyid> - delete existing user encryption key.
34 master_erase <keyid> - delete existing user encryption key.
73 what the key description is for the old key since we are only interested in the
80 If there is no old keyid due to a security enabling, then a 0 should be
109 Overwrite can be done without a key if security is not enabled. A key serial
110 of 0 can be passed in to indicate no key.
124 master passphrase key is passed to the kernel. The master passphrase key
125 is just another encrypted-key.
135 passphrase key is passed to the kernel. The master passphrase key is just
[all …]
|
| /linux-6.15/Documentation/security/ |
| H A D | siphash.rst | 18 Generating a key
24 siphash_key_t key;
25 get_random_bytes(&key, sizeof(key));
56 siphash_key_t key;
61 get_random_bytes(&table->key, sizeof(table->key));
86 to always ensure the struct has no padding holes. The easiest way to do this
135 64-bit code, SipHash-1-3 is no slower than HalfSipHash-1-3, and can be faster.
147 hsiphash_key_t key;
148 get_random_bytes(&key, sizeof(key));
178 hsiphash_key_t key;
[all …]
|
| /linux-6.15/Documentation/core-api/ |
| H A D | protection-keys.rst | 20 a "protection key", giving 16 possible keys.
22 Protections for each key are defined with a per-CPU user-accessible register
32 access only and have no effect on instruction fetches.
37 Pkeys use 3 bits in each page table entry, to encode a "protection key index",
40 Protections for each key are defined with a per-CPU user-writable system
42 overlay permissions for each protection key index.
47 Unlike x86_64, the protection key permissions also apply to instruction
62 to change access permissions to memory covered with a key. In this example
80 is no longer in use::
119 value for the protection key register and so will not be consistent with
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | thunderbolt.rst | 112 The ``authorized`` attribute reads 0 which means no PCIe tunnels are
141 # key=$(openssl rand -hex 32)
142 # echo $key > /sys/bus/thunderbolt/devices/0-3/key
149 device using the same key::
151 # echo $key > /sys/bus/thunderbolt/devices/0-3/key
156 However, if the challenge fails no tunnels are created and error is
160 the device without a key or write a new key and write 1 to the
224 be available for your system in which case there is no need to plug in a
238 If no errors are returned, the host controller shortly disappears. Once
259 Upgrading on-board retimer NVM when there is no cable connected
[all …]
|
| /linux-6.15/arch/riscv/boot/dts/sophgo/ |
| H A D | sg2042-milkv-pioneer.dts | 22 key-power {
46 no-sdio;
47 no-sd;
65 no-sdio;
66 no-mmc;
|
| /linux-6.15/Documentation/bpf/ |
| H A D | map_bloom_filter.rst | 39 time. If no number is specified, the default used will be 5 hash
45 synchronising concurrent updates and lookups to ensure no false negative
86 int bpf_map_update_elem (int fd, const void *key, const void *value, __u64 flags)
89 ``bpf_map_update_elem`` function. The ``key`` parameter must be set to
98 int bpf_map_lookup_elem (int fd, const void *key, void *value)
101 filter using libbpf's ``bpf_map_lookup_elem`` function. The ``key``
128 void *lookup(__u32 key)
130 if (bpf_map_peek_elem(&bloom_filter, &key) == 0) {
134 return bpf_map_lookup_elem(&hash_table, &key);
154 0, /* key size, must be zero */
|