[PATCH v3 0/3] ufs: Add callback for vendor-specific RTT capability

[Ed Tsai (蔡宗軒)]

On Mon, 2026-06-15 at 13:57 +0800, ed.tsai at mediatek.com wrote:
> From: Ed Tsai <ed.tsai at mediatek.com>
> 
> The first patch adds the get_hba_nortt() callback to the UFS core
> layer,
> allowing vendor drivers to provide dynamic, platform-specific RTT
> capability handling.
> 
> The second patch implements this callback in the MediaTek UFS driver,
> distinguishing between legacy platforms (which require the RTT to be
> limited to 2) and newer MT6995 B0+ platforms (which can use the value
> from the capability register directly).
> 
> The third patch removes the max_num_rtt field from
> ufs_hba_variant_ops
> as it is now replaced by the get_hba_nortt() callback.
> 
> Changes in v3:
> - Fix incomplete v2 that was sent prematurely - now properly removes
>   max_num_rtt field in patch 3
> 
> Changes in v2:
> - Keep max_num_rtt field in patch 1 to maintain bisectability
> - Split removal of max_num_rtt into a separate patch (patch 3)
> 
> Ed Tsai (3):
>   ufs: core: Add get_hba_nortt callback for vendor-specific RTT
>     capability
>   ufs: mediatek: Implement get_hba_nortt callback for RTT capability
>   ufs: core: Remove max_num_rtt field from ufs_hba_variant_ops
> 
>  drivers/ufs/core/ufshcd.c       |  9 +++++----
>  drivers/ufs/host/ufs-mediatek.c | 12 +++++++++++-
>  drivers/ufs/host/ufs-mediatek.h |  4 ++--
>  include/ufs/ufshcd.h            |  5 +++--
>  4 files changed, 21 insertions(+), 9 deletions(-)
> 

Hi Martin,

Just a gentle ping on this patch series.

All three patches have received reviewed tags from Bart and Peter.
Could you please consider picking this up for the next cycle when you
have a chance?

Thanks,

Ed.