The current Renesas UFS driver contains initialization code
that is specific to R-Car S4 R8A779F0. The upcoming R-Car X5H
initialization code is different and contained in a separate
driver. Update the Kconfig entry help text for the current
driver to help discern it from the X5H driver. No functional
change.

Signed-off-by: Marek Vasut <[email protected]>
---
Cc: Bhupesh Sharma <[email protected]>
Cc: Casey Connolly <[email protected]>
Cc: Michal Simek <[email protected]>
Cc: Neha Malcom Francis <[email protected]>
Cc: Neil Armstrong <[email protected]>
Cc: Nobuhiro Iwamatsu <[email protected]>
Cc: Sumit Garg <[email protected]>
Cc: Tom Rini <[email protected]>
Cc: Tuyen Dang <[email protected]>
Cc: Venkatesh Yadav Abbarapu <[email protected]>
Cc: Yoshihiro Shimoda <[email protected]>
Cc: [email protected]
Cc: [email protected]
---
 drivers/ufs/Kconfig | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/ufs/Kconfig b/drivers/ufs/Kconfig
index b466374fe40..4c6b08ad31c 100644
--- a/drivers/ufs/Kconfig
+++ b/drivers/ufs/Kconfig
@@ -48,12 +48,12 @@ config UFS_PCI
          If unsure, say N.
 
 config UFS_RENESAS
-       bool "Renesas specific hooks to UFS controller platform driver"
+       bool "Renesas R-Car S4 UFS Controller support"
        depends on UFS
        select BOUNCE_BUFFER
        help
-         This selects the Renesas specific additions to UFSHCD platform driver.
-         UFS host on Renesas needs some vendor specific configuration before
-         accessing the hardware.
+         This selects the Renesas S4 specific additions to UFSHCD
+         platform driver. UFS host on Renesas needs some vendor
+         specific configuration before accessing the hardware.
 
 endmenu
-- 
2.51.0

Reply via email to