sdio_uart_activate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– sdio_uart_activate(9) β€” like, the kernel API manual bestie πŸ’–

okay so this is the sdio_uart_activate page from the Kernel API Manual, and honestly? it's a little baddie. it's all about starting up hardware. let's get into it πŸŽ€


✨ NAME ✨

sdio_uart_activate β€” start up hardware πŸ”₯

🌸 SYNOPSIS 🌸

int sdio_uart_activate (struct tty_port *tport , struct tty_struct *tty
);

πŸ¦‹ ARGUMENTS πŸ¦‹

  • tport β€” the tty port to activate, aka the one getting woken up πŸ’…
  • tty β€” the tty bound to this port. they're a package deal fr fr 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so we're activating a tty port. iconic. and here's the thing β€” the port locking guarantees us this will run exactly once per set of opens, no cap πŸ’―. and if it succeeds? then the shutdown method will run exactly once to match it. balanced, as all things should be ✨

start up and shutdown are protected from each other by the internal locking, so they will not run at the same time β€” not even during a hangup event 😭 which is honestly so real of them.

and if we successfully start up the port, we take an extra kref as we will keep it around until shutdown, when the kref is dropped. periodt πŸŽ€

🌈 SEE ALSO 🌈

go read those too bestie, iykyk πŸ“šπŸ’œ


okay that's the whole vibe check πŸ’… this page lives in ./drivers/mmc/core, dated October 2026 β€” slay, see u in the next one πŸŒΈβœ¨πŸ’–

πŸ“¦ where this page comes from