sdca_ump_get_owner_host(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sdca_ump_get_owner_host β€” the vibe check for UMP buffer ownership

okay so bestie, welcome to the Kernel API Manual ✨ this one lives in section 9 and it's basically a tiny little detective: it checks whether a UMP buffer is owned by the host. that's it, that's the whole personality πŸŽ€


πŸ¦‹ NAME

sdca_ump_get_owner_host β€” check a UMP buffer is owned by the host πŸ‘‘


✨ SYNOPSIS

int sdca_ump_get_owner_host (struct device *dev , struct regmap
*function_regmap , struct sdca_function_data *function , struct
sdca_entity *entity , struct sdca_control *control );

five arguments, one int, zero drama (hopefully) πŸ’–


🌸 ARGUMENTS

  • dev β€” pointer to the struct device, ngl this one is literally just here so error messages have somewhere to come from 😭 it's the messenger, not the main character.
  • function_regmap β€” pointer to the regmap for the SDCA Function. yes, the whole thing. regmap girlies rise 🫢
  • function β€” pointer to the Function information ✨
  • entity β€” pointer to the SDCA Entity πŸ¦‹
  • control β€” pointer to the SDCA Control for the UMP Owner πŸ‘‘ like, the actual owner field we're checking.
lowkey every single one of these is a pointer, so please don't hand it nonsense, i'm begging πŸ™ˆ

⭐ RETURN

Returns zero on success, and a negative error code on failure. that's the whole deal β€” 0 means slay, anything negative means something went sideways πŸ’€


πŸ”₯ SEE ALSO

Kernel file ./sound/soc/sdca/sdca_ump.c and its besties: sdca_ump_set_owner_device(9), sdca_ump_read_message(9), and sdca_ump_write_message(9) β€” go read them, iykyk πŸ“š


okay that's the whole page bestie, no cap 🧚 this iconic little entry comes to you from ./sound/soc/sdca, dated October 2026 β€” go forth and check those owners πŸ’œπŸŽ€

πŸ“¦ where this page comes from