omap_hwmod_assert_hardreset(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… omap_hwmod_assert_hardreset ✨

okay bestie, welcome to the Kernel API Manual β€” this one's a lil' function called omap_hwmod_assert_hardreset, and honestly it does exactly one thing but it does it iconically. Let's get into it 🫢


🌸 NAME 🌸

omap_hwmod_assert_hardreset β€” assert the HW reset line of submodules contained in the hwmod module.

Like, you're pulling the reset lever. That's the whole vibe. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int omap_hwmod_assert_hardreset (struct omap_hwmod *oh , const char
*name );

returns an int, takes two args, no cap. πŸ’œ


✨ ARGUMENTS ✨

  • oh β€” a struct omap_hwmod *. that's the hwmod module you're messing with, main character energy πŸ‘‘
  • name β€” const char *, the name of the reset line to look up and then assert. yep, you literally tell it which reset line by name. iykyk πŸ’…

πŸ”₯ DESCRIPTION πŸ”₯

So here's the tea πŸ“: some IP β€” like dsp, ipu or iva β€” contains a processor that requires a HW reset line to be asserted / deasserted in order to enable the IP fully. Like, fully fully. no half-enabling here, periodt.

It returns -EINVAL if oh is null or if the operation is not yet supported on this OMAP. lowkey rude but okay 😭. Otherwise, it just passes along the return value from _assert_hardreset β€” not me doing zero extra work, just vibing and forwarding the result 🧚

ngl, those two -EINVAL cases are the ones that'll get you: a null oh, or an OMAP where this isn't supported yet. handle it. πŸ™ˆ

🌈 SEE ALSO 🌈

This list is long long β€” but we are not skipping a single one, because every reference ate and left no crumbs πŸ”₯


and that's the whole page bestie, go assert some reset lines responsibly πŸ’–βœ¨

anyway, this came out of ./arch/arm/mach-omap2 and it's the October 2026 edition of omap_hwmod_assert_hardreset(9) β€” bye, love u, read ur manpages πŸŽ€πŸ’…

πŸ“¦ where this page comes from