vsp1_entity_remote_pad(9)

💅 vsp1_entity_remote_pad(9) 💅

okay so bestie, welcome to the Kernel API Manual — this one's from the kernel docs and it's lowkey adorable once you get it, i promise 🫶

---

✨ NAME ✨

vsp1_entity_remote_pad — find the pad at the remote end of a link 🔗

---

🌸 SYNOPSIS 🌸

struct media_pad * vsp1_entity_remote_pad (struct media_pad *pad );

---

🎀 ARGUMENTS 🎀

• pad — the pad sitting at the local end of the link, like the one you're standing on already 👀

---

🦋 DESCRIPTION 🦋

so what this actually does: it searches for a remote pad connected to the pad you handed it, and the way it does that is by iterating over all links originating or terminating at that pad until it finds one that's enabled. slay, honestly 💅

and here's the tea about why it's built like that ☕ — our link setup implementation guarantees that the output fan-out will not be higher than one for the data pipelines. iconic behavior, no cap. the one exception? the links to the HGO and HGT, which can be enabled in addition to a regular data link. those two are the main character exceptions, iykyk 🌈

so when it's traversing outgoing links, this function ignores HGO and HGT entities — which means you should use it in place of the generic media_pad_remote_pad_first function when you're traversing data pipelines. that's the whole vibe check right there ✨

it returns a pointer to the pad at the remote end of the first found enabled link, or NULL if no enabled link has been found. and if that's your result then... yeah 😭 that's the whole story.

⚠️ quick reminder bestie: HGO and HGT get skipped on outgoing traversal. that's not a bug, that's the point — don't @ me 🔥

---

🌟 SEE ALSO 🌟

• Kernel file ./drivers/media/platform/renesas/vsp1/vsp1_entity.c
• vsp1_entity_get_state(9)

---

and that's the whole page, bestie, you ate that 🍓 go forth and traverse those data pipelines with main character energy 👑

signed off with love from ./drivers/media/platform/renes... — October 2026 💜💫