#
# MobiCore configuration
#
config MOBICORE_DRIVER
	tristate "MobiCore Driver"
	depends on ARM
	---help---
	  Enable Linux Kernel MobiCore Support
	  This option enables MobiCore Driver which is used to communicate with
	  TEE OS, for things like, setting up log buffers, interrupt pins,
	  and IPC channels.

config MOBICORE_DEBUG
	bool "MobiCore Module debug mode"
	depends on MOBICORE_DRIVER
	---help---
	  Enable Debug mode in the MobiCore Driver.
	  MobiCore Driver has loglevel control thru DEBUG and VERBOSE
	  This option enables MCDRV_DBG() macros to print useful debugging
	  information about mobicore operations.

config MOBICORE_VERBOSE
	bool "MobiCore Module verbose debug mode"
	depends on MOBICORE_DEBUG
	---help---
	  Enable Verbose Debug mode in the MobiCore Driver.
	  It enables MCDRV_DBG_VERBOSE() macros to print extra information
	  about mobicore operations. Beware: this is only useful for
	  debuging deep in the driver because it prints too much logs

config MOBICORE_API
	tristate "Linux MobiCore API"
	depends on MOBICORE_DRIVER
	---help---
	  Enable Linux Kernel MobiCore API
	  This option enables MobiCore Driver which is used to communicate with
	  TEE OS, for things like, setting up log buffers, interrupt pins,
	  and IPC channels.

config TRUSTONIC_TRUSTED_UI
	tristate "<t-base TUI"
	depends on MOBICORE_API
	---help---
	  Enable <t-base Trusted User Interface
	  Trustonic TUI features was based on Trustonic TEE mechanism to protect
	  Touch/Display inside TEE, to prevent malicious access of sensitive data
	  used by APPs like Banking.

# TODO: Obsolete, to-be-removed
#config TRUSTONIC_TRUSTED_UI_FB_BLANK
#	bool "<t-base TUI with fb_blank"
#	depends on TRUSTONIC_TRUSTED_UI
#	---help---
#	  Blank the framebuffer before starting a TUI session
