mmc: sdhci-of-dwcmshc: Intermittent data error under stress test

[Liming Sun]

sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110

SRU Justification:

[Impact]
This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110" error under stress test

[Fix]
The fix added a quirk for the BF3 sdhci driver to avoid such data error.

[Test Case]
1. Same functionality and testing as on BlueField-1/2.
2. Install OS on NVME, and run the FIO test on EMMC.
fio --name=mmcblk0_randrw_stress_round_1 \
  --ioengine=libaio --direct=1 --time_based=1 \
  --end_fsync=1 --ramp_time=5 --norandommap=1 \
  --randrepeat=0 --group_reporting=1 --numjobs=8 \
  --iodepth=128 --rw=randrw --overwrite=1 \
  --runtime=3600 --bs=4K --filename=/dev/mmcblk0 &

[Regression Potential]
Same behavior from user perspective.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-bluefield/5.15.0-1029.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!