_ocp_softreset(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, this is _ocp_softreset(9) from the Kernel API Manual β€” a tiny low-level reset icon with main character energy. Let’s get into it πŸ’…

πŸŽ€ NAME πŸŽ€

_ocp_softreset β€” reset an omap_hwmod via the OCP_SYSCONFIG bit.

✨ SYNOPSIS ✨

int _ocp_softreset (struct omap_hwmod *oh );

🫢 ARGUMENTS 🫢

  • oh β€” struct omap_hwmod *. That’s the hwmod getting the reset treatment, bestie.

πŸ’… DESCRIPTION πŸ’…

Okay so _ocp_softreset resets an omap_hwmod oh via the OCP_SYSCONFIG bit. Quick vibe check: the hwmod must be enabled for this to work β€” no enabled hwmod, no reset magic. ✨

It returns one of these, and every single one matters:

  • -ENOENT β€” if the hwmod cannot be reset this way
  • -EINVAL β€” if the hwmod is in the wrong state
  • -ETIMEDOUT β€” if the module did not reset in time
  • 0 β€” upon success

In OMAP3, a specific SYSSTATUS register is used to get the reset status. Starting in OMAP4, some IPs do not have SYSSTATUS registers and instead use the SYSCONFIG softreset bit to provide the status.

Note that some IP like McBSP do have reset control but don’t have reset status.


🌈 SEE ALSO 🌈

Kernel file ./arch/arm/mach-omap2/omap_hwmod.c is the source file, and the whole reference entourage is:

mwah πŸ’‹ β€” from ./arch/arm/mach-omap2, dated October 2026, and this is _ocp_softreset(9) from the Kernel API Manual. periodt.

πŸ“¦ where this page comes from