michaelh/zephyr
1
0
Fork 0
Code Releases Activity

display: introduce CONFIG_DISPLAY_INIT_PRIORITY

Browse source 
This introduces a new kconfig CONFIG_DISPLAY_INIT_PRIORITY
to specify the initialization priority for display devices.
Most of the display devices are using APPLICATION and
CONFIG_APPLICATION_INIT_PRIORITY which is not entirely
appropriate for devices. Due to linking order, the display
device may be initialized after application code at same
init level and priority. This results in the display device
not ready to be used for application code. So this kconfig
option allows the display devices to be initialized earlier
if needed.

For the drivers using CONFIG_APPLICATION_INIT_PRIORITY,
they have been changed to use CONFIG_DISPLAY_INIT_PRIORITY
instead.

Note that the default value for CONFIG_DISPLAY_INIT_PRIORITY
is the same as CONFIG_APPLICATION_INIT_PRIORITY at 90 to
avoid any functional changes.

Signed-off-by: Daniel Leung <daniel.leung@intel.com>
This commit is contained in:
Daniel Leung 2021-08-11 09:23:50 -07:00 • committed by Carles Cufí
commit 8b8e8f99ba
11 changed files with 16 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

2
drivers/display/ls0xx.c
View file

@ -340,5 +340,5 @@ static struct display_driver_api ls0xx_driver_api = {
DEVICE_DT_INST_DEFINE(0, ls0xx_init, NULL,
&ls0xx_driver, &ls0xx_config,
POST_KERNEL, CONFIG_APPLICATION_INIT_PRIORITY,
POST_KERNEL, CONFIG_DISPLAY_INIT_PRIORITY,
&ls0xx_driver_api);