soc: rockchip: add cpuinfo support

[firefly-linux-kernel-4.4.55.git] / drivers / md / Kconfig

diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
index 7913fdcfc8496bdd7c719a8c3334f6136c74eced..3d237a03dab3dbd2ead85526a76e8ddcf9271f2d 100644 (file)
--- a/drivers/md/Kconfig
+++ b/drivers/md/Kconfig
@@ -458,6 +458,33 @@ config DM_VERITY
 
          If unsure, say N.
 
+config DM_VERITY_HASH_PREFETCH_MIN_SIZE_128
+       bool "Prefetch size 128"
+
+config DM_VERITY_HASH_PREFETCH_MIN_SIZE
+       int "Verity hash prefetch minimum size"
+       depends on DM_VERITY
+       range 1 4096
+       default 128 if DM_VERITY_HASH_PREFETCH_MIN_SIZE_128
+       default 1
+       ---help---
+         This sets minimum number of hash blocks to prefetch for dm-verity.
+         For devices like eMMC, having larger prefetch size like 128 can improve
+         performance with increased memory consumption for keeping more hashes
+         in RAM.
+
+config DM_VERITY_FEC
+       bool "Verity forward error correction support"
+       depends on DM_VERITY
+       select REED_SOLOMON
+       select REED_SOLOMON_DEC8
+       ---help---
+         Add forward error correction support to dm-verity. This option
+         makes it possible to use pre-generated error correction data to
+         recover from corrupted blocks.
+
+         If unsure, say N.
+
 config DM_SWITCH
        tristate "Switch target support (EXPERIMENTAL)"
        depends on BLK_DEV_DM
@@ -488,4 +515,22 @@ config DM_LOG_WRITES
 
          If unsure, say N.
 
+config DM_ANDROID_VERITY
+       tristate "Android verity target support"
+       depends on DM_VERITY
+       depends on X509_CERTIFICATE_PARSER
+       depends on SYSTEM_TRUSTED_KEYRING
+       depends on PUBLIC_KEY_ALGO_RSA
+       depends on KEYS
+       depends on ASYMMETRIC_KEY_TYPE
+       depends on ASYMMETRIC_PUBLIC_KEY_SUBTYPE
+       depends on MD_LINEAR
+       select DM_VERITY_HASH_PREFETCH_MIN_SIZE_128
+       ---help---
+         This device-mapper target is virtually a VERITY target. This
+         target is setup by reading the metadata contents piggybacked
+         to the actual data blocks in the block device. The signature
+         of the metadata contents are verified against the key included
+         in the system keyring. Upon success, the underlying verity
+         target is setup.
 endif # MD