Searched +full:key +full:- +full:up (Results 1 – 25 of 230) sorted by relevance
12345678910
| /Documentation/devicetree/bindings/input/ |
| D | gpio-keys.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
15 - gpio-keys
16 - gpio-keys-polled
23 poll-interval: true
26 …"^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switc…
35 - items:
[all …]
|
| D | qcom,pm8921-pwrkey.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/qcom,pm8921-pwrkey.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PM8921 PMIC Power Key
10 - Bjorn Andersson <andersson@kernel.org>
13 - $ref: input.yaml#
18 - enum:
19 - qcom,pm8921-pwrkey
20 - qcom,pm8058-pwrkey
[all …]
|
| D | qcom,pm8941-pwrkey.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/qcom,pm8941-pwrkey.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PM8941 PMIC Power Key
10 - Courtney Cavin <courtney.cavin@sonymobile.com>
11 - Vinod Koul <vkoul@kernel.org>
14 - $ref: input.yaml#
19 - qcom,pm8941-pwrkey
20 - qcom,pm8941-resin
[all …]
|
| D | pxa27x-keypad.txt | 4 - compatible : should be "marvell,pxa27x-keypad"
5 - reg : Address and length of the register set for the device
6 - interrupts : The interrupt for the keypad controller
7 - marvell,debounce-interval : How long time the key will be
9 is debounce interval for direct key and bit[15:0] is debounce
10 interval for matrix key. The value is in binary number of 2ms
13 Please refer to matrix-keymap.txt
16 - marvell,direct-key-count : How many direct keyes are used.
17 - marvell,direct-key-mask : The mask indicates which keyes
18 are used. If bit[X] of the mask is set, the direct key X
[all …]
|
| D | adc-keys.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/input/adc-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alexandre Belloni <alexandre.belloni@bootlin.com>
13 - $ref: input.yaml#
17 const: adc-keys
19 io-channels:
22 io-channel-names:
25 keyup-threshold-microvolt:
[all …]
|
| /Documentation/networking/ |
| D | dns_resolver.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - Overview.
10 - Compilation.
11 - Setting up.
12 - Usage.
13 - Mechanism.
14 - Debugging.
21 by way of requesting a key of key type dns_resolver. These queries are
22 upcalled to userspace through /sbin/request-key.
25 request-key. It is under development and does not yet provide the full feature
[all …]
|
| D | fib_trie.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 LC-trie implementation notes
8 ----------
10 An end node with data. This has a copy of the relevant key, along
16 indexed through a subset of the key. See Level Compression.
19 ------------------------
21 The number of bits in the key segment used for indexing into the
22 child array - the "child index". See Level Compression.
25 The position (in the key) of the key segment used for indexing into
30 a segment of the key specified by the parent's "pos" and "bits"
[all …]
|
| D | openvswitch.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 flow-level packet processing on selected network devices. It can be
10 VLAN processing, network access control, flow-based network control,
22 extracting its flow key and looking it up in the flow table. If there
25 its processing, userspace will likely set up a flow to handle further
26 packets of the same type entirely in-kernel).
29 Flow key compatibility
30 ----------------------
35 versions to parse additional protocols as part of the flow key. It
39 applications to work with any version of the flow key, past or future.
[all …]
|
| /Documentation/crypto/ |
| D | asymmetric-keys.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Asymmetric / Public-key Cryptography Key Type
9 - Overview.
10 - Key identification.
11 - Accessing asymmetric keys.
12 - Signature verification.
13 - Asymmetric key subtypes.
14 - Instantiation data parsers.
15 - Keyring link restrictions.
21 The "asymmetric" key type is designed to be a container for the keys used in
[all …]
|
| D | descore-readme.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 ------------------------------------------------------------------------------
15 des - fast & portable DES encryption & decryption.
42 2. PORTABILITY to any byte-addressable host with a 32bit unsigned C type
43 3. Plug-compatible replacement for KERBEROS's low-level routines.
46 register-starved machines. My discussions with Richard Outerbridge,
51 up in a parameterized fashion so it can easily be modified by speed-daemon
58 compile on a SPARCStation 1 (cc -O4, gcc -O2):
60 this code (byte-order independent):
62 - 30us per encryption (options: 64k tables, no IP/FP)
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-tables.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
20 layer. This means that the IR key strokes will look like normal keyboard
21 key strokes (if CONFIG_INPUT_KEYBOARD is enabled). Using the event
30 .. flat-table:: IR default keymapping
31 :header-rows: 0
32 :stub-columns: 0
36 - .. row 1
38 - Key code
40 - Meaning
42 - Key examples on IR
[all …]
|
| /Documentation/security/keys/ |
| D | request-key.rst | 2 Key Request Service
5 The key request service is part of the key retention service (refer to
12 struct key *request_key(const struct key_type *type,
18 struct key *request_key_tag(const struct key_type *type,
25 struct key *request_key_with_auxdata(const struct key_type *type,
34 struct key *request_key_rcu(const struct key_type *type,
45 The main difference between the access points is that the in-kernel interface
46 does not need to link the key to a keyring to prevent it from being immediately
47 destroyed. The kernel interface returns a pointer directly to the key, and
48 it's up to the caller to destroy the key.
[all …]
|
| D | core.rst | 2 Kernel Key Retention Service
5 This service allows cryptographic keys, authentication tokens, cross-domain
9 Keyrings are permitted; these are a special type of key that can hold links to
13 The key service can be configured on by enabling:
15 "Security options"/"Enable access key retention support" (CONFIG_KEYS)
22 Key Overview
26 tokens, keyrings, etc.. These are represented in the kernel by struct key.
28 Each key has a number of attributes:
30 - A serial number.
31 - A type.
[all …]
|
| /Documentation/core-api/ |
| D | assoc_array.rst | 20 Rather, the array is made up of metadata blocks that point to objects.
24 4. Index keys must be unique. Inserting an object with the same key as one
35 key order.
43 10. Objects in the array can be looked up by means of their index key.
45 11. Objects can be looked up while the array is being modified, provided the
46 RCU readlock is being held by the thread doing the look up.
48 The implementation uses a tree of 16-pointer nodes internally that are indexed
49 on each level by nibbles from the index key in the same manner as in a radix
51 what would otherwise be a series of single-occupancy nodes. Further, nodes
68 ./script/config -e ASSOCIATIVE_ARRAY
[all …]
|
| /Documentation/admin-guide/ |
| D | sysrq.rst | 1 Linux Magic System Request Key Hacks
6 What is the magic SysRq key?
9 It is a 'magical' key combo you can hit which the kernel will respond to
10 regardless of whatever else it is doing, unless it is completely locked up.
12 How do I enable the magic SysRq key?
15 You need to say "yes" to 'Magic SysRq key (CONFIG_MAGIC_SYSRQ)' when
18 the SysRq key. The default value in this file is set by the
22 - 0 - disable sysrq completely
23 - 1 - enable all functions of sysrq
24 - >1 - bitmask of allowed sysrq functions (see below for detailed function
[all …]
|
| /Documentation/input/devices/ |
| D | atarikbd.rst | 12 provides a convenient connection point for a mouse and switch-type joysticks.
13 The ikbd processor also maintains a time-of-day clock with one second
18 The ikbd communicates with the main processor over a high speed bi-directional
27 The keyboard always returns key make/break scan codes. The ikbd generates
28 keyboard scan codes for each key press and release. The key scan make (key
30 ISO key position in the scan code table should exist even if no keyswitch
31 exists in that position on a particular keyboard. The break code for each key
41 0xF8-0xFB relative mouse position records (lsbs determined by
43 0xFC time-of-day
49 The two shift keys return different scan codes in this mode. The ENTER key
[all …]
|
| /Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 9 - Borislav Deianov <borislav@users.sf.net>
10 - Henrique de Moraes Holschuh <hmh@hmh.eng.br>
12 http://ibm-acpi.sf.net/
19 This driver used to be named ibm-acpi until kernel 2.6.21 and release
20 0.13-20070314. It used to be in the drivers/acpi tree, but it was
21 moved to the drivers/misc tree and renamed to thinkpad-acpi for kernel
25 The driver is named "thinkpad-acpi". In some places, like module
29 "tpacpi" is used as a shorthand where "thinkpad-acpi" would be too
33 ------
38 - Fn key combinations
[all …]
|
| /Documentation/bpf/ |
| D | map_cpumap.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
9 - ``BPF_MAP_TYPE_CPUMAP`` was introduced in kernel version 4.15
11 .. kernel-doc:: kernel/bpf/cpumap.c
14 An example use-case for this map type is software based Receive Side Scaling (RSS).
16 The CPUMAP represents the CPUs in the system indexed as the map-key, and the
17 map-value is the config setting (per CPUMAP entry). Each CPUMAP entry has a dedicated
32 ----------
35 .. code-block:: c
37 long bpf_redirect_map(struct bpf_map *map, u32 key, u64 flags)
39 Redirect the packet to the endpoint referenced by ``map`` at index ``key``.
[all …]
|
| D | map_devmap.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
9 - ``BPF_MAP_TYPE_DEVMAP`` was introduced in kernel version 4.14
10 - ``BPF_MAP_TYPE_DEVMAP_HASH`` was introduced in kernel version 5.4
14 ``BPF_MAP_TYPE_DEVMAP`` is backed by an array that uses the key as
16 is backed by a hash table that uses a key to lookup a reference to a net device.
17 The user provides either <``key``/ ``ifindex``> or <``key``/ ``struct bpf_devmap_val``>
21 - The key to a hash map doesn't have to be an ``ifindex``.
22 - While ``BPF_MAP_TYPE_DEVMAP_HASH`` allows for densely packing the net devices
23 it comes at the cost of a hash of the key when performing a look up.
31 ----------
[all …]
|
| /Documentation/process/ |
| D | maintainer-pgp-guide.rst | 12 Linux Foundation. Please read that document for more in-depth discussion
15 .. _`Protecting Code Integrity`: https://github.com/lfit/itpol/blob/master/protecting-code-integrit…
22 communication channels between developers via PGP-signed email exchange.
26 - Distributed source repositories (git)
27 - Periodic release snapshots (tarballs)
35 - git repositories provide PGP signatures on all tags
36 - tarballs provide detached PGP signatures with all downloads
41 -------------------------------------------
64 ----------------------
70 $ gpg --version | head -n1
[all …]
|
| /Documentation/filesystems/ |
| D | afs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - Overview.
10 - Usage.
11 - Mountpoints.
12 - Dynamic root.
13 - Proc filesystem.
14 - The cell database.
15 - Security.
16 - The @sys substitution.
45 CONFIG_AF_RXRPC - The RxRPC protocol transport
[all …]
|
| D | fscrypt.rst | 2 Filesystem-level encryption (fscrypt)
11 Note: "fscrypt" in this document refers to the kernel-level portion,
14 covers the kernel-level portion. For command-line examples of how to
18 `fscryptctl <https://github.com/google/fscryptctl>`_ or `Android's key
20 <https://source.android.com/security/encryption/file-based>`_, over
25 Unlike dm-crypt, fscrypt operates at the filesystem level rather than
28 filesystem. This is useful for multi-user systems where each user's
29 data-at-rest needs to be cryptographically isolated from the others.
34 directly into supported filesystems --- currently ext4, F2FS, UBIFS,
44 fscrypt does not support encrypting files in-place. Instead, it
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 6 ---------------
16 ------------------
28 update <old_keyid> <new_keyid> - enable or update passphrase.
29 disable <keyid> - disable enabled security and remove key.
30 freeze - freeze changing of security states.
31 erase <keyid> - delete existing user encryption key.
32 overwrite <keyid> - wipe the entire nvdimm.
33 master_update <keyid> <new_keyid> - enable or update master passphrase.
34 master_erase <keyid> - delete existing user encryption key.
36 3. Key Management
[all …]
|
| /Documentation/networking/pse-pd/ |
| D | introduction.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 --------
15 ----------------
22 with single balanced twisted-pair PHYs, as per Clause 104 of IEEE 802.3. PoDL
26 IEEE 802.3-2018 Addendums and Related Clauses
27 ---------------------------------------------
29 Key addenda to the IEEE 802.3-2018 standard relevant to power delivery over
32 - **802.3af (Approved in 2003-06-12)**: Known as PoE in the market, detailed in
33 Clause 33, delivering up to 15.4W of power.
34 - **802.3at (Approved in 2009-09-11)**: Marketed as PoE+, enhancing PoE as
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | nuvoton,nau8821.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Seven Lee <wtli@nuvoton.com>
13 - $ref: dai-common.yaml#
25 nuvoton,jkdet-enable:
29 nuvoton,jkdet-pull-enable:
30 description: Enable JKDET pin pull. If set - pin pull enabled,
34 nuvoton,jkdet-pull-up:
35 description: Pull-up JKDET pin. If set then JKDET pin is pull up,
[all …]
|
12345678910