With the recent addition of a generic device_detect for MCI devices, the MCI_STARTUP help text is no longer accurate. Reword it, but leave the option as-is as some boards may be broken if we drop the option (e.g. because they still depend on a probe order or call default_environment_path_set, but don't explicitly detect the device). Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> --- drivers/mci/Kconfig | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/mci/Kconfig b/drivers/mci/Kconfig index 60c60ceaa527..6ae1e812528c 100644 --- a/drivers/mci/Kconfig +++ b/drivers/mci/Kconfig @@ -12,12 +12,12 @@ if MCI comment "--- Feature list ---" config MCI_STARTUP - bool "Probe on system start" + bool "Force probe on system start" help - Say 'y' here if the MCI framework should probe for attached MCI cards - on system start up. This is required if the card carries barebox's - environment (for example on systems where the MCI card is the sole - bootmedia). Otherwise probing run on demand with "mci*.probe=1" + Say 'y' here if the MCI framework should always probe for all attached + MCI cards on system start up. This may required for some legacy boards. + When this is 'n', probing happens on demand either with "mci*.probe=1" + or with driver/board code calling device_detect. config MCI_INFO bool "MCI Info" -- 2.26.2 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
