cpufunc.h(3avr)

πŸ“¦
version 2.2.1 Β· 3 versions
, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’… cpufunc.h β€” the cpufunc.h(3avr) glow-up

okay bestie, welcome to cpufunc.h πŸŽ€ β€” this is the AVR-LibC manual page for it, section 3avr, and yes it's short, but short and iconic is a whole genre. no cap.


✨ NAME ✨

cpufunc.h β€” literally just that. the header. the moment. the file itself πŸ¦‹


✨ SYNOPSIS ✨

🌸 Macros 🌸

here's what's living in here as a macro, and it's giving minimalism:

#define _NOP()
#define _MemoryBarrier()

🌸 Functions 🌸

and the functions, bestie, presented in full, exactly as written, don't @ me:

void ccp_write_io (volatile uint8_t *__ioaddr, uint8_t __value)
void ccp_write_spm (volatile uint8_t *__ioaddr, uint8_t __value)
not me putting these in a code block with full respect for the exact parameter names πŸ’€ volatile uint8_t *__ioaddr and uint8_t __value β€” untouched, unedited, unbothered. periodt.

so real quick vibe check on what you're looking at:

  • _NOP() β€” a macro, no arguments, takes nothing, gives nothing. it's the lowkey-est thing here πŸ™ˆ
  • _MemoryBarrier() β€” also a macro, also no arguments. same energy, different name.
  • ccp_write_io β€” a function taking a volatile uint8_t *__ioaddr and a uint8_t __value, returning void. three things to remember, and you got this 🫢
  • ccp_write_spm β€” same shape fr fr: volatile uint8_t *__ioaddr, uint8_t __value, returns void. the sibling. the duo. πŸ‘‘

✨ Author ✨

okay so nobody wrote this in the human sense β€” it was generated automatically by Doxygen for AVR-LibC from the source code. the source code is the author. the source code is the main character. we're all just reading its diary πŸ’œ


and that's the whole page, bestie, we ate and left no crumbs πŸ’…βœ¨

this was cpufunc.h(3avr) from AVR-LibC, Version 2.2.1 β€” mwah, go write some firmware, ily πŸ§šπŸŒΈπŸ’–

πŸ“¦ where this page comes from