sdhci_arasa...er_sdcardclk(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sdhci_arasan_register_sdcardclk β€” the Kernel API Manual, bestie edition 🌸

okay so real talk, this is from the Kernel API Manual and it's the page for sdhci_arasan_register_sdcardclk, which lowkey has the longest name ever but we move πŸ’–


✨ NAME ✨

sdhci_arasan_register_sdcardclk β€” literally just registers the sdcardclk so a PHY can use it. that's the whole vibe πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int sdhci_arasan_register_sdcardclk (struct sdhci_arasan_data
*sdhci_arasan , struct clk *clk_xin , struct device *dev );

three args, one int coming back at you, no cap ✨


🌈 ARGUMENTS 🌈

  • sdhci_arasan β€” our very own private data structure 🫢 like, ours, our little guy.
  • clk_xin β€” pointer to the functional clock ⭐
  • dev β€” pointer to our struct device πŸ‘‘

πŸ’œ DESCRIPTION πŸ’œ

so some PHY devices are nosy (affectionate) and genuinely need to know what the actual card clock is 🌸 and the way they find out? we hand them a clock through the common clock framework so they can go query it themselves. it's giving "here bestie, look it up" 😭✨


πŸ”₯ RETURN πŸ”₯

0 on success πŸŽ‰ and an error value on error πŸ˜­πŸ’€ (yes that's the whole return section, it ate and left no crumbs)


🧚 SEE ALSO 🧚

Kernel file ./drivers/mmc/host/sdhci-of-arasan.c β€” go read it, iykyk πŸ‘‘

and the whole friend group:


ngl every single one of those is linked and every single one matters, don't skip a single one or i will know πŸ™ˆ

okay that's the page!! sourced from ./drivers/mmc/host, dated October 2026, and that's the whole manual entry, periodt πŸ’…πŸŽ€πŸ’–

πŸ“¦ where this page comes from