boards: board_app_initialize() don't return early on failure

- depending on the situation we're more likely to get actionable user
feedback by allowing boot to complete rather than silently failing
This commit is contained in:
Daniel Agar
2021-12-09 20:41:54 -05:00
parent 08ee3208b2
commit 8185e2a384
42 changed files with 7 additions and 110 deletions
-4
View File
@@ -345,7 +345,6 @@ __EXPORT int board_app_initialize(uintptr_t arg)
// if (!spi1) {
// syslog(LOG_ERR, "[boot] FAILED to initialize SPI port %d\n", CONFIG_NSH_MMCSDSPIPORTNO);
// led_off(LED_BLUE);
// return -ENODEV;
// }
// /* Now bind the SPI interface to the MMCSD driver */
@@ -354,7 +353,6 @@ __EXPORT int board_app_initialize(uintptr_t arg)
// if (result != OK) {
// led_off(LED_BLUE);
// syslog(LOG_ERR, "[boot] FAILED to bind SPI port 1 to the MMCSD driver\n");
// return -ENODEV;
// }
// up_udelay(20);
@@ -365,7 +363,6 @@ __EXPORT int board_app_initialize(uintptr_t arg)
if (!spi2) {
syslog(LOG_ERR, "[boot] FAILED to initialize SPI port 2\n");
led_off(LED_BLUE);
return -ENODEV;
}
/* Default SPI2 to 1MHz and de-assert the known chip selects. */
@@ -386,7 +383,6 @@ __EXPORT int board_app_initialize(uintptr_t arg)
// if (result != OK) {
// syslog(LOG_ERR, "[boot] FAILED to init params in FLASH %d\n", result);
// led_off(LED_AMBER);
// return -ENODEV;
// }
// #endif