omap_hwmod_register_links(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

omap_hwmod_register_links β€” register an array of hwmod links. That's the whole name, and honestly it's giving β€œguest list for the kernel links party” πŸ’Œ

🌸 SYNOPSIS 🌸

int omap_hwmod_register_links (struct omap_hwmod_ocp_if **ois );

πŸ’… ARGUMENTS πŸ’…

  • ois β€” pointer to an array of omap_hwmod_ocp_if to register. This is the link lineup you're handing over 🫢

πŸŽ€ DESCRIPTION πŸŽ€

Okay so the tea β˜• is this: omap_hwmod_register_links is intended to be called early in boot, before the clock framework is initialized. Like, early-early, bestie.

If ois is not null, it will register all omap_hwmods listed in ois that are valid for this chip. No cap 🌈

Returns -EINVAL if omap_hwmod_init hasn't been called before calling this function, -ENOMEM if the link memory area can't be allocated, or 0 upon success. That's the return-value mood board: invalid setup, memory says no, or success slay ✨

πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./arch/arm/mach-omap2/omap_hwmod.c β€” that's the file this page points at, bestie 🧚

Okay, cross-reference avalanche incoming πŸŒͺ️ Every single name from the SEE ALSO list is below, in order, and yes, it's a lot. We're not skipping a single one πŸ‘‘

Source/version/date sign-off πŸŽ€: source is ./arch/arm/mach-omap2, page/version is omap_hwmod_register_links(9), date is October 2026 β€” bye bestie! πŸ’–

πŸ“¦ where this page comes from