drivers/crypto/amlogic/Kconfig

Source file repositories/reference/linux-study-clean/drivers/crypto/amlogic/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/crypto/amlogic/Kconfig
Extension: [no extension]
Size: 797 bytes
Lines: 26
Domain: Driver Families
Bucket: drivers/crypto
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

config CRYPTO_DEV_AMLOGIC_GXL
	tristate "Support for amlogic cryptographic offloader"
	depends on HAS_IOMEM
	default m if ARCH_MESON
	select CRYPTO_SKCIPHER
	select CRYPTO_ENGINE
	select CRYPTO_ECB
	select CRYPTO_CBC
	select CRYPTO_AES
	help
	  Select y here to have support for the cryptographic offloader
	  available on Amlogic GXL SoC.
	  This hardware handles AES ciphers in ECB/CBC mode.

	  To compile this driver as a module, choose M here: the module
	  will be called amlogic-gxl-crypto.

config CRYPTO_DEV_AMLOGIC_GXL_DEBUG
	bool "Enable amlogic stats"
	depends on CRYPTO_DEV_AMLOGIC_GXL
	depends on DEBUG_FS
	help
	  Say y to enable amlogic-crypto debug stats.
	  This will create /sys/kernel/debug/gxl-crypto/stats for displaying
	  the number of requests per flow and per algorithm.

Annotation

Atlas domain: Driver Families / drivers/crypto.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.