a cryptography engine
Every time you load a web page over HTTPS, your device is encrypting and decrypting a torrent of data — scrambling it so eavesdroppers see only gibberish, then unscrambling it for you. The math behind this (ciphers like AES, hashes like SHA-256) is fixed, well-defined, and runs on essentially every byte that crosses the network or goes to disk. A cryptography engine is a hardware block built to do exactly that math — encryption, decryption, hashing — far faster and more efficiently than a general CPU can.
Concretely, a crypto engine is a small fixed-function accelerator wired to compute a standard algorithm directly in logic. Take AES encryption: in software it takes many CPU instructions per block (substitutions, shifts, and mixing repeated over several 'rounds'); a hardware AES engine performs an entire round in a single dedicated circuit, so it encrypts a block in a handful of cycles. The CPU just hands the engine a key and a block of data and collects the ciphertext. Because the algorithm never changes, there is no reason to keep it in slow, general-purpose form — the engine is the textbook case for fixing a stable, high-volume operation in silicon. Modern CPUs even fold simple crypto in as dedicated instructions (like the AES-NI instructions on x86).
Why it matters beyond speed: a hardware crypto engine is faster, dramatically lower-energy (important when every packet and every disk write is encrypted by default), and can be made more secure — because keys can live inside the engine and never be exposed to general software, and a careful hardware implementation can resist timing side-channel attacks that a naive software version leaks through. The honest caveat is that 'in hardware' does not automatically mean 'secure': a poorly designed engine can still leak secrets through power or timing side channels, and a fixed engine cannot be patched if the algorithm itself is later broken.
Full-disk encryption writes every block to storage encrypted. With a hardware AES engine the phone does this transparently with negligible battery cost; doing the same AES in software would consume noticeably more CPU and power on every single read and write — which is why dedicated crypto hardware is standard in modern SoCs.
A crypto engine fixes a stable, high-volume algorithm in silicon: faster, far lower-energy, and able to guard keys.
Doing crypto in hardware is not automatically secure — a careless engine can still leak keys via power or timing side channels, and a hard-wired algorithm cannot be updated if it is later broken.