bcm63xx/u-boot/drivers/mmc/omap_hsmmc.c, branch master

mmc: omap_hsmmc: Set 3.3V for IO voltage

2019-04-12T12:05:57Z

Pbias voltage should match the IO voltage set for the SD card. With the latest pbias change to 3.3V, update the capabilities and IO voltages settings to 3.3V. Signed-off-by: Faiz Abbas

Merge tag 'dm-pull-10feb19' of git://git.denx.de/u-boot-dm

2019-02-10T13:11:32Z

Samsung sound patches (applied for Samsung maintainer) Common sound support buildman environment support of-platdata documentation improvements

mmc: omap_hsmmc: Use regulator_set_enable_if_allowed for enabling regulator

2019-02-09T19:50:22Z

Use regulator_set_enable_if_allowed() api instead of regulator_set_enable() while enabling io regulators. This way the driver doesn't see an error when disabling an always-on regulator and when enabling is not supported. Reviewed-by: Simon Glass Signed-off-by: Lokesh Vutla

mmc: omap_hsmmc: Workaround errata regarding SDR104/HS200 tuning failures (i929)

2019-02-09T12:50:58Z

Errata i929 in certain OMAP5/DRA7XX/AM57XX silicon revisions (SPRZ426D - November 2014 - Revised February 2018 [1]) mentions unexpected tuning pattern errors. A small failure band may be present in the tuning range which may be missed by the current algorithm. Furthermore, the failure bands vary with temperature leading to different optimum tuning values for different temperatures. As suggested in the related Application Report (SPRACA9B - October 2017 - Revised July 2018 [2]), tuning should be done in two stages. In stage 1, assign the optimum ratio in the maximum pass window for the current temperature. In stage 2, if the chosen value is close to the small failure band, move away from it in the appropriate direction. References: [1] http://www.ti.com/lit/pdf/sprz426 [2] http://www.ti.com/lit/pdf/SPRACA9 Signed-off-by: Faiz Abbas

mmc: omap: Surround DM_FLAG_PRE_RELOC flag with OF_CONTROL check

2018-11-14T17:16:28Z

When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be bound before relocation. However due to a bug in the DM core, the flag only takes effect when devices are statically declared via U_BOOT_DEVICE(). This bug has been fixed recently by commit "dm: core: Respect drivers with the DM_FLAG_PRE_RELOC flag in lists_bind_fdt()", but with the fix, it has a side effect that all existing drivers that declared DM_FLAG_PRE_RELOC flag will be bound before relocation now. This may expose potential boot failure on some boards due to insufficient memory during the pre-relocation stage. To mitigate this potential impact, the following changes are implemented: - Remove DM_FLAG_PRE_RELOC flag in the driver, if the driver only supports configuration from device tree (OF_CONTROL) - Keep DM_FLAG_PRE_RELOC flag in the driver only if the device is statically declared via U_BOOT_DEVICE() - Surround DM_FLAG_PRE_RELOC flag with OF_CONTROL check, for drivers that support both statically declared devices and configuration from device tree Signed-off-by: Bin Meng Reviewed-by: Simon Glass

mmc: omap_mmc: Remove invert references

2018-09-29T12:06:56Z

With DM_GPIO and DM_MMC translating GPIO_ACTIVE_LOW, any boards using the 'cd-invert' option will no longer need to do this. This patch removes the support for 'invert' from the MMC driver. Signed-off-by: Adam Ford [trini: Fix warning over when !DM_GPIO] Signed-off-by: Tom Rini

mmc: omap_hsmmc: Fix pbias for omap3_logic to enable CD pin

2018-09-26T01:49:18Z

The MMC card detect pin is connected to gpio127 on omap3_logic. When setting up the pbias register for MMC, let's also enable gpio_127 for the card detect. As part of the package deal, gpio_126 and gpio_129 are also enabled. Signed-off-by: Adam Ford

mmc: omap_hsmmc: Make DM_GPIO calls dependent on DM_GPIO

2018-09-12T01:39:11Z

The getcd and getwp functions when DM_MMC is enabled are assumming the DM_GPIO is enabled. In cases (like SPL) where DM_GPIO may not be enabled, wrap these calls in an #ifdef Signed-off-by: Adam Ford

mmc: omap_hsmmc: use a default 52MHz max clock rate if none is specified

2018-02-26T01:52:15Z

mmc_of_parse() doesn't set a default value if none is available in DT. In that case, use a default 52MHz clock rate. Signed-off-by: Alex Kiernan Signed-off-by: Jean-Jacques Hiblot Tested-by: Adam Ford Reviewed-by: Tom Rini

mmc: omap_hsmmc: make it possible to compile out ADMA support

2018-02-26T01:52:15Z

Some platforms don't have ADMA controllers. For those platforms, compiling it out reduces the size of the binary by about 600 bytes. Leaving the support in doesn't break things as the driver checks at runtime if the ADMA2 controller is present. Signed-off-by: Jean-Jacques Hiblot Tested-by: Adam Ford Reviewed-by: Tom Rini