u-boot.git/drivers/fastboot, branch v2021.04

fastboot: add UUU command UCmd and ACmd support

2021-02-26T14:30:55Z

add support for the UUU commands ACmd and UCmd. Enable them through the Kconfig option CONFIG_FASTBOOT_UUU_SUPPORT base was commit in NXP kernel 9b149c2a2882: ("MLK-18591-3 android: Add FSL android fastboot support") and ported it to current mainline. Tested this patch on imx6ul based board. Signed-off-by: Heiko Schocher Acked-by: Patrick Delaunay

fastboot: Allow u-boot-style partitions

2021-02-26T14:30:55Z

This adds support for partitions of the form "dev.hwpart:part" and "dev#partname". This allows one to flash to eMMC boot partitions without having to use CONFIG_FASTBOOT_MMC_BOOT1_SUPPORT. It also allows one to flash to an entire device without needing CONFIG_FASTBOOT_MMC_USER_NAME. Lastly, one can also flash MMC devices other than CONFIG_FASTBOOT_FLASH_MMC_DEV. Because devices can be specified explicitly, CONFIG_FASTBOOT_FLASH_MMC_DEV is used only when necessary for existing functionality. For those cases, fastboot_mmc_get_dev has been added as a helper function. This allows There should be no conflicts with the existing system, but just in case, I have ordered detection of these names after all existing names. The fastboot_mmc_part test has been updated for these new names. Signed-off-by: Sean Anderson Reviewed-by: Simon Glass

fastboot: Move part_get_info_by_name_or_alias after raw_part_get_info_by_name

2021-02-26T14:30:55Z

This makes the next commit more readable by doing the move now. Signed-off-by: Sean Anderson Reviewed-by: Simon Glass

fastboot: Remove mmcpart argument from raw_part_get_info_by_name

2021-02-26T14:30:55Z

The only thing mmcpart was used for was to pass to blk_dselect_hwpart. This calls blk_dselect_hwpart directly from raw_part_get_info_by_name. The error handling is dropped, but it is reintroduced in the next commit (albeit less specificly). Signed-off-by: Sean Anderson Reviewed-by: Simon Glass

fastboot: reinit partition after storing GPT or MBR

2021-02-07T18:22:55Z

In case MMC has MBR system and fastboot writes GPT, MMC is still recognized as MBR. Invoke part_init() to purge cached data and update information about partition table type. Signed-off-by: Roman Stratiienko

fastboot: add command to select the eMMC boot configuration

2021-02-07T18:22:55Z

Add command oem bootbus which executes the command ``mmc bootbus `` on the current fastboot mmc device ( = CONFIG_FASTBOOT_FLASH_MMC_DEV) to set the eMMC boot configuration on first update, with = boot_bus_width reset_boot_bus_width boot_mode $> fastboot oem bootbus: Signed-off-by: Patrick Delaunay

fastboot: add command to select the default emmc hwpart for boot

2021-02-07T18:22:55Z
Add fastboot command oem partconf which executes the command ``mmc partconf 0`` on the current mmc device to configure the eMMC boot partition with : boot_ack boot_partition, so the command is: $> fastboot oem partconf: The partition_access argument is forced to 0 (userdata) Signed-off-by: Patrick Delaunay [lukma - Kconfig adjustments after merging this patch]

fastboot: mmc: extend flash/erase for both emmc hwpart 1 and 2

2021-02-07T18:22:55Z
Update the code and the configs for eMMC boot and userdata partitions acces - FASTBOOT_MMC_BOOT_SUPPORT: boot partition 1 and 2 (erase/write) - FASTBOOT_MMC_BOOT1_NAME: boot partition 1, default name="mmc0boot0" - FASTBOOT_MMC_BOOT2_NAME: boot partition 2, default name="mmc0boot1" This patch also removes the unnecessary dependency with ARCH_MEDIATEK and EFI_PARTITION. Signed-off-by: Patrick Delaunay

fastboot: mmc: Add CONFIG_FASTBOOT_MMC_USER_SUPPORT

2021-02-07T18:22:55Z
Split userdata and boot partition support for eMMC update and correct the description (update is supported). The new configuration CONFIG_FASTBOOT_MMC_USER_SUPPORT allows to activate support of userdata partition update, based on target name=CONFIG_FASTBOOT_MMC_USER_NAME This patch also removes the unnecessary dependency with ARCH_MEDIATEK and EFI_PARTITION. Signed-off-by: Patrick Delaunay

fastboot: Implement generic fastboot_set_reboot_flag

2021-02-07T18:22:54Z
It is possible to implement fastboot_set_reboot_flag in a generic way if BCB commands are turned on for a target. Using bcb_set_reboot_reason allows to do this by simply passing string with correct reboot reason that should be handled during next boot process. If BCB are turned off, then bcb_set_reboot_reason would simply return error, so it won't introduce any new behaviour for such targets. Signed-off-by: Roman Kovalivskyi