host1x_sync..._by_id_noref(9)
π host1x_syncpt_get_by_id_noref(9) β from the Kernel API Manual, bestie π
okay so real talk, this one is a kernel function and the whole vibe is "grab a thing, but do NOT hold onto it." no refcount bump, no commitment, we're just looking πβ¨
β¨ NAME β¨
host1x_syncpt_get_by_id_noref β bestie, this literally obtains a syncpoint by ID but doesn't increase the refcount. that's the whole personality. lowkey iconic, highkey dangerous if you get comfy π
π¦ SYNOPSIS π¦
struct host1x_syncpt * host1x_syncpt_get_by_id_noref (struct host1x
*host , unsigned int id );
like yes that's a whole pointer to a struct host1x_syncpt and yes it comes straight back at you, periodt π
πΈ ARGUMENTS πΈ
hostβ the host1x controller, aka the main character here π this is the thing you're asking.idβ the syncpoint ID, like the little name tag that says which syncpoint you want π
π«Ά SEE ALSO π«Ά
the whole friend group is in ./drivers/gpu/host1x/syncpt.c and honestly they all ate:
host1x_syncpt_alloc(9)host1x_syncpt_id(9)host1x_syncpt_incr_max(9)host1x_syncpt_incr(9)host1x_syncpt_wait(9)host1x_syncpt_request(9)host1x_syncpt_put(9)host1x_syncpt_read_max(9)host1x_syncpt_read_min(9)host1x_syncpt_read(9)host1x_syncpt_get_by_id(9)host1x_syncpt_get(9)host1x_syncpt_get_base(9)host1x_syncpt_base_id(9)host1x_syncpt_release_vblank_reservation(9)
π¨ ok one tiny thing, and it's giving cautionary tale: this is the noref version. it hands you the syncpoint without upping the refcount, so don't go acting like you own it. the name literally told you. iykyk π
that's the whole page, no cap π written under ./drivers/gpu/host1x, dated October 2026, and brought to you by host1x_sync..._by_id_noref(9) β slay, go read the source bestie πβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms