On 6/14/23 21:15, Christoph Hellwig wrote:
I really hate having this core complexity, but I suspect trying to driver
hacks would be even worse than that, especially as this goes through
the SCSI midlayer. I think the answer is simply that if Google keeps
buying broken hardware for their products from Samsung they just need
to stick to a 4k page size instead of moving to a larger one.
Although I do not like it that the Exynos UFS controller does not follow
the UFS standard, this UFS controller is used much more widely than only
in devices produced by my employer. See e.g. the output of the following
grep command:
$ git grep -nH '\.compatible' */*/ufs-exynos.c
drivers/ufs/host/ufs-exynos.c:1739: { .compatible = "samsung,exynos7-ufs",
drivers/ufs/host/ufs-exynos.c:1741: { .compatible =
"samsung,exynosautov9-ufs",
drivers/ufs/host/ufs-exynos.c:1743: { .compatible =
"samsung,exynosautov9-ufs-vh",
drivers/ufs/host/ufs-exynos.c:1745: { .compatible = "tesla,fsd-ufs",
Thanks,
Bart.
