ti_sci_reset_assert(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ti_sci_reset_assert(9) β€” the kernel API manual, but make it make sense

okay so bestie, welcome to the kernel API manual page for ti_sci_reset_assert, and yes it's a function reference, and yes we're gonna get through it together 🫢


✨ NAME ✨

ti_sci_reset_assert β€” assert device reset. that's it, that's the whole vibe. it asserts a reset. periodt.


🌸 SYNOPSIS 🌸

int ti_sci_reset_assert (struct reset_controller_dev *rcdev , unsigned long id );

like, that's the whole call. one function, two args, returns an int. iconic behavior honestly πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • rcdev β€” the reset controller entity. this is your main character, the reset controller itself πŸ”₯
  • id β€” the ID of the reset to be asserted. which reset are we doing? this one, specifically. no cap.

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does this actually do? it implements the reset driver op to assert a device's reset, using the TI SCI protocol. that's the whole job description fr fr.

and the way it works is kind of a slay β€” it invokes the function ti_sci_reset_set with the corresponding parameters as passed in, but with the assert argument set to true for asserting the reset. so it's lowkey a wrapper, but a purposeful one ✨

ngl, the "corresponding parameters as passed in" part is important β€” it doesn't secretly swap anything else out. only assert goes to true.

πŸ’œ RETURN πŸ’œ

0 for a successful request, else a corresponding error value. so if you get 0, congrats bestie, you ate πŸ’– if you don't, that error value is telling you something, so listen to it 😭


πŸ‘‘ SEE ALSO πŸ‘‘

get into these, iykyk:


also quick vibe check: this whole page lives in ./drivers/reset, and it's tagged October 2026, so yeah β€” that's the version and date, right there in the sign-off. mwah πŸ’‹

that's the page, bestie. go assert some resets responsibly πŸ§šβ€β™€οΈπŸŒ·β­

πŸ“¦ where this page comes from