ipc_pcie_addr_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ipc_pcie_addr_map β€” a kernel API manual moment (section 9, bestie)

okay so real talk, this is ipc_pcie_addr_map from the Kernel API Manual, section 9, and it's genuinely one of those little functions that's doing the absolute most behind the scenes ✨


🌸 NAME 🌸

ipc_pcie_addr_map β€” bestie, what it does is take the kernel's virtual address and map it over to either the IOVA address space or the Physical address space (pick your fighter πŸ’…), and then that mapping gets stashed away in the skb's cb. that's the whole vibe. no cap.


πŸŽ€ SYNOPSIS πŸŽ€

int ipc_pcie_addr_map (struct iosm_pcie *ipc_pcie , unsigned char *data
, size_t size , dma_addr_t *mapping , int direction );

like, look at her. iconic signature. five arguments, one int return, zero notes. πŸ¦‹


✨ ARGUMENTS ✨

  • ipc_pcie β€” pointer to struct iosm_pcie. she's the main character, everything routes through her πŸ‘‘
  • data β€” the skb mem containing the data. yes, that skb. the one whose cb we're about to fill 🫢
  • size β€” the data size. how much data we're talking about, fr fr
  • mapping β€” the DMA mapping address. this is where the mapped address lands πŸ’«
  • direction β€” the data direction. which way the data's going, iykyk 🌈

πŸ”₯ RETURN πŸ”₯

  • 0 on success πŸŽ‰ β€” slay, it worked
  • a failure value on error 😭 β€” not slay, something went wrong
no in-between, bestie. it's either the 0 glow-up or the failure arc. πŸ’€

🌟 SEE ALSO 🌟

first up, the kernel file itself, go read it:

./drivers/net/wwan/iosm/iosm_ipc_pcie.h

and then the whole friend group, because of course there's a whole friend group:

like, that's the group chat. they all get it. πŸ’œ


and that's the page! 🧚 source lives in <pink>./drivers/net/wwan/iosm</pink>, dated October 2026, and she's filed under ipc_pcie_addr_map(9) β€” mwah, kiss the manual, bye bestie! πŸ’…πŸŽ€

πŸ“¦ where this page comes from