scmi_xfer_in...ter_unlocked(9)
πΈ scmi_xfer_in...ter_unlocked(9) πΈ
okay bestie, you're in the Kernel API Manual and the main character is scmi_xfer_in...ter_unlocked(9) β yes, the title is literally truncated like that, and we're keeping it π
.
π NAME π
scmi_xfer_inflight_register_unlocked β Register the xfer as in-flight β¨
β¨ SYNOPSIS β¨
the exact signature, no edits, no cap:
void scmi_xfer_inflight_register_unlocked (struct scmi_xfer *xfer ,
struct scmi_xfers_info *minfo );
π ARGUMENTS π
xferβ The xfer to register π«Άminfoβ Pointer to Tx/Rx Message management info based on channel type π«
π¦ DESCRIPTION π¦
lowkey important note: this helper assumes that the xfer to be registered as in-flight had been built using an xfer sequence number which still corresponds to a free slot in the xfer_alloc_table.
That's the assumption it's rolling with, periodt πΈ
π CONTEXT π
Assumes to be called with xfer_lock already acquired. Periodt. So bestie, lock first β that's the rune it's living by π
π SEE ALSO π
Kernel file ./drivers/firmware/arm_scmi/driver.c β and the whole squad:
struct scmi_xfers_info(9)struct scmi_protocol_instance(9)struct scmi_info(9)scmi_create_protocol_devices(9)scmi_xfer_token_set(9)scmi_xfer_token_clear(9)scmi_xfer_inflight_register(9)scmi_xfer_raw_inflight_register(9)scmi_xfer_pending_set(9)scmi_xfer_get(9)scmi_xfer_raw_get(9)scmi_xfer_raw_channel_get(9)__scmi_xfer_put(9)scmi_xfer_raw_put(9)scmi_xfer_lookup_unlocked(9)scmi_bad_message_trace(9)scmi_msg_response_validate(9)scmi_xfer_state_update(9)scmi_xfer_command_acquire(9)scmi_rx_callback(9)xfer_put(9)scmi_wait_for_message_response(9)scmi_xfer_raw_wait_for_message_response(9)do_xfer(9)do_xfer_with_response(9)xfer_get_init(9)version_get(9)scmi_set_protocol_priv(9)scmi_get_protocol_priv(9)scmi_common_extended_name_get(9)scmi_common_get_max_msg_size(9)scmi_protocol_msg_check(9)struct scmi_iterator(9)scmi_revision_area_get(9)scmi_protocol_version_negotiate(9)scmi_protocol_version_initialize(9)scmi_alloc_init_protocol_instance(9)scmi_get_protocol_instance(9)scmi_protocol_acquire(9)scmi_protocol_release(9)scmi_devm_protocol_get(9)scmi_devm_protocol_acquire(9)scmi_devm_protocol_put(9)scmi_is_transport_atomic(9)scmi_handle_get(9)scmi_handle_put(9)scmi_channels_setup(9)
mwah π β this little love letter is from ./drivers/firmware/arm_scmi, dated October 2026, and it's literally titled scmi_xfer_in...ter_unlocked(9); go register those xfers, bestie π
π¦ 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