Home
last modified time | relevance | path

Searched refs:IV (Results 1 – 25 of 31) sorted by relevance

12

/linux/tools/perf/scripts/perl/Perf-Trace-Util/
H A DContext.c47 XSprePUSH; PUSHi((IV)RETVAL); in XS()
70 XSprePUSH; PUSHi((IV)RETVAL); in XS()
93 XSprePUSH; PUSHi((IV)RETVAL); in XS()
/linux/Documentation/admin-guide/device-mapper/
H A Ddm-crypt.rst17 Encryption cipher, encryption mode and Initial Vector (IV) generator.
30 format (selected by capi: prefix). The IV specification is the same
58 keys (for example IV seed) so the key contains more parts concatenated
82 The IV offset is a sector count that is added to the sector number
83 before creating the IV.
142 The <type> can be "none" if metadata is used only for persistent IV.
147 used for storing authentication tag (and persistent IV if needed).
160 IV generators will use sector number counted in <sector_size> units
163 For example, if <sector_size> is 4096 bytes, plain64 IV for the second
/linux/drivers/zorro/
H A Dzorro.ids322 1500 Picasso IV Z2 RAM [Graphics Card]
323 1600 Picasso IV Z2 RAM [Graphics Card]
324 1700 Picasso IV Z2 [Graphics Card]
325 1800 Picasso IV Z3 [Graphics Card]
413 0100 AMax II/IV [Macintosh Emulator]
417 0600 Blizzard 1220-IV [Accelerator]
422 1100 Blizzard 1230-IV/1260 [Accelerator]
/linux/Documentation/hwmon/
H A Dw83627ehf.rst150 * 5 "Smart Fan IV" mode
154 SmartFan IV mode is configurable only if it was configured at system
156 SmartFan IV operational parameters can not be configured at this time,
157 and the various pwm attributes are not used in SmartFan IV mode.
160 returned when reading pwm attributes is unrelated to SmartFan IV
H A Dnct6775.rst156 * 5 "Smart Fan IV" mode
245 Smart Fan IV mode (5)
/linux/Documentation/userspace-api/media/mediactl/
H A Dmedia-controller.rst7 Part IV - Media Controller API
/linux/Documentation/crypto/
H A Dapi-samples.rst21 u8 iv[16]; /* AES-256-XTS takes a 16-byte IV */
61 /* Initialize the IV */
H A Duserspace-if.rst159 should be processed for encryption or decryption. In addition, the IV is
174 - specification of the IV information marked with the flag ALG_SET_IV
218 should be processed for encryption or decryption. In addition, the IV is
233 - specification of the IV information marked with the flag ALG_SET_IV
/linux/Documentation/translations/zh_CN/filesystems/
H A Dgfs2-glocks.rst39 UN IV/NL 未加锁（无关联的 DLM 锁）或 NL
/linux/arch/x86/crypto/
H A Daes-xts-avx-x86_64.S842 .set IV, %rsi define
846 vmovdqu (IV), %xmm0
863 vmovdqu %xmm0, (IV)
/linux/tools/power/cpupower/bindings/python/
H A DREADME83 John B. Wyatt IV
/linux/arch/arm64/crypto/
H A Daes-modes.S324 IV .req x5
336 ld1 {vctr.16b}, [IV]
474 st1 {vctr.16b}, [IV] /* return next CTR value */
577 .unreq IV
/linux/arch/arm64/boot/dts/qcom/
H A Dsm8450-sony-xperia-nagara-pdx224.dts12 model = "Sony Xperia 5 IV";
H A Dsm8450-sony-xperia-nagara-pdx223.dts12 model = "Sony Xperia 1 IV";
H A Dsm6375-sony-xperia-murray-pdx225.dts21 model = "Sony Xperia 10 IV";
/linux/Documentation/arch/powerpc/
H A Dqe_firmware.rst16 IV - Microcode Programming Details
57 IV - Microcode Programming Details
/linux/Documentation/i2c/busses/
H A Di2c-ali15x3.rst67 * "Aladdin IV" includes the M1541 Socket 7 North bridge
/linux/drivers/gpu/drm/nouveau/nvkm/engine/sec/fuc/
H A Dg98.fuc0s438 // init key, IV
502 // pull updated IV
/linux/Documentation/admin-guide/media/
H A Dbttv-cardlist.rst478 - Teppro TEV-560/InterVision IV-560
H A Dbttv.rst1372 - Intervision IV-510 (capture only bt8x8)
1373 - Intervision IV-550 (bt8x8)
1374 - Intervision IV-100 (zoran)
1375 - Intervision IV-1000 (bt8x8)
1396 - TEPPRO IV-550 (For BT848 Main Chip)
/linux/tools/perf/Documentation/
H A Djitdump-specification.txt51 IV/ Record header
/linux/Documentation/networking/
H A Dudplite.rst92 A detailed discussion of UDP-Lite checksum coverage options is in section IV.
/linux/arch/arm/crypto/
H A Daes-ce-core.S494 @ Encrypt the IV in q0 with the second AES key. This should only
/linux/drivers/net/wireless/broadcom/brcm80211/brcmsmac/
H A Dd11.h763 u8 IV[16]; /* 0x0b - 0x12 */ member
/linux/Documentation/power/
H A Dfreezing-of-tasks.rst112 IV. Why do we do that?

12