ufshcd_verify_dev_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this is the Kernel API Manual page for ufshcd_verify_dev_init(9) β€” and the name is literally telling you what it does: Verify device initialization πŸ’…βœ¨


✨ SYNOPSIS ✨

int ufshcd_verify_dev_init (struct ufs_hba *hba );

πŸŽ€ ARGUMENTS πŸŽ€

  • hba β€” the per-adapter instance, aka the main-character struct for this call 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

So here’s the vibe: this function sends a NOP OUT UPIU and waits for a NOP IN response to check whether the device Transport Protocol (UTP) layer is ready after a reset. It’s basically giving the device a little β€œu up?” text πŸ’¬βœ¨

If the UTP layer at the device side is not initialized, it may not respond with NOP IN UPIU within timeout of NOP_OUT_TIMEOUT, and we retry sending NOP OUT for NOP_OUT_RETRIES iterations. No cap, that’s the whole check πŸ”πŸ’–


πŸ”₯ RETURN πŸ”₯

Here’s the tea, bestie:

  • 0 upon success πŸŽ‰
  • > 0 in case the UFS device reported an OCS error 😭
  • < 0 if another error occurred πŸ’€

🌈 SEE ALSO 🌈

Kernel file: ./drivers/ufs/core/ufshcd.c β€” and now the whole friend group, every single one, no skips πŸ‘‘βœ¨


okay that’s literally the whole page, bestie 🫢 β€” signing off from ./drivers/ufs/core, October 2026, for ufshcd_verify_dev_init(9) πŸ’–βœ¨

πŸ“¦ where this page comes from