STRUCT OMAP_RNG_PDATA(9)
πΈ 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
- 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