pvr_hwrt_dataset_lookup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pvr_hwrt_dataset_lookup(9) β€” like, the whole page, but make it make sense

okay so this is from the Kernel API Manual, and the star of the show is pvr_hwrt_dataset_lookup ✨ β€” yes that's a mouthful, we're gonna get through it together, bestie 🫢


πŸŽ€ NAME πŸŽ€

pvr_hwrt_dataset_lookup β€” bestie, this literally just looks up an HWRT dataset pointer from a handle. that's the whole vibe check πŸ‘‘


🌸 SYNOPSIS 🌸

struct pvr_hwrt_dataset * pvr_hwrt_dataset_lookup (struct pvr_file
*pvr_file , u32 handle );

like, you hand it a pvr_file and a handle, and it gives you back a struct pvr_hwrt_dataset *. iconic signature, no notes πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pvr_file β€” pointer to the pvr_file structure. yes. it's a pointer to the thing. we love her πŸ’–
  • handle β€” the object handle. it's a u32, it's the key you're looking up, periodt.

✨ DESCRIPTION ✨

so what actually happens? it takes a reference on the dataset object πŸ”₯ β€” like it's holding onto it for you so it doesn't ghost you mid-use.

⚠️ important bestie: you gotta call pvr_hwrt_dataset_put to release that reference. don't just walk away with it, that's not the move 😭

πŸ’œ RETURN πŸ’œ

  • The requested object on success 🌈 β€” slay, you got it
  • NULL on failure 😭 β€” and why would it fail? (object does not exist in list, or is not a HWRT dataset). so if it's not in the list, or it's just not the right kind of dataset, you get the big NULL. ngl, rude, but fair πŸ’€

🧚 SEE ALSO 🧚

iykyk, go read those too, they're all in the same little friend group πŸ“


okay that's the page!! πŸŽ€ this all lives over in ./drivers/gpu/drm/imagination, dated October 2026, and the whole thing is filed under pvr_hwrt_dataset_lookup(9) β€” mwah, go forth and reference-count responsibly πŸ’–βœ¨

πŸ“¦ where this page comes from