STRUCT DRM_TEGRA_GEM_GET_TILING(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct drm_tegra_gem_get_tiling(9) πŸ’…

okay so this is a page from the Kernel API Manual and it's literally the cheat sheet for struct drm_tegra_gem_get_tiling β€” the little parameter bundle you hand to the get-tiling IOCTL. yes bestie, get. we're asking the kernel questions here, not telling it what to do. πŸŽ€


✨ NAME ✨

struct drm_tegra_gem_get_tiling β€” the parameters for the get tiling IOCTL, periodt πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

struct drm_tegra_gem_get_tiling {
    __u32 handle;
    __u32 mode;
    __u32 value;
    __u32 pad;
 };

(no cap, that's the whole struct β€” she's compact and she knows it ✨)


🌸 Members 🌸

okay let's meet the cast, one field at a time 🫢

  • handle β€” handle to the GEM object you're asking about, i.e. the one whose tiling parameters you wanna query. it's giving "who's this about?" energy πŸ‘‘
  • mode β€” the tiling mode currently associated with the GEM object. lowkey important: the kernel sets this one for you, upon successful completion of the IOCTL. you don't fill it in, you receive it 🎁
  • value β€” the tiling mode parameter currently associated with the GEM object. again, set by the kernel upon successful completion of the IOCTL. so you read it, you don't write it, iykyk 😌
  • pad β€” structure padding that may be used in the future. must be 0. fr fr, zero it out, don't get cute with it πŸ™ˆ
πŸ’€ real talk: mode and value are the kernel's little gifts to you after a successful IOCTL, so don't rock up with your own values expecting them to mean anything. they're outputs. and pad stays 0. that's the vibe check and you passed 🧚

🌈 SEE ALSO 🌈

go look at the kernel file ./include/uapi/drm/tegra_drm.h and then go on a whole little reading spree with these icons πŸ’–:

that's the whole friend group, go say hi to all of them πŸ¦‹βœ¨


and that's the page!! came from ./include/uapi/drm, dated October 2026 β€” mwah, iconic, no notes πŸ’œπŸŽ€

πŸ“¦ where this page comes from