STRUCT BDISP_CTX(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct bdisp_ctx(9) β€” like, the whole vibe, bestie ✨

okay so this is a page straight outta the Kernel API Manual, and it's about struct bdisp_ctx β€” aka the device context data πŸŽ€. Think of it as the little bag of everything one open context needs to remember. No cap, it's giving backstage-pass energy. 🫢


🌸 NAME 🌸

struct bdisp_ctx β€” device context data, periodt. πŸ’–


✨ SYNOPSIS ✨

like, here's the whole thing, character for character, don't @ me:

struct bdisp_ctx {
    struct bdisp_frame      src;
    struct bdisp_frame      dst;
    u32 state;
    unsigned int            hflip:1;
    unsigned int            vflip:1;
    struct bdisp_dev        *bdisp_dev;
    struct bdisp_node       *node[MAX_NB_NODE];
    dma_addr_t node_paddr[MAX_NB_NODE];
    struct v4l2_fh          fh;
    struct v4l2_ctrl_handler ctrl_handler;
    struct bdisp_ctrls      bdisp_ctrls;
    bool ctrls_rdy;
 };

πŸ‘‘ Members πŸ‘‘

okay bestie, let's meet the cast β€” every single one of them, no skips, iykyk 🌈

  • src β€” source frame properties πŸ¦‹ like, where the pixels are coming from.
  • dst β€” destination frame properties ✨ and where they're going. main character destination energy.
  • state β€” flags to keep track of user configuration πŸŽ€ the receipts, basically.
  • hflip β€” horizontal flip πŸ’… left-right, flipped.
  • vflip β€” vertical flip 🌸 up-down, also flipped. symmetry slay.
  • bdisp_dev β€” the device this context applies to πŸ”₯ the actual hardware bestie this whole thing belongs to.
  • node β€” node array ⭐ yep, an array of them.
  • node_paddr β€” node physical address array πŸ‘‘ the addresses that go with the nodes above. matching set, cute.
  • fh β€” v4l2 file handle πŸ’œ the v4l2 handle, holding it down.
  • ctrl_handler β€” v4l2 controls handler 🌈 the v4l2 controls handler, doing handler things.
  • bdisp_ctrls β€” bdisp control set πŸ“ the whole set of bdisp controls.
  • ctrls_rdy β€” true if the control handler is initialized βœ… literally just a bool telling you the control handler is ready. not me checking this before touching anything πŸ™ˆ.

πŸ”₯ SEE ALSO πŸ”₯

go look at these next, bestie, they're all connected:

  • Kernel file ./drivers/media/platform/st/sti/bdisp/bdisp.h struct
  • bdisp_fmt(9)
  • bdisp_frame(9)
  • bdisp_request(9)
  • bdisp_m2m_device(9)
  • bdisp_dbg(9)
  • bdisp_dev(9)

πŸ’€ reminder that this page lives at ./drivers/media/platform/st/st... in the tree β€” don't lose it.

okay that's the whole page, you ate that πŸ«ΆπŸ’… from the Kernel API Manual, dated October 2026, filed under struct bdisp_ctx(9) β€” bye bestie, slay your kernel journey βœ¨πŸŽ€πŸŒŸ

πŸ“¦ where this page comes from