mcps_data_request(9)

🌸 mcps_data_request(9) — or, like, the send-data glow-up 💅

okay bestie, welcome to the Kernel API Manual page for mcps_data_request 💖 yes that's the manual name, no I'm not gonna make you read it in a boring header line, we're doing this properly.

So real talk: this one is the "Send Data" request, and it does exactly what it says on the tin — it's the request according to the API Spec. Main character energy from the jump. 🎀

---

✨ SYNOPSIS ✨

u8 mcps_data_request (u8 src_addr_mode , u8 dst_address_mode , u16
dst_pan_id , union macaddr *dst_addr , u8 msdu_length , u8 *msdu , u8
msdu_handle , u8 tx_options , struct secspec *security , void
*device_ref );

That's the whole thing, no cap — copy it exactly, don't get cute with the types. 🫶

---

🦋 ARGUMENTS 🦋

Ten arguments, ten little besties. Here's the vibe check on each one, and I'm keeping the names exactly as they are, because renaming kernel args is not the slay you think it is:

• src_addr_mode — Source Addressing Mode.
• dst_address_mode — Destination Addressing Mode.
• dst_pan_id — Destination PAN ID.
• dst_addr — Pointer to Destination Address.
• msdu_length — length of Data.
• msdu — Pointer to Data.
• msdu_handle — Handle of Data.
• tx_options — Tx Options Bit Field.
• security — Pointer to Security Structure or NULL.
• device_ref — Nondescript pointer to target device. (Nondescript is literally the word, I'm not making that up, she's mysterious and that's fine 💀)

---

👑 RETURN 👑

It hands you back an 802.15.4 status code of action. That's it, that's the whole return section. Short queen behavior. ✨

---

🌈 SEE ALSO 🌈

okay this is the part where the page goes FULL group chat, because there are so many references and every single one of them is here. Kernel file ./drivers/net/ieee802154/ca8210.c and then:

• struct cas_control(9)
• struct ca8210_test(9)
• struct ca8210_priv(9)
• struct work_priv_container(9)
• struct ca8210_platform_data(9)
• struct fulladdr(9)
• union macaddr(9)
• struct secspec(9)
• link_to_linux_err(9)
• ca8210_test_int_driver_write(9)
• ca8210_reset_send(9)
• ca8210_mlme_reset_worker(9)
• ca8210_rx_done(9)
• ca8210_spi_transfer_complete(9)
• ca8210_spi_transfer(9)
• ca8210_spi_exchange(9)
• ca8210_interrupt_handler(9)
• tdme_setsfr_request_sync(9)
• tdme_chipinit(9)
• tdme_channelinit(9)
• tdme_checkpibattribute(9)
• tdme_settxpower(9)
• mlme_reset_request_sync(9)
• mlme_set_request_sync(9)
• hwme_set_request_sync(9)
• hwme_get_request_sync(9)
• ca8210_async_xmit_complete(9)
• ca8210_skb_rx(9)
• ca8210_net_rx(9)
• ca8210_skb_tx(9)
• ca8210_start(9)
• ca8210_stop(9)
• ca8210_xmit_async(9)
• ca8210_get_ed(9)
• ca8210_set_channel(9)
• ca8210_set_hw_addr_filt(9)
• ca8210_set_tx_power(9)
• ca8210_set_cca_mode(9)
• ca8210_set_cca_ed_level(9)
• ca8210_set_csma_params(9)
• ca8210_set_frame_retries(9)
• ca8210_test_int_open(9)
• ca8210_test_check_upstream(9)
• ca8210_test_int_user_write(9)
• ca8210_test_int_user_read(9)
• ca8210_test_int_ioctl(9)
• ca8210_test_int_poll(9)
• ca8210_get_platform_data(9)
• ca8210_config_extern_clk(9)
• ca8210_register_ext_clock(9)
• ca8210_unregister_ext_clock(9)
• ca8210_reset_init(9)
• ca8210_interrupt_init(9)
• ca8210_dev_com_init(9)
• ca8210_dev_com_clear(9)
• ca8210_hw_setup(9)
• ca8210_test_interface_init(9)
• ca8210_test_interface_clear(9)
• ca8210_remove(9)
• ca8210_probe(9)

Like… sixty-ish references, and every single one of them ate. That's the whole list, don't let anyone tell you I skipped one. 💅

real talk bestie: the entire reference crew lives under ./drivers/net/ieee802154, so that's where you go when you wanna read more.

---

and that's the page!! 🎀 this little love letter came from source ./drivers/net/ieee802154, dated October 2026 — mwah, go forth and send that data, iykyk 💖🦋✨