This document describes how to test that setting a fixed drive strength for eMMC works properly.
Kernel Version and Configuration
Support for this feature is expected to land upstream in v4.15. It is currently available in a topic branch:
It is critical that CONFIG_MMC_SDHI is enabled for these tests. Also, the kernel command line from the device tree should be used for proper setup of the dyndbg variable by specifiying dyndbg="file drivers/mmc/core/* +p". A branch already prepared for that is:
All debug messages examined in this test are automatically created during boot. There is no need to trigger the messages by some event.
- Salvator-XS/r8a7795 (R-Car H3 ES2.0 SoC) with on-board eMMC.
Here is some background to understanding the debug output. The reference document is the JEDEC eMMC standard v5.1.
To select the drive strength, CMD6 (SWITCH) is used to modify the EXT_CSD, see chapter 6.6.1. The bit pattern for CMD6 can be found in chapter 6.10.4. There we can see, that bits 8-15 are the value to be written to the register while bits 16-23 are the index of the register. As described in chapter 7.4.65, the drive strength can be configured in the HS_TIMING register (index: 185/0xb9), bits 4-7.
So, we can use this command to find a CMD6 which writes to register 185/0xb9:
# dmesg | grep CMD6.*b9 mmc0: starting CMD6 arg 03b91201 flags 0000049d
Looking at arg, we see that 0xb9 is in the index bits 16-23, so the value bits 8-15 are 0x12. Since bits 4-7 are 1, the drive strength is of type 1 here.
If we now remove the drive strength property from the device tree, we fall back to the default behaviour. So, in the file arch/arm64/boot/dts/renesas/r8a7795-salvator-xs.dts, remove the following line:
fixed-emmc-driver-type = <1>;
Then, the debug output will change like this:
# dmesg | grep CMD6.*b9 mmc0: starting CMD6 arg 03b90201 flags 0000049d
Looking at arg, we see that 0xb9 is in the index bits 16-23, so the value bits 8-15 are 0x02. Since bits 4-7 are 0, the drive strength is of type 0 here.