bcom_psc_gen_bd_tx_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ bcom_psc_gen_bd_tx_init πŸŽ€

okay so bestie, welcome to the Kernel API Manual ✨ this one's a little kernel function that sets you up with a transmit task on a PSC port β€” think of it as getting your fave a whole little send-y setup so the data can actually, you know, go. πŸ’…


🌸 NAME 🌸

bcom_psc_gen_bd_tx_init β€” literally allocates a transmit bcom_task for a PSC port πŸ¦‹


✨ SYNOPSIS ✨

struct bcom_task * bcom_psc_gen_bd_tx_init (unsigned psc_num , int
queue_len , phys_addr_t fifo );

that's the whole vibe. three things in, one struct bcom_task * out. 🫢


πŸ’– ARGUMENTS πŸ’–

  • psc_num β€” the number of the PSC you want to allocate a task for, like "which port bestie" πŸ”₯
  • queue_len β€” how many buffer descriptors to allocate for the task, i.e. the size of your little queue πŸ‘‘
  • fifo β€” the physical address of the FIFO register (yes, the actual physical address, no cap) ⭐

🌈 DESCRIPTION 🌈

So what it does: it allocates a bestcomm task structure for transmitting data to a PSC. That's the whole job. It's giving "set me up so I can send things" energy and honestly? We respect it. 😭


πŸ¦‹ SEE ALSO πŸ¦‹

  • the kernel file ./drivers/dma/bestcomm/gen_bd.c πŸ’€ (go read it, iykyk)
  • bcom_psc_gen_bd_rx_init(9) β€” the receiving sibling, the other main character 🌸

lowkey a reminder: this is kernel API territory, not your cute lil userland script, so like… be normal about it bestie πŸ’œ

and that's the page!! πŸŽ€ fr fr that's it 🫢

signed off from ./drivers/dma/bestcomm, October 2026 β€” periodt, that's the version and the date, mwah πŸ’‹πŸ’–

πŸ“¦ where this page comes from