On Wed, Dec 30, 2020 at 10:34 AM Fabio Estevam festevam@gmail.com wrote:
On Wed, Dec 30, 2020 at 1:29 PM Adam Ford aford173@gmail.com wrote:
In the meantime, would you be opposed to this patch since other imx8m kits have the equivalent patch already applied? They could be removed if/when the esdhc driver gets updated.
I am not opposed to this patch, but would be nice if the U-Boot esdhc driver could be changed to behave like the kernel one.
I just sent an RFC [1] for change that uses the esdhc_soc_data flags to determine whether or not the function/feature is present in the controller and checks to see if the function is enabled from Kconfig.
I was able to remove the u-boot.dtsi changes that I previously pushed, and I was able to see that the eMMC device is running at HS400_ES (200MHz)
u-boot=> mmc dev 2 switch to partitions #0, OK mmc2(part 0) is current device u-boot=> mmc info Device: FSL_SDHC Manufacturer ID: 45 OEM: 100 Name: DG403 Bus Speed: 200000000 Mode: HS400ES (200MHz) Rd Block Len: 512 MMC version 5.1 High Capacity: Yes Capacity: 29.1 GiB Bus Width: 8-bit DDR Erase Group Size: 512 KiB HC WP Group Size: 8 MiB User Capacity: 29.1 GiB WRREL Boot Capacity: 4 MiB ENH RPMB Capacity: 4 MiB ENH Boot area 0 is not write protected Boot area 1 is not write protected u-boot=>
[1] - https://patchwork.ozlabs.org/project/uboot/patch/20201230173907.2891555-1-af...