subsys: kconfig: Remove 'default n' properties and clean up a bit
Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
This commit is contained in:
parent
15bc615b5b
commit
1073882998
48 changed files with 117 additions and 416 deletions
|
@ -7,22 +7,18 @@
|
|||
menu "Disk"
|
||||
|
||||
config DISK_ACCESS
|
||||
bool
|
||||
default n
|
||||
prompt "Enable Disk Interface"
|
||||
bool "Enable Disk Interface"
|
||||
help
|
||||
Enable disk access over a supported media backend like FLASH or RAM
|
||||
|
||||
config DISK_ACCESS_MAX_VOLUMES
|
||||
int
|
||||
int "Maximum Disk Interfaces"
|
||||
default 8
|
||||
prompt "Maximum Disk Interfaces"
|
||||
help
|
||||
Maximum number of disk access interfaces supported
|
||||
|
||||
config SYS_LOG_DISK_LEVEL
|
||||
int
|
||||
prompt "Disk log level"
|
||||
int "Disk log level"
|
||||
depends on SYS_LOG
|
||||
default 0
|
||||
help
|
||||
|
@ -54,8 +50,7 @@ endif # DISK_ACCESS
|
|||
if DISK_ACCESS_RAM
|
||||
|
||||
config DISK_RAM_VOLUME_NAME
|
||||
string
|
||||
prompt "RAM Disk mount point or drive name"
|
||||
string "RAM Disk mount point or drive name"
|
||||
default "RAM"
|
||||
help
|
||||
Disk name as per file system naming guidelines.
|
||||
|
@ -65,48 +60,41 @@ endif # DISK_ACCESS_RAM
|
|||
if DISK_ACCESS_FLASH
|
||||
|
||||
config DISK_FLASH_VOLUME_NAME
|
||||
string
|
||||
prompt "Flash mount point or drive name"
|
||||
string "Flash mount point or drive name"
|
||||
default "NAND"
|
||||
help
|
||||
Disk name as per file system naming guidelines.
|
||||
|
||||
config DISK_FLASH_DEV_NAME
|
||||
string
|
||||
prompt "Flash device name to be used as storage backend"
|
||||
string "Flash device name to be used as storage backend"
|
||||
|
||||
config DISK_FLASH_START
|
||||
hex
|
||||
prompt "Flash device start address in hex"
|
||||
hex "Flash device start address in hex"
|
||||
help
|
||||
This is start address of the flash to be used as storage backend.
|
||||
|
||||
config DISK_FLASH_MAX_RW_SIZE
|
||||
int
|
||||
prompt "Flash device max read-write size in decimal"
|
||||
int "Flash device max read-write size in decimal"
|
||||
help
|
||||
This is the maximum number of bytes that the
|
||||
flash_write API can accept per invocation.
|
||||
API.
|
||||
|
||||
config DISK_FLASH_ERASE_ALIGNMENT
|
||||
hex
|
||||
prompt "Flash device erase alignment in hex"
|
||||
hex "Flash device erase alignment in hex"
|
||||
help
|
||||
This is the start address alignment required by
|
||||
the flash component.
|
||||
|
||||
config DISK_ERASE_BLOCK_SIZE
|
||||
hex
|
||||
prompt "Flash device erasable block size in hex"
|
||||
hex "Flash device erasable block size in hex"
|
||||
help
|
||||
This is typically the minimum block size that
|
||||
is erased at one time in flash storage.
|
||||
Typically it is equal to the flash memory page size.
|
||||
|
||||
config DISK_VOLUME_SIZE
|
||||
hex
|
||||
prompt "Flash device volume size in hex"
|
||||
hex "Flash device volume size in hex"
|
||||
help
|
||||
This is the file system volume size in bytes.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue