STRUCT OMAP_RNG_PDATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 STRUCT OMAP_RNG_PDATA(9) 🌸

okay so bestie, welcome to the Kernel API Manual β€” yes we're literally in the kernel docs rn, and today's main character is struct omap_rng_pdata, which is the RNG IP block-specific data situation. πŸ’…


✨ NAME ✨

struct omap_rng_pdata β€” the RNG IP block-specific data πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct omap_rng_pdata {
    u16 *regs;
    u32 data_size;
    u32 (*data_present)(struct omap_rng_dev *priv);
    int (*init)(struct omap_rng_dev *priv);
    void (*cleanup)(struct omap_rng_dev *priv);
 };

no cap, that's the whole vibe right there πŸ‘‘


🧩 MEMBERS 🧩

okay let's go through the squad one by one, everyone's got a job:

  • regs β€” pointer to the register offsets structure. it's giving "here's where the stuff lives" πŸ—ΊοΈ
  • data_size β€” the number of bytes in the RNG output. literally just how much random you're getting, fr fr πŸ”’
  • data_present β€” callback to determine if data is available. it's the vibe check function, like "is the data here yet or are we waiting" πŸ™ˆ
  • init β€” callback for the IP specific initialization sequence. the getting-ready part, the pre-game routine ✨
  • cleanup β€” callback for the IP specific cleanup sequence. the "okay we're done here, tidy up bestie" moment 🧹

πŸ‘€ SEE ALSO πŸ‘€

  • the kernel file ./drivers/char/hw_random/omap-rng.c β€” go read it, it's iconic iykyk πŸ“–

lowkey reminder: every single one of those members is a real field with a real job, so don't be out here skipping any of them, bestie 🫢

aaaand that's the page πŸŽ€ huge shoutout to ./drivers/char/hw_random for being the section, and to October 2026 for the timestamp β€” slay, we love a dated drop β­πŸ’œ

πŸ“¦ where this page comes from