Home
last modified time | relevance | path

Searched refs:algorithm (Results 1 – 188 of 188) sorted by relevance

/linux-4.1.27/crypto/
DKconfig91 tristate "Cryptographic algorithm manager"
105 tristate "Userspace cryptographic algorithm configuration"
118 algorithm registration.
144 This converts an arbitrary crypto algorithm into a parallel
145 algorithm that executes in kernel threads.
158 converts an arbitrary synchronous software crypto algorithm
159 into an asynchronous algorithm that executes in a kernel thread.
227 xoring it with a salt. This algorithm is mainly useful for CTR
237 This block cipher algorithm is required for IPSec.
246 This block cipher algorithm is required for IPSec.
[all …]
/linux-4.1.27/Documentation/crypto/
Dapi-intro.txt30 [algorithm api] (for registering algorithms)
32 The idea is to make the user interface and algorithm registration API
94 When submitting a new algorithm for inclusion, a mandatory requirement
189 SHA1 algorithm contributors:
192 DES algorithm contributors:
197 Blowfish algorithm contributors:
201 Twofish algorithm contributors:
205 SHA256/384/512 algorithm contributors:
210 AES algorithm contributors:
218 CAST5 algorithm contributors:
[all …]
Dasymmetric-keys.txt143 The algorithm used must be noted in sig->pkey_hash_algo, and all the MPIs that
154 The function may also return -ENOTSUPP if an unsupported public-key algorithm
155 or public-key/hash algorithm combination is specified or the key doesn't
199 against the key. For instance the name of the public key algorithm type
303 public-key algorithm such as RSA and DSA this will likely be a printable
/linux-4.1.27/drivers/staging/skein/
DKconfig2 tristate "Skein digest algorithm"
7 Skein secure hash algorithm is one of 5 finalists from the NIST SHA3
16 cipher algorithm.
/linux-4.1.27/arch/arm/crypto/
DKconfig12 tristate "SHA1 digest algorithm (ARM-asm)"
20 tristate "SHA1 digest algorithm (ARM NEON)"
31 tristate "SHA1 digest algorithm (ARM v8 Crypto Extensions)"
40 tristate "SHA-224/256 digest algorithm (ARM v8 Crypto Extensions)"
49 tristate "SHA-224/256 digest algorithm (ARM-asm and NEON)"
57 tristate "SHA384 and SHA512 digest algorithm (ARM NEON)"
80 algorithm.
/linux-4.1.27/drivers/block/zram/
DKconfig19 bool "Enable LZ4 algorithm support"
25 This option enables LZ4 compression algorithm support. Compression
26 algorithm can be changed using `comp_algorithm' device attribute.
/linux-4.1.27/drivers/crypto/ux500/hash/
Dhash_core.c244 if (HASH_ALGO_SHA1 == ctx->config.algorithm) { in get_empty_message_digest()
250 ctx->config.algorithm) { in get_empty_message_digest()
263 if (HASH_ALGO_SHA1 == ctx->config.algorithm) { in get_empty_message_digest()
268 } else if (HASH_ALGO_SHA256 == ctx->config.algorithm) { in get_empty_message_digest()
695 if (config->algorithm != HASH_ALGO_SHA1 && in hash_setconfiguration()
696 config->algorithm != HASH_ALGO_SHA256) in hash_setconfiguration()
708 switch (config->algorithm) { in hash_setconfiguration()
956 hash_get_digest(device_data, digest, ctx->config.algorithm); in hash_dma_final()
1057 hash_get_digest(device_data, digest, ctx->config.algorithm); in hash_hw_final()
1274 u8 *digest, int algorithm) in hash_get_digest() argument
[all …]
Dhash_alg.h295 int algorithm; member
388 u8 *digest, int algorithm);
/linux-4.1.27/crypto/asymmetric_keys/
DKconfig13 tristate "Asymmetric public-key crypto algorithm subtype"
22 ENOPKG will be reported if the requisite algorithm is unavailable.
25 tristate "RSA public-key algorithm"
28 This option enables support for the RSA algorithm (PKCS#1, RFC3447).
Dx509.asn124 algorithm OBJECT IDENTIFIER ({ x509_note_OID }),
48 algorithm AlgorithmIdentifier,
Dpkcs7.asn136 algorithm OBJECT IDENTIFIER ({ pkcs7_note_OID }),
111 algorithm OBJECT IDENTIFIER ({ pkcs7_note_OID }),
Dmscode.asn126 algorithm OBJECT IDENTIFIER ({ mscode_note_digest_algo }),
/linux-4.1.27/net/netfilter/ipvs/
DKconfig116 The robin-robin scheduling algorithm simply directs network
125 The weighted robin-robin scheduling algorithm directs network
138 The least-connection scheduling algorithm directs network
148 The weighted least-connection scheduling algorithm directs network
158 The weighted failover scheduling algorithm directs network
168 The locality-based least-connection scheduling algorithm is for
170 This algorithm usually directs packet destined for an IP address to
183 algorithm is also for destination IP load balancing. It is
200 The destination hashing scheduling algorithm assigns network
210 The source hashing scheduling algorithm assigns network
[all …]
/linux-4.1.27/drivers/net/wireless/rtlwifi/btcoexist/
Dhalbtc8821a1ant.c501 u8 algorithm = BT_8821A_1ANT_COEX_ALGO_UNDEFINED; in halbtc8821a1ant_action_algorithm() local
509 return algorithm; in halbtc8821a1ant_action_algorithm()
525 algorithm = BT_8821A_1ANT_COEX_ALGO_SCO; in halbtc8821a1ant_action_algorithm()
530 algorithm = BT_8821A_1ANT_COEX_ALGO_HID; in halbtc8821a1ant_action_algorithm()
534 algorithm = BT_8821A_1ANT_COEX_ALGO_A2DP; in halbtc8821a1ant_action_algorithm()
539 algorithm = BT_8821A_1ANT_COEX_ALGO_PANHS; in halbtc8821a1ant_action_algorithm()
543 algorithm = BT_8821A_1ANT_COEX_ALGO_PANEDR; in halbtc8821a1ant_action_algorithm()
552 algorithm = BT_8821A_1ANT_COEX_ALGO_HID; in halbtc8821a1ant_action_algorithm()
556 algorithm = BT_8821A_1ANT_COEX_ALGO_SCO; in halbtc8821a1ant_action_algorithm()
561 algorithm = BT_8821A_1ANT_COEX_ALGO_SCO; in halbtc8821a1ant_action_algorithm()
[all …]
Dhalbtc8723b1ant.c529 u8 algorithm = BT_8723B_1ANT_COEX_ALGO_UNDEFINED; in halbtc8723b1ant_action_algorithm() local
537 return algorithm; in halbtc8723b1ant_action_algorithm()
553 algorithm = BT_8723B_1ANT_COEX_ALGO_SCO; in halbtc8723b1ant_action_algorithm()
558 algorithm = BT_8723B_1ANT_COEX_ALGO_HID; in halbtc8723b1ant_action_algorithm()
562 algorithm = BT_8723B_1ANT_COEX_ALGO_A2DP; in halbtc8723b1ant_action_algorithm()
567 algorithm = in halbtc8723b1ant_action_algorithm()
572 algorithm = in halbtc8723b1ant_action_algorithm()
582 algorithm = BT_8723B_1ANT_COEX_ALGO_HID; in halbtc8723b1ant_action_algorithm()
586 algorithm = BT_8723B_1ANT_COEX_ALGO_SCO; in halbtc8723b1ant_action_algorithm()
591 algorithm = BT_8723B_1ANT_COEX_ALGO_SCO; in halbtc8723b1ant_action_algorithm()
[all …]
Dhalbtc8821a2ant.c357 u8 algorithm = BT_8821A_2ANT_COEX_ALGO_UNDEFINED; in halbtc8821a2ant_action_algorithm() local
373 return algorithm; in halbtc8821a2ant_action_algorithm()
389 algorithm = BT_8821A_2ANT_COEX_ALGO_SCO; in halbtc8821a2ant_action_algorithm()
394 algorithm = BT_8821A_2ANT_COEX_ALGO_HID; in halbtc8821a2ant_action_algorithm()
398 algorithm = BT_8821A_2ANT_COEX_ALGO_A2DP; in halbtc8821a2ant_action_algorithm()
403 algorithm = BT_8821A_2ANT_COEX_ALGO_PANHS; in halbtc8821a2ant_action_algorithm()
407 algorithm = BT_8821A_2ANT_COEX_ALGO_PANEDR; in halbtc8821a2ant_action_algorithm()
416 algorithm = BT_8821A_2ANT_COEX_ALGO_PANEDR_HID; in halbtc8821a2ant_action_algorithm()
420 algorithm = BT_8821A_2ANT_COEX_ALGO_PANEDR_HID; in halbtc8821a2ant_action_algorithm()
425 algorithm = BT_8821A_2ANT_COEX_ALGO_SCO; in halbtc8821a2ant_action_algorithm()
[all …]
Dhalbtc8192e2ant.c589 u8 algorithm = BT_8192E_2ANT_COEX_ALGO_UNDEFINED; in halbtc8192e2ant_action_algorithm() local
597 return algorithm; in halbtc8192e2ant_action_algorithm()
613 algorithm = BT_8192E_2ANT_COEX_ALGO_SCO; in halbtc8192e2ant_action_algorithm()
618 algorithm = BT_8192E_2ANT_COEX_ALGO_HID; in halbtc8192e2ant_action_algorithm()
622 algorithm = BT_8192E_2ANT_COEX_ALGO_A2DP; in halbtc8192e2ant_action_algorithm()
627 algorithm = in halbtc8192e2ant_action_algorithm()
632 algorithm = in halbtc8192e2ant_action_algorithm()
642 algorithm = BT_8192E_2ANT_COEX_ALGO_SCO; in halbtc8192e2ant_action_algorithm()
646 algorithm = BT_8192E_2ANT_COEX_ALGO_PANEDR_HID; in halbtc8192e2ant_action_algorithm()
651 algorithm = BT_8192E_2ANT_COEX_ALGO_SCO; in halbtc8192e2ant_action_algorithm()
[all …]
Dhalbtc8723b2ant.c424 u8 algorithm = BT_8723B_2ANT_COEX_ALGO_UNDEFINED; in btc8723b2ant_action_algorithm() local
432 return algorithm; in btc8723b2ant_action_algorithm()
448 algorithm = BT_8723B_2ANT_COEX_ALGO_SCO; in btc8723b2ant_action_algorithm()
453 algorithm = BT_8723B_2ANT_COEX_ALGO_HID; in btc8723b2ant_action_algorithm()
457 algorithm = BT_8723B_2ANT_COEX_ALGO_A2DP; in btc8723b2ant_action_algorithm()
462 algorithm = in btc8723b2ant_action_algorithm()
467 algorithm = in btc8723b2ant_action_algorithm()
477 algorithm = BT_8723B_2ANT_COEX_ALGO_PANEDR_HID; in btc8723b2ant_action_algorithm()
481 algorithm = BT_8723B_2ANT_COEX_ALGO_PANEDR_HID; in btc8723b2ant_action_algorithm()
486 algorithm = BT_8723B_2ANT_COEX_ALGO_SCO; in btc8723b2ant_action_algorithm()
[all …]
/linux-4.1.27/Documentation/
Dmodule-signing.txt35 SHA-512 (the algorithm is selected by data in the signature).
76 (3) "Which hash algorithm should modules be signed with?"
78 This presents a choice of which hash algorithm the installation phase will
87 The algorithm selected here will also be built into the kernel (rather
88 than being a module) so that modules signed with that algorithm can have
183 1. The hash algorithm (e.g., sha256)
193 The hash algorithm used does not have to match the one configured, but if it
194 doesn't, you should make sure that hash algorithm is either built into the
Dmd-cluster.txt75 The algorithm is:
156 to be added. For this, the following algorithm is used:
Dkmemleak.txt85 The scanning algorithm steps:
188 To keep the algorithm simple, kmemleak scans for values pointing to any
Dcrc32.txt134 the parallelism. With the classic Sarwate algorithm, each table lookup
147 twice as fast as the basic Sarwate algorithm.
Dassoc_array.txt317 iteration algorithm should not, however, miss any objects.
490 algorithm will insert a shortcut to skip over the '1111' keyspace in a single
498 insertion algorithm finds that it is trying to insert a 17th object into a
Dxz.txt9 algorithm (filter) is LZMA2. Additional filters can be used to improve
Dlzo.txt74 an implementation design choice independant on the algorithm or encoding.
Dkernel-parameters.txt576 algorithm. Accepted values range from 0 to 7
/linux-4.1.27/arch/arm64/crypto/
DKconfig12 tristate "SHA-1 digest algorithm (ARMv8 Crypto Extensions)"
17 tristate "SHA-224/SHA-256 digest algorithm (ARMv8 Crypto Extensions)"
/linux-4.1.27/net/sched/
DKconfig51 scheduling algorithm. This algorithm classifies the waiting packets
68 packet scheduling algorithm. See
73 different properties and different algorithm.
82 (HFSC) packet scheduling algorithm.
123 packet scheduling algorithm.
134 packet scheduling algorithm.
145 packet scheduling algorithm.
156 scheduling algorithm. This queueing discipline allows the combination
168 scheduling algorithm.
179 (GRED) packet scheduling algorithm for some of your network devices
[all …]
/linux-4.1.27/drivers/crypto/
DKconfig26 tristate "PadLock driver for AES algorithm"
31 Use VIA PadLock for AES algorithm.
59 engine for the CryptoAPI AES algorithm.
80 tristate "SHA1 digest algorithm"
90 tristate "SHA256 digest algorithm"
100 tristate "SHA384 and SHA512 digest algorithm"
117 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
153 tristate "GHASH digest algorithm"
158 GHASH message digest algorithm for GCM (Galois/Counter Mode).
217 to offload cryptographic algorithm computation.
/linux-4.1.27/lib/
DKconfig124 of CRC32 algorithm. Choose the default ("slice by 8") unless you
130 Calculate checksum 8 bytes at a time with a clever slicing algorithm.
131 This is the fastest algorithm, but comes with a 8KiB lookup table.
141 Calculate checksum 4 bytes at a time with a clever slicing algorithm.
150 Calculate checksum a byte at a time using Sarwate's algorithm. This
189 algorithm. Module will be called crc8.
350 overlapping nodes. The algorithm is implemented as an
471 tristate "CORDIC algorithm"
473 This option provides an implementation of the CORDIC algorithm;
/linux-4.1.27/net/mac80211/
DKconfig28 This option enables the 'minstrel' TX rate control algorithm
35 This option enables the 'minstrel_ht' TX rate control algorithm
42 This option enables VHT in the 'minstrel_ht' TX rate control algorithm
45 prompt "Default rate control algorithm"
49 This option selects the default rate control algorithm
58 Select Minstrel as the default rate control algorithm.
71 comment "Some wireless drivers require a rate control algorithm"
Ddebugfs_key.c76 KEY_OPS(algorithm);
329 DEBUGFS_ADD(algorithm); in ieee80211_debugfs_key_add()
Dmlme.c2516 ieee80211_send_auth(sdata, 3, auth_data->algorithm, 0, in ieee80211_auth_challenge()
2552 if (auth_alg != ifmgd->auth_data->algorithm || in ieee80211_rx_mgmt_auth()
2555 mgmt->sa, auth_alg, ifmgd->auth_data->algorithm, in ieee80211_rx_mgmt_auth()
2572 switch (ifmgd->auth_data->algorithm) { in ieee80211_rx_mgmt_auth()
2587 ifmgd->auth_data->algorithm); in ieee80211_rx_mgmt_auth()
2599 if (ifmgd->auth_data->algorithm == WLAN_AUTH_SAE && in ieee80211_rx_mgmt_auth()
3708 if (auth_data->algorithm == WLAN_AUTH_SAE) { in ieee80211_probe_auth()
3718 ieee80211_send_auth(sdata, trans, auth_data->algorithm, status, in ieee80211_probe_auth()
4523 auth_data->algorithm = auth_alg; in ieee80211_mgd_auth()
Dieee80211_i.h374 u16 algorithm, expected_transaction; member
/linux-4.1.27/Documentation/networking/
Ddctcp.txt4 DCTCP is an enhancement to the TCP congestion control algorithm for data
22 The algorithm is further described in detail in the following two
Dbaycom.txt104 the software DCD algorithm (see below).
121 utilise a software DCD algorithm (options=1) or use a DCD signal from
125 open. It is highly recommended to use the software DCD algorithm,
129 par96: the software DCD algorithm for this type of modem is rather poor.
131 a reasonable DCD algorithm in software. Therefore, if your radio
Dpolicy-routing.txt64 Lookup algorithm
97 Very clean, stable and robust algorithm for OSPF routing
127 It is a funny, but pretty useless algorithm.
Dfib_trie.txt31 Note that the search algorithm will simply skip over these bits when
69 level compression algorithm on part of the trie.
72 Looks up a key, deletes it and runs the level compression algorithm.
De1000e.txt68 for this reason an adaptive interrupt moderation algorithm was implemented.
76 The algorithm classifies the incoming traffic every interval into
90 grid computing, the algorithm can reduce latency even more when
Dtcp.txt48 Good TCP congestion control is a complex problem because the algorithm
De1000.txt100 for this reason an adaptive interrupt moderation algorithm was implemented.
108 The algorithm classifies the incoming traffic every interval into
122 grid computing, the algorithm can reduce latency even more when
Dxfrm_sync.txt20 For this reason, we also add a nagle-like algorithm to restrict
Dde4x5.txt98 auto media sense algorithm is that it can now use one that is more in
Dip-sysctl.txt227 Set the congestion control algorithm to be used for new
228 connections. The algorithm "reno" is always available, but
286 F-RTO is an enhanced recovery algorithm for TCP retransmission
1558 address selection algorithm.
1768 Select the hmac algorithm used when generating the cookie value sent by
Dcxgb.txt33 This feature provides an adaptive algorithm that adjusts the interrupt
Dz8530drv.txt520 min), and then the selected algorithm for keyup will be
Dbonding.txt810 This algorithm will place all traffic to a particular
813 This algorithm is 802.3ad compliant.
832 This algorithm will place all traffic to a particular
842 This algorithm is 802.3ad compliant.
869 This algorithm is not fully 802.3ad compliant. A
/linux-4.1.27/Documentation/device-mapper/
Dverity.txt13 <algorithm> <digest> <salt>
54 <algorithm>
55 The cryptographic hash algorithm used for this device. This should
56 be the name of the algorithm, like "sha1".
110 selected cryptographic digest algorithm. The hashes are linearly-ordered in
Dswitch.txt37 robin algorithm to send I/O across all paths and let the storage array
Ddm-raid.txt222 1.4.2 Add RAID10 "far" and "offset" algorithm support.
/linux-4.1.27/Documentation/blockdev/
Dzram.txt46 3) Select compression algorithm
49 change selected compression algorithm (once the device is initialised
50 there is no way to change compression algorithm).
57 #select lzo compression algorithm
117 comp_algorithm RW show and change the compression algorithm
/linux-4.1.27/drivers/i2c/algos/
DKconfig2 # I2C algorithm drivers configuration
/linux-4.1.27/Documentation/arm/
Dcluster-pm-race-avoidance.txt1 Cluster-wide Power-up/power-down race avoidance algorithm
4 This file documents the algorithm which is used to coordinate CPU and
8 The section "Rationale" explains what the algorithm is for and why it is
11 algorithm in use.
96 In this algorithm, each individual core in a multi-core processor is
102 The algorithm defines the following states for each CPU in the system:
176 race avoidance algorithm.
255 The race avoidance algorithm does not provide a way to determine
417 The race avoidance algorithm documented above does not provide a
482 As currently described and implemented, the algorithm does not
[all …]
Dvlocks.txt29 The easiest way to explain the vlocks algorithm is with some pseudo-code:
69 "entering" array in Lamport's bakery algorithm [1].
122 the basic algorithm:
171 when executing the algorithm in cached memory.
DBooting64 method. Whether this is a hard coded value or some algorithm that
/linux-4.1.27/security/integrity/ima/
DKconfig76 prompt "Default integrity hash algorithm"
80 Select the default hash algorithm used for the measurement
82 hash algorithm can be overwritten using the kernel command
/linux-4.1.27/Documentation/security/
DIMA-templates.txt62 calculated with the SHA1 or MD5 hash algorithm;
65 algorithm (field format: [<hash algo>:]digest, where the digest
66 prefix is shown only if the hash algorithm is not SHA1 or MD5);
Dkeys-request-key.txt7 the requesting algorithm works.
/linux-4.1.27/arch/xtensa/lib/
Dmemset.S121 bbci.l a5, 1, .L0 # if now aligned, return to main algorithm
128 j .L0 # dst is now aligned, return to main algorithm
Dmemcopy.S113 # return to main algorithm
124 j .Ldstaligned # dst is now aligned, return to main algorithm
380 # return to main algorithm
392 # return to main algorithm
Dusercopy.S111 # return to main algorithm
122 j .Ldstaligned # dst is now aligned, return to main algorithm
/linux-4.1.27/Documentation/frv/
Datomic-ops.txt26 To get around this, the following algorithm has been implemented. It operates in a way similar to
34 (*) All atomic operations can then be broken down into the following algorithm:
56 This algorithm suffers from two problems:
/linux-4.1.27/fs/isofs/
Drock.h78 char algorithm[2]; member
Drock.c546 algo = isonum_721(rr->u.ZF.algorithm); in parse_rock_ridge_inode_internal()
579 rr->u.ZF.algorithm[0], in parse_rock_ridge_inode_internal()
580 rr->u.ZF.algorithm[1]); in parse_rock_ridge_inode_internal()
/linux-4.1.27/net/sctp/
DKconfig66 This option sets the default sctp cookie hmac algorithm
84 Use no hmac algorithm in SCTP cookie generation
/linux-4.1.27/drivers/staging/rtl8188eu/include/
Drtw_cmd.h167 u8 algorithm; /* could be none, wep40, TKIP, CCMP, wep104 */ member
186 u8 algorithm; member
Dieee80211.h822 u16 algorithm; member
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-iio-frequency-adf43507 the fractional-N PLL. It is assumed that the algorithm
Dsysfs-fs-ext457 algorithm will pre-read into the buffer cache
Dsysfs-class-uwb_rc40 algorithm will be used. Valid channels depends on the
Dsysfs-block-zram74 compression algorithm selection.
/linux-4.1.27/drivers/crypto/caam/
DKconfig77 tristate "Register algorithm implementations with the Crypto API"
91 tristate "Register hash algorithm implementations with Crypto API"
/linux-4.1.27/Documentation/devicetree/bindings/watchdog/
Dgpio-wdt.txt6 - hw_algo: The algorithm used by the driver. Should be one of the
/linux-4.1.27/lib/xz/
DKconfig5 LZMA2 compression algorithm and BCJ filters are supported using
/linux-4.1.27/drivers/net/wireless/b43/
Dmain.c831 u8 index, u8 algorithm, const u8 *key) in key_write() argument
840 value = ((kidx << 4) | algorithm); in key_write()
968 u8 index, u8 algorithm, in do_key_write() argument
982 if (algorithm == B43_SEC_ALGO_TKIP) { in do_key_write()
997 key_write(dev, index, algorithm, buf); in do_key_write()
1001 dev->key[index].algorithm = algorithm; in do_key_write()
1005 int index, u8 algorithm, in b43_key_write() argument
1020 if (algorithm == B43_SEC_ALGO_TKIP && key_len == 32) in b43_key_write()
1051 do_key_write(dev, index, algorithm, key, key_len, mac_addr); in b43_key_write()
1055 do_key_write(dev, index + 4, algorithm, key, key_len, NULL); in b43_key_write()
[all …]
Dxmit.c323 mac_ctl |= (key->algorithm << B43_TXH_MAC_KEYALG_SHIFT) & in b43_generate_txhdr()
326 if (key->algorithm == B43_SEC_ALGO_TKIP) { in b43_generate_txhdr()
732 if (dev->key[keyidx].algorithm != B43_SEC_ALGO_NONE) { in b43_rx()
Db43.h702 u8 algorithm; member
/linux-4.1.27/Documentation/filesystems/pohmelfs/
Dinfo.txt58 with appropriate hash algorithm and key file and cipher algorithm, mode and key file:
Ddesign_notes.txt12 Since all Linux filesystems lock the whole inode during writing, algorithm
/linux-4.1.27/drivers/staging/rtl8723au/hal/
Drtl8723a_bt-coexist.c6460 u8 algorithm = BT_2ANT_COEX_ALGO_UNDEFINED; in btdm_ActionAlgorithm() local
6538 return algorithm; in btdm_ActionAlgorithm()
6544 algorithm = BT_2ANT_COEX_ALGO_SCO; in btdm_ActionAlgorithm()
6548 algorithm = BT_2ANT_COEX_ALGO_HID; in btdm_ActionAlgorithm()
6551 algorithm = BT_2ANT_COEX_ALGO_A2DP; in btdm_ActionAlgorithm()
6555 algorithm = BT_2ANT_COEX_ALGO_PANHS; in btdm_ActionAlgorithm()
6558 algorithm = BT_2ANT_COEX_ALGO_PANEDR; in btdm_ActionAlgorithm()
6569 algorithm = BT_2ANT_COEX_ALGO_HID; in btdm_ActionAlgorithm()
6575 algorithm = BT_2ANT_COEX_ALGO_SCO; in btdm_ActionAlgorithm()
6578 algorithm = BT_2ANT_COEX_ALGO_PANEDR_HID; in btdm_ActionAlgorithm()
[all …]
/linux-4.1.27/drivers/staging/rtl8712/
Drtl871x_cmd.h205 u8 algorithm; /* encryption algorithm, could be none, wep40, member
221 u8 algorithm; member
Dieee80211.h614 u16 algorithm; member
Drtl871x_cmd.c688 psetstakey_para->algorithm = (unsigned char) in r8712_setstakey_cmd()
692 psetstakey_para->algorithm, false); in r8712_setstakey_cmd()
Drtl871x_mlme.c1254 psetkeyparm->algorithm = in r8712_set_key()
1257 psetkeyparm->algorithm = in r8712_set_key()
1262 switch (psetkeyparm->algorithm) { in r8712_set_key()
/linux-4.1.27/drivers/i2c/
DKconfig77 Some I2C bus drivers require so-called "I2C algorithm" modules
133 Say Y here if you want the I2C algorithm drivers to produce a bunch
/linux-4.1.27/drivers/staging/rtl8723au/core/
Drtw_mlme.c1806 psetkeyparm->algorithm = (unsigned char) in rtw_set_key23a()
1810 psetkeyparm->algorithm); in rtw_set_key23a()
1812 psetkeyparm->algorithm = (u8)psecuritypriv->dot11PrivacyAlgrthm; in rtw_set_key23a()
1815 psetkeyparm->algorithm); in rtw_set_key23a()
1819 if (is_wep_enc(psetkeyparm->algorithm)) in rtw_set_key23a()
1823 psetkeyparm->algorithm, psetkeyparm->keyid, in rtw_set_key23a()
1827 psetkeyparm->algorithm, keyid); in rtw_set_key23a()
1829 switch (psetkeyparm->algorithm) { in rtw_set_key23a()
Drtw_mlme_ext.c924 u16 auth_mode, seq, algorithm; in OnAuth23a() local
940 algorithm = le16_to_cpu(mgmt->u.auth.auth_alg); in OnAuth23a()
942 DBG_8723A("auth alg =%x, seq =%X\n", algorithm, seq); in OnAuth23a()
951 if ((algorithm != WLAN_AUTH_OPEN && auth_mode == 0) || in OnAuth23a()
952 (algorithm == WLAN_AUTH_OPEN && auth_mode == 1)) { in OnAuth23a()
955 algorithm, auth_mode, in OnAuth23a()
1018 if (algorithm == WLAN_AUTH_OPEN && (auth_mode == 0 || auth_mode == 2)) { in OnAuth23a()
1023 pstat->authalg = algorithm; in OnAuth23a()
1036 pstat->authalg = algorithm; in OnAuth23a()
5881 ctrl = BIT(15) | (pparm->algorithm) << 2 | pparm->keyid; in setkey_hdl23a()
[all …]
Drtw_cmd.c700 psetstakey_para->algorithm = in rtw_setstakey_cmd23a()
703 GET_ENCRY_ALGO(psecuritypriv, sta, psetstakey_para->algorithm, in rtw_setstakey_cmd23a()
769 psetstakey_para->algorithm = 0; in rtw_clearstakey_cmd23a()
/linux-4.1.27/scripts/
Dspelling.txt65 algorith||algorithm
67 algoritm||algorithm
69 algorrithm||algorithm
70 algorritm||algorithm
77 alogrithm||algorithm
/linux-4.1.27/arch/m68k/ifpsp060/src/
Dilsp.S86 # or 32-bit divides if possible. Else, use a special math algorithm #
190 # perform the divide algorithm:
283 # if the divisor msw is 0, use simpler algorithm then the full blown
287 bhi.b lddknuth # go use D. Knuth algorithm
290 # a simpler algorithm may be used :
320 # In this algorithm, the divisor is treated as a 2 digit (word) number
Dfpsp.S10065 # algorithm just got done playing with fp0 and expected no exceptions
Dfplsp.S8004 # in Step 2 of the algorithm for LOGN and compute #
/linux-4.1.27/Documentation/i2c/
Dsummary34 of I2C adapters. Each specific adapter driver either depends on one algorithm
/linux-4.1.27/drivers/net/wireless/ath/ath9k/
DKconfig98 bool "Atheros ath9k ACK timeout estimation algorithm (EXPERIMENTAL)"
102 This option enables ath9k dynamic ACK timeout estimation algorithm
/linux-4.1.27/drivers/staging/rtl8723au/include/
Drtw_cmd.h220 u32 algorithm; /* encryption algorithm, could be none, wep40, TKIP, CCMP, wep104 */ member
239 u32 algorithm; member
/linux-4.1.27/Documentation/scheduler/
Dsched-deadline.txt9 2. Scheduling algorithm
35 algorithm, augmented with a mechanism (called Constant Bandwidth Server, CBS)
39 2. Scheduling algorithm
48 consistent with the guarantee (using the CBS[2,3] algorithm). Tasks are then
58 algorithm selects the task with the earliest scheduling deadline as the one
63 In more details, the CBS algorithm assigns scheduling deadlines to
Dsched-design-CFS.txt47 algorithm variants to recognize sleepers.
/linux-4.1.27/net/bridge/
DKconfig15 networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
/linux-4.1.27/drivers/staging/rtl8188eu/core/
Drtw_mlme_ext.c655 u16 algorithm; in OnAuth() local
675 algorithm = le16_to_cpu(*(__le16 *)((size_t)pframe + WLAN_HDR_A3_LEN)); in OnAuth()
677 DBG_88E("auth alg=%x, seq=%X\n", algorithm, seq); in OnAuth()
683 if ((algorithm > 0 && auth_mode == 0) || /* rx a shared-key auth but shared not enabled */ in OnAuth()
684 (algorithm == 0 && auth_mode == 1)) { /* rx a open-system auth but shared-key is enabled */ in OnAuth()
686 algorithm, auth_mode, sa[0], sa[1], sa[2], sa[3], sa[4], sa[5]); in OnAuth()
741 if (algorithm == 0 && (auth_mode == 0 || auth_mode == 2)) { in OnAuth()
746 pstat->authalg = algorithm; in OnAuth()
759 pstat->authalg = algorithm; in OnAuth()
5314 ctrl = BIT(15) | ((pparm->algorithm) << 2) | pparm->keyid; in setkey_hdl()
[all …]
Drtw_mlme.c1639 psetkeyparm->algorithm = (unsigned char)psecuritypriv->dot118021XGrpPrivacy; in rtw_set_key()
1642 psetkeyparm->algorithm)); in rtw_set_key()
1644 psetkeyparm->algorithm = (u8)psecuritypriv->dot11PrivacyAlgrthm; in rtw_set_key()
1647 psetkeyparm->algorithm)); in rtw_set_key()
1653 psetkeyparm->algorithm, psetkeyparm->keyid, pmlmepriv->key_mask); in rtw_set_key()
1656 psetkeyparm->algorithm, keyid)); in rtw_set_key()
1658 switch (psetkeyparm->algorithm) { in rtw_set_key()
Drtw_cmd.c641 psetstakey_para->algorithm = (unsigned char)psecuritypriv->dot11PrivacyAlgrthm; in rtw_setstakey_cmd()
643 GET_ENCRY_ALGO(psecuritypriv, sta, psetstakey_para->algorithm, false); in rtw_setstakey_cmd()
701 psetstakey_para->algorithm = _NO_PRIVACY_; in rtw_clearstakey_cmd()
/linux-4.1.27/Documentation/RCU/
DUP.txt16 Suppose that an RCU-based algorithm scans a linked list containing
38 Suppose that an RCU-based algorithm again scans a linked list containing
DRTFP.txt46 in read-mostly situations. This algorithm does take pains to avoid
264 This restriction makes this algorithm unsuitable for use in
297 This restriction makes this algorithm unsuitable for use in
586 Outline of algorithm to unload modules...
2086 ,Title="[{RFC}][{PATCH}] rcu classic: new algorithm for callbacks-processing"
2094 Updated RCU classic algorithm. Introduced multi-tailed list
DwhatisRCU.txt618 occur when using this algorithm in a real-world Linux
933 occur when using this algorithm in a real-world Linux
935 algorithm.]
/linux-4.1.27/kernel/time/
DKconfig164 therefore uses a fast but non-scalable algorithm for small
165 systems and a lazier but scalable algorithm for large systems.
/linux-4.1.27/drivers/md/
Draid5.h435 int level, algorithm, rmw_level; member
Draid5.c2546 int algorithm = previous ? conf->prev_algo in raid5_compute_sector() local
2547 : conf->algorithm; in raid5_compute_sector()
2577 switch (algorithm) { in raid5_compute_sector()
2609 switch (algorithm) { in raid5_compute_sector()
2746 int algorithm = previous ? conf->prev_algo in compute_blocknr() local
2747 : conf->algorithm; in compute_blocknr()
2763 switch (algorithm) { in compute_blocknr()
2787 switch (algorithm) { in compute_blocknr()
6566 conf->algorithm = mddev->new_layout; in setup_conf()
6813 conf->algorithm, in run()
[all …]
Ddm-raid.c82 const unsigned algorithm; /* RAID algorithm. */ member
170 rs->md.layout = raid_type->algorithm; in context_alloc()
/linux-4.1.27/drivers/net/wireless/b43legacy/
Dxmit.c253 mac_ctl |= (key->algorithm << in generate_txhdr_fw3()
494 if (dev->key[keyidx].algorithm != B43legacy_SEC_ALGO_NONE) { in b43legacy_rx()
Db43legacy.h561 u8 algorithm; member
/linux-4.1.27/Documentation/hwmon/
Dadt747072 order for the automatic pwm algorithm to run. This was the case for earlier
Dabituguru-datasheet127 algorithm described above will still work.
147 algorithm described above will still work.
Dvt1211193 Long story short, the controller implements the following algorithm to set the
Dasc762185 control algorithm is employed to minimize acoustic impact while achieving
Dlm9353 controlled by up to four temperature zones. The fancontrol algorithm is lookup
/linux-4.1.27/drivers/net/ppp/
DKconfig63 Deflate algorithm (the same algorithm that gzip uses) to compress
/linux-4.1.27/Documentation/video4linux/
Dsh_mobile_ceu_camera.txt1 Cropping and Scaling algorithm, used in the sh_mobile_ceu_camera driver
Dvivid.txt978 The scaler is a simple scaler that uses the Coarse Bresenham algorithm. It's
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-driver-ib_srp166 SRP credit algorithm in the SRP specification.
188 information see also the SRP credit algorithm in the SRP
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.txt27 The basic algorithm is to assert your line when you want the bus, then make
/linux-4.1.27/Documentation/filesystems/
Df2fs.txt567 In the greedy algorithm, F2FS selects a victim segment having the smallest number
568 of valid blocks. In the cost-benefit algorithm, F2FS selects a victim segment
570 log block thrashing problem in the greedy algorithm. F2FS adopts the greedy
571 algorithm for on-demand cleaner, while background cleaner adopts cost-benefit
572 algorithm.
Dromfs.txt80 accessible, whichever is smaller). The applied algorithm is the same
83 the source. This algorithm was chosen because although it's not quite
Dntfs.txt416 which parity algorithm to use by specifying the option "parity-algorithm
417 which", where you need to replace "which" with the name of the algorithm to
421 otherwise. If you find which algorithm works please let us know (email the
Dgfs2-glocks.txt139 smoothed exponential estimates and the algorithm used is
174 3. To improve the algorithm for selecting resource groups for
Dext4.txt201 table readahead algorithm will pre-read into
285 algorithm used is designed to automatically tune
462 table readahead algorithm will pre-read into
Dvfat.txt325 following algorithm:
Dhpfs.txt28 heuristic algorithm that I removed. I thing it's danger to let the
Dpath-lookup.txt18 algorithm changed this by holding the dcache_lock at the beginning and walking
Dext2.txt99 blocks. The block allocation algorithm attempts to allocate data blocks
Dxfs-delayed-logging-design.txt588 To keep pin/unpin symmetry, the algorithm needs to change to a "pin on
634 are in progress). Ultimately a two pass algorithm where the formatting is done
Dsharedsubtree.txt896 The overall algorithm breaks the operation into 3 phases: (look at
/linux-4.1.27/drivers/char/tpm/
Dtpm.h327 u8 algorithm[4]; member
/linux-4.1.27/fs/reiserfs/
DREADME126 textbook he got the algorithm from in the code. Note that his analysis
128 was probably more important than the actual algorithm. Colin Plumb also
/linux-4.1.27/Documentation/driver-model/
Dbinding.txt30 algorithm, it is up to the bus driver to provide a callback to compare
/linux-4.1.27/arch/x86/
DKconfig.debug292 compilers. The gcc 4.x series have a rewritten inlining algorithm and
294 this algorithm is so good that allowing gcc 4.x and above to make the
/linux-4.1.27/Documentation/dmaengine/
Dprovider.txt168 algorithm against a memory buffer.
172 simple XOR, and Q being a Reed-Solomon algorithm.
176 algorithm against a memory buffer.
/linux-4.1.27/Documentation/rapidio/
Drapidio.txt236 implemented according to the enumeration algorithm outlined in the RapidIO
247 algorithm. When a new device is found, the enumerator takes ownership of that
278 into the routing table. The algorithm recurs by calling itself with hopcount + 1
/linux-4.1.27/Documentation/early-userspace/
Dbuffer-format.txt79 algorithm used.
/linux-4.1.27/Documentation/filesystems/nfs/
Dpnfs.txt41 hashing and variations of this algorithm can be found at:
/linux-4.1.27/net/ipv4/
DKconfig524 tristate "TCP-Hybla congestion control algorithm"
547 MIMD congestion control algorithm which has some nice scaling
555 TCP Low Priority (TCP-LP), a distributed algorithm whose goal is
577 algorithm, which uses a mixed loss/delay approach to compute the
/linux-4.1.27/drivers/staging/rtl8192u/ieee80211/
Dieee80211_softmac.c674 auth->algorithm = WLAN_AUTH_OPEN; in ieee80211_authentication_req()
676 auth->algorithm = WLAN_AUTH_SHARED_KEY; in ieee80211_authentication_req()
678 auth->algorithm = WLAN_AUTH_OPEN;//0x80; in ieee80211_authentication_req()
679 printk("=================>%s():auth->algorithm is %d\n",__func__,auth->algorithm); in ieee80211_authentication_req()
916 auth->algorithm = cpu_to_le16(WLAN_AUTH_OPEN); in ieee80211_auth_resp()
1578 if (le16_to_cpu(a->algorithm) != WLAN_AUTH_OPEN) in auth_rq_parse()
Dieee80211.h1096 __le16 algorithm; member
/linux-4.1.27/arch/sh/lib64/
Dmemcpy.S27 ! but the algorithm used needs some comparison.
Dcopy_user_memcpy.S25 ! but the algorithm used needs some comparison.
/linux-4.1.27/Documentation/trace/
Devents-kmem.txt91 can be allocated and freed on the same CPU through some algorithm change.
Dring-buffer-design.txt66 algorithm. The writers act like a "stack". The way interrupts works
191 This case is still valid for this algorithm.
394 The main idea behind the lockless algorithm is to combine the moving
/linux-4.1.27/drivers/staging/wlan-ng/
Dhfa384x.h413 u16 algorithm; member
725 u16 algorithm; member
Dprism2sta.c1676 rec.algorithm = inf->info.authreq.algorithm; in prism2sta_inf_authreq_defer()
/linux-4.1.27/init/
DKconfig161 This compression algorithm's ratio is best. Decompression speed
169 XZ uses the LZMA2 algorithm and instruction set specific
880 scenerio while allowing a simple algorithm to be used from bootup.
1907 prompt "Which hash algorithm should modules be signed with?"
1910 This determines which sort of hashing algorithm will be used during
1911 signature generation. This algorithm _must_ be built into the kernel
1913 possible to load a signed module containing the algorithm to check
1955 choice made in "Compression algorithm".
1973 prompt "Compression algorithm"
/linux-4.1.27/Documentation/vm/
Dbalance47 the balancing algorithm works the same way on the various architectures,
Dcleancache.txt8 pages that the kernel's pageframe replacement algorithm (PFRA) would like
/linux-4.1.27/Documentation/video4linux/bttv/
DInsmod-options60 algorithm. You may use lower numbers, if I2C
/linux-4.1.27/Documentation/thermal/
Dsysfs-api.txt228 This file gives information about the algorithm that is currently
230 algorithm or user space application.
Dintel_powerclamp.txt206 we have a simple algorithm to double the injection ratio. A possible
/linux-4.1.27/Documentation/arm/nwfpe/
DREADME.FPE87 These are fully implemented as well. They use the same algorithm as the
/linux-4.1.27/arch/m68k/fpsp040/
Dslogn.S46 | of the algorithm for LOGN and compute log(1+X) as
/linux-4.1.27/Documentation/fb/
Dmodedb.txt71 Formula (GTF) which is an algorithm to calculate the timings, given the
/linux-4.1.27/drivers/staging/rtl8192e/
Drtllib_softmac.c821 auth->algorithm = WLAN_AUTH_OPEN; in rtllib_authentication_req()
823 auth->algorithm = cpu_to_le16(WLAN_AUTH_SHARED_KEY); in rtllib_authentication_req()
825 auth->algorithm = WLAN_AUTH_OPEN; in rtllib_authentication_req()
1062 auth->algorithm = cpu_to_le16(WLAN_AUTH_OPEN); in rtllib_auth_resp()
1833 if (le16_to_cpu(a->algorithm) != WLAN_AUTH_OPEN) in auth_rq_parse()
Drtllib.h1183 __le16 algorithm; member
/linux-4.1.27/drivers/net/wireless/ipw2x00/
Dlibipw.h409 __le16 algorithm; member
/linux-4.1.27/Documentation/virtual/kvm/
Dmsr.txt149 The suggested algorithm for detecting kvmclock presence is then:
Dapi.txt1749 following algorithm:
/linux-4.1.27/Documentation/powerpc/
Dqe_firmware.txt276 this algorithm:
/linux-4.1.27/drivers/net/ethernet/neterion/vxge/
Dvxge-config.h2083 enum vxge_hw_rth_algoritms algorithm,
Dvxge-config.c3718 enum vxge_hw_rth_algoritms algorithm, in vxge_hw_vpath_rts_rth_set() argument
3742 VXGE_HW_RTS_ACCESS_STEER_DATA0_RTH_GEN_ALG_SEL(algorithm); in vxge_hw_vpath_rts_rth_set()
/linux-4.1.27/Documentation/power/
Dbasic-pm-debugging.txt157 in accordance with the algorithm:
/linux-4.1.27/Documentation/locking/
Drt-mutex-design.txt16 inheritance (PI) algorithm that is used, as well as reasons for the
89 algorithm. These locks disable preemption for UP (when
700 algorithm needs to be careful. This is because the current process is
Dww-mutex-design.txt26 The algorithm that the TTM graphics subsystem came up with for dealing with
/linux-4.1.27/Documentation/block/
Dbiodoc.txt224 iii. The i/o scheduler algorithm itself can be replaced/set as appropriate
231 i/o scheduling algorithm aspects and details outside of the generic loop.
983 The generic i/o scheduler algorithm attempts to sort/merge/batch requests for
1014 Plugging is an approach that the current i/o scheduling algorithm resorts to so
/linux-4.1.27/Documentation/scsi/
DChangeLog.sym53c8xx337 - Simpler algorithm to deal with SCSI command starvation.
345 algorithm (from Stefan Esser) is better than 2%, this should
DChangeLog.ncr53c8xx441 - New CCB starvation avoiding algorithm.
DChangeLog.megaraid365 is free to change its mapping algorithm in the future if necessary .."
Dst.txt423 used as the compression algorithm. The value
/linux-4.1.27/sound/oss/
DCHANGELOG154 - Changed audio buffer partitioning algorithm so that it selects
/linux-4.1.27/Documentation/devicetree/bindings/thermal/
Dthermal.txt11 not about how the system must control or which algorithm or policy
/linux-4.1.27/Documentation/sound/oss/
DREADME.OSS58 Rob Hooft Volume computation algorithm for the FM synth.
61 Greg Lee Volume computation algorithm for the GUS and
1064 DSP algorithm which is used to for the general MIDI emulation. The
1065 algorithm file (.ld) is read by the config program and written to a
/linux-4.1.27/drivers/staging/rtl8723au/os_dep/
Dioctl_cfg80211.c410 psetstakey_para->algorithm = psta->dot118021XPrivacy; in set_pairwise_key()
453 psetkeyparm->algorithm = alg; in set_group_key()
/linux-4.1.27/Documentation/cgroups/
Dmemory.txt250 The reclaim algorithm has not been modified for cgroups, except that
608 limit, the reclaim algorithm reclaims from the tasks in the ancestor and the
/linux-4.1.27/arch/x86/math-emu/
DREADME60 (2) Divide has been tuned to get reasonable performance. The algorithm
/linux-4.1.27/drivers/staging/rtl8188eu/os_dep/
Dioctl_linux.c2135 psetstakey_para->algorithm = (u8)psta->dot118021XPrivacy; in set_pairwise_key()
2174 psetkeyparm->algorithm = alg; in set_group_key()
/linux-4.1.27/mm/
DKconfig461 for clean pages that the kernel's pageframe replacement algorithm
/linux-4.1.27/Documentation/isdn/
DREADME209 Bit 0: 0 = Use delayed tty-send-algorithm
/linux-4.1.27/Documentation/mtd/
Dnand_ecc.txt686 The algorithm itself is pretty straightforward. Just xor the given and
/linux-4.1.27/arch/arm/mm/
DKconfig768 bool "Round robin I and D cache replacement algorithm"
/linux-4.1.27/Documentation/x86/
Dboot.txt730 The kernel runtime start address is determined by the following algorithm:
/linux-4.1.27/net/netfilter/
DKconfig981 what packets. The work-load sharing algorithm is based on source
/linux-4.1.27/arch/x86/crypto/
Daesni-intel_asm.S1136 # middle section of the temp results combined as in karatsuba algorithm
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt1161 internal algorithm, usually based on readings from the thermal sensors.