ufshcd_advan..._req_handler(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie, meet ufshcd_advan..._req_handler(9) from the Kernel API Manual — she handles an advanced RPMB request and she is literally the moment. 💅✨

💖 NAME 💖

ufshcd_advanced_rpmb_req_handler — handle advanced RPMB request. That's the whole name, no cap. 🎀

✨ SYNOPSIS ✨

here's the exact signature, no edits, no vibes-based renaming:

int ufshcd_advanced_rpmb_req_handler (struct ufs_hba *hba , struct
       utp_upiu_req *req_upiu , struct utp_upiu_req *rsp_upiu , struct ufs_ehs
       *req_ehs , struct ufs_ehs *rsp_ehs , int sg_cnt , struct scatterlist
       *sg_list , enum dma_data_direction dir );

🎀 ARGUMENTS 🎀

okay the cast of characters, in order:

  • hba — per adapter instance. one per adapter instance, got it. 🫶
  • req_upiu — the upiu request.
  • rsp_upiu — the upiu reply.
  • req_ehs — EHS field which contains Advanced RPMB Request Message.
  • rsp_ehs — EHS field which returns Advanced RPMB Response Message.
  • sg_cnt — The number of sg lists actually used.
  • sg_list — Pointer to SG list when DATA IN/OUT UPIU is required in ARPMB operation.
  • dir — DMA direction.

🦋 RETURN 🦋

0 upon success, slay. > 0 in case the UFS device reported an OCS error. < 0 if another error occurred. that's the return-value vibe check, fr fr. 💀

🌸 SEE ALSO 🌸

bestie, the SEE ALSO list is huge and iconic — same order, every single reference, no skips:

mwah 💋 — this cutie comes from source/version ./drivers/ufs/core, dated October 2026, and the page title is still ufshcd_advan..._req_handler(9). bye bestie! 🫶🌈

📦 where this page comes from