STRUCT ACPM_RX_DATA(9)
π struct acpm_rx_data β RX queue data π
okay bestie, so this is a page from the Kernel API Manual, and it's all about struct acpm_rx_data. That's the little data blob that keeps track of the RX queue. Slay. Let's get into it π«Ά
β¨ SYNOPSIS β¨
struct acpm_rx_data {
u32 *cmd;
size_t cmdcnt;
size_t rxcnt;
bool completed;
};
no cap, that's the whole vibe right there π
π Members π
cmdβ pointer to where the data shall be saved. literally just a pointer to the save spot, iykyk πcmdcntβ allocated capacity of thecmdbuffer, measured in 32-bit words. that's the capacity, not the length, bestie β know the difference π₯rxcntβ expected length of the response in 32-bit words. what you're expecting back, fr fr πcompletedβ a flag indicating if the firmware response has been fully processed.truemeans done-done, periodt β
π SEE ALSO π
okay so if you're going down this rabbit hole, here's the whole friend group π
- Kernel file
./drivers/firmware/samsung/exynos-acpm.c struct acpm_shmem(9)struct acpm_chan_shmem(9)struct acpm_queue(9)struct acpm_chan(9)struct acpm_info(9)struct acpm_match_data(9)acpm_get_saved_rx(9)acpm_get_rx(9)acpm_dequeue_by_polling(9)acpm_wait_for_queue_slots(9)acpm_prepare_xfer(9)acpm_wait_for_message_response(9)acpm_do_xfer(9)acpm_set_xfer(9)acpm_chan_shmem_get_params(9)acpm_achan_alloc_cmds(9)acpm_free_mbox_chans(9)acpm_channels_init(9)acpm_handle_put(9)devm_acpm_release(9)acpm_get_by_node(9)devm_acpm_get_by_node(9)devm_acpm_get_by_phandle(9)
and that's the whole page, bestie π go read the source at ./drivers/firmware/samsung, and this one's dated October 2026 β main character energy fr π¦β¨
π¦ 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