PVR_HAS_FEATURE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… PVR_HAS_FEATURE(9) πŸ’…

okay so welcome to the Kernel API Manual bestie, today we're learning about PVR_HAS_FEATURE β€” no cap, it's a whole vibe check for your PowerVR hardware πŸ”₯

✨ NAME ✨

PVR_HAS_FEATURE β€” literally just tests whether a PowerVR device has a given feature 🫢


🌸 SYNOPSIS 🌸

PVR_HAS_FEATURE (pvr_dev , feature );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • pvr_dev β€” [IN] the target PowerVR device, aka your main character πŸŽ€
  • feature β€” [IN] the hardware feature name, bestie. the name of the feature. yes it's that simple ✨

πŸ’œ DESCRIPTION πŸ’œ

so here's the tea β˜• β€” feature names are derived from the ones you'll find in struct pvr_device_features by dropping the 'has_' prefix, which this macro applies for you. it's giving "i gotchu, don't worry about typing it yourself" energy, fr fr πŸ’…


⭐ RETURN ⭐

  • true if the named feature is present in the hardware πŸ‘‘
  • false if the named feature is not present in the hardware 😭

🧚 SEE ALSO 🧚

Kernel file ./drivers/gpu/drm/imagination/pvr_device.h struct pvr_gpu_id(9), struct pvr_fw_version(9), struct pvr_device_data(9), struct pvr_device(9), struct pvr_file(9), PVR_FEATURE_VALUE(9), PVR_HAS_QUIRK(9), PVR_HAS_ENHANCEMENT(9), PVR_PACKED_BVNC(9), pvr_gpu_id_to_packed_bvnc(9), PVR_CR_FIELD_GET(9), pvr_cr_read32(9), pvr_cr_read64(9), pvr_cr_write32(9), pvr_cr_write64(9), pvr_cr_poll_reg32(9), pvr_cr_poll_reg64(9), pvr_round_up_to_cacheline_size(9), IOCTL validation helpers(9), pvr_ioctl_union_padding_check(9), PVR_STATIC_ASSERT_64BIT_ALIGNED(9), PVR_IOCTL_UNION_PADDING_CHECK(9) πŸ¦‹πŸŒΈ


alright bestie that's the whole page, go read some source πŸ’–

sign-off szn: this iconic lil page lives in ./drivers/gpu/drm/imagination and it dropped October 2026 β€” periodt πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from