[U-Boot] [PATCHv2 1/4] dm: MIGRATION: Add migration plan for DM_MMC

[Simon Goldschmidt]

On 29.11.2018 20:12, Tom Rini wrote:
> Given that at this point the MMC subsystem itself has been migrated
> along with a number of subsystem drivers, formalize a deadline for
> migration.
>
> Cc: Simon Glass <sjg at chromium.org>
> Cc: Jaehoon Chung <jh80.chung at samsung.com>
> Signed-off-by: Tom Rini <trini at konsulko.com>
> ---
> Changes in v2:
> - Note that failure to migration may lead to removal.
> ---
>   Makefile                       | 8 ++++++++
>   doc/driver-model/MIGRATION.txt | 9 +++++++++
>   2 files changed, 17 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index a4b1d1db5241..0ab48f9ac97f 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -920,6 +920,14 @@ ifeq ($(CONFIG_DM_I2C_COMPAT)$(CONFIG_SANDBOX),y)
>   	@echo "before sending patches to the mailing list."
>   	@echo "===================================================="
>   endif
> +ifneq ($(CONFIG_DM_MMC)$(CONFIG_OF_CONTROL)$(CONFIG_BLK),yyy)

This might not be a too widespread use of U-Boot, but I do have one 
configuration that boots from FPGA and loads Linux via TFTP. Due to size 
constraints in FPGA onchip RAM, I have MMC disabled completely. This 
patch gives me a warning in this case.

I can live with that as I know I have MMC disabled and don't this 
warning for my other configs though. Just wanted to let you know, as you 
complained about getting no replies to this thread ;-)

Simon

> +	@echo "===================== WARNING ======================"
> +	@echo "This board does not use CONFIG_DM_MMC. Please update"
> +	@echo "the board to use CONFIG_DM_MMC before the v2019.04 release."
> +	@echo "Failure to update by the deadline may result in board removal."
> +	@echo "See doc/driver-model/MIGRATION.txt for more info."
> +	@echo "===================================================="
> +endif
>   	@# Check that this build does not use CONFIG options that we do not
>   	@# know about unless they are in Kconfig. All the existing CONFIG
>   	@# options are whitelisted, so new ones should not be added.
> diff --git a/doc/driver-model/MIGRATION.txt b/doc/driver-model/MIGRATION.txt
> index 5ebefd608b99..71c26571828a 100644
> --- a/doc/driver-model/MIGRATION.txt
> +++ b/doc/driver-model/MIGRATION.txt
> @@ -5,6 +5,15 @@ U-Boot has been migrating to a new driver model since its introduction in
>   2014. This file describes the schedule for deprecation of pre-driver-model
>   features.
>   
> +CONFIG_DM_MMC
> +-------------
> +
> +Status: In progress
> +Deadline: 2019.04
> +
> +The subsystem itself has been converted and maintainers should submit patches
> +switching over to using CONFIG_DM_MMC and other base driver model options in
> +time for inclusion in the 2019.04 rerelease.
>   
>   CONFIG_BLK
>   ----------