pdc_rx_buf_pool_create(9)
π pdc_rx_buf_pool_create(9) π
okay so bestie, you're in the Kernel API Manual rn and this page is all about a function called pdc_rx_buf_pool_create β yes the name is a mouthful, yes you'll get it, stay with me π«Ά
β¨ NAME β¨
pdc_rx_buf_pool_create β literally builds the pool of receive buffers, the ones whose whole job is catching the metadata header that comes back with every single response message π
πΈ SYNOPSIS πΈ
int pdc_rx_buf_pool_create (struct pdc_state *pdcs );
π ARGUMENTS π
pdcsβ the PDC state structure. that's it, that's the whole argument list, we love a simple queen π
π¦ DESCRIPTION π¦
so here's the vibe: that metadata? it does not get returned to the mailbox client. nope, not invited to the party π
so the PDC driver handles these buffers itself β it's the one managing them, no cap. that's genuinely the whole description, short and iconic β
π₯ RETURN π₯
the manpage is being super mysterious about this one, so here it is exactly as written, no edits:
PDC_SUCCESS -ENOMEM if pool creation fails
translation: PDC_SUCCESS when it works, -ENOMEM if pool creation fails. she's terse but she's clear π
π SEE ALSO π
the kernel file to go stare at: ./drivers/mailbox/bcm-pdc-mailbox.c
and the whole friend group of related pages, in order, no skips π«Ά
pdc_setup_debugfs(9)pdc_build_rxd(9)pdc_build_txd(9)pdc_receive_one(9)pdc_receive(9)pdc_tx_list_sg_add(9)pdc_tx_list_final(9)pdc_rx_list_init(9)pdc_rx_list_sg_add(9)pdc_irq_handler(9)pdc_work_cb(9)pdc_ring_init(9)pdc_desc_count(9)pdc_rings_full(9)pdc_last_tx_done(9)pdc_send_data(9)pdc_hw_init(9)pdc_hw_disable(9)pdc_interrupts_init(9)pdc_mb_init(9)pdc_dt_read(9)pdc_probe(9)
and that's the page, bestie!! π§ it lives down in ./drivers/mailbox and it is dated October 2026 β so like, future queen energy πβ¨ go read the buffers, you're gonna slay π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms