vsp1_entity_get_state(9)

💅 vsp1_entity_get_state — Get the subdev state for an entity

okay so bestie, you know how every entity in the VSP1 world has, like, a state? Yeah. This is the function that goes and gets it for you. No cap. 🎀

---

✨ SYNOPSIS ✨

struct v4l2_subdev_state * vsp1_entity_get_state (struct v4l2_subdev_state *sd_state , enum v4l2_subdev_format_whence which );

wait, hold up, let me give you the full thing properly, no crumbs missing:

struct v4l2_subdev_state * vsp1_entity_get_state (struct v4l2_entity *entity ,
                                                 struct v4l2_subdev_state *sd_state ,
                                                 enum v4l2_subdev_format_whence which );

okay actually, to be so fr, here's the exact signature, character for character, do not come for me:

struct v4l2_subdev_state * vsp1_entity_get_state (struct vsp1_entity
*entity , struct v4l2_subdev_state *sd_state , enum
v4l2_subdev_format_whence which );

she returns a struct v4l2_subdev_state * and she takes three things. iconic. 💅

---

🦋 ARGUMENTS 🦋

• entity — the entity. that's her. that's the main character. 👑
• sd_state — the TRY state. yes, literally the TRY state, she gets her own spotlight here.
• which — the state selector, and your options are ACTIVE or TRY. choose wisely bestie. 🫶

---

🌸 DESCRIPTION 🌸

so here's the tea. when you call this with which set to V4L2_SUBDEV_FORMAT_ACTIVE, the caller must hold the entity lock to access the returned configuration. like, this is not a suggestion, this is the rule. 🔒 don't be out here accessing config without the lock, that's giving chaos and we don't do chaos.

the function returns the subdev state that the which argument asks for. and the way it works is lowkey so clean:

• the TRY state gets passed in explicitly through the sd_state argument, and when you request it, it's just... returned. no drama, no detour. literally handed right back to you. ✨
• the ACTIVE state? that one comes from the entity structure itself. she's already living there. 💖

that's it. that's the whole vibe. state comes in, state comes out, which decides which one. slay. 🧚

---

⭐ SEE ALSO ⭐

• Kernel file ./drivers/media/platform/renesas/vsp1/vsp1_entity.c
• vsp1_entity_remote_pad(9) — go read that one next bestie, iykyk 💜

---

ngl, if you're touching the ACTIVE state without the entity lock, that's a 💀 moment. take the lock. hold the lock. be the lock. 🙈

---

and that's the whole page babes 🍓 — brought to you by the Kernel API Manual, hot off the source at ./drivers/media/platform/renes..., dated October 2026, and yes she's still out here being vsp1_entity_get_state(9). periodt. 🌈👑