STRUCT TI_SCI_MSG_REQ_SET_IO_ISOLATION(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct ti_sci_msg_req_set_io_isolation(9) πŸ’…

okay bestie, welcome to the Kernel API Manual β€” yes, that's the manual name, and yes, this page is a little struct in it. Buckle up, it's a short one but it's lowkey important 🫢


✨ NAME ✨

struct ti_sci_msg_req_set_io_isolation β€” it's literally the request for TI_SCI_MSG_SET_IO_ISOLATION. That's it, that's the whole name. Periodt πŸ’…


🌸 SYNOPSIS 🌸

here's the whole shape of it, no cap:

struct ti_sci_msg_req_set_io_isolation {
    struct ti_sci_msg_hdr hdr;
    u8 state;
 };

look at her. two members. main character energy, minimal effort πŸ’–


πŸŽ€ Members πŸŽ€

  • hdr β€” the generic header, the little backpack every TI-SCI message carries around πŸŽ’
  • state β€” the deseared state of the IO isolation. yep, that's what the original says, we don't editorialise, we just report 🫑

πŸ¦‹ Description πŸ¦‹

so this message is the one you send when you want to enable or disable IO isolation for low power modes ✨ like, it's the "hey can we isolate the IO pretty please" note.

and the response? it's just a generic ACK / NACK message. that's it. no essay back, just a thumbs up or a thumbs down 😭


🌈 SEE ALSO 🌈

the whole squad, fr fr β€” Kernel file ./drivers/firmware/ti_sci.h plus:

  • struct ti_sci_msg_hdr(9)
  • struct ti_sci_msg_resp_version(9)
  • struct ti_sci_msg_req_reboot(9)
  • struct ti_sci_msg_resp_query_fw_caps(9)
  • struct ti_sci_msg_req_set_device_state(9)
  • struct ti_sci_msg_req_get_device_state(9)
  • struct ti_sci_msg_resp_get_device_state(9)
  • struct ti_sci_msg_req_set_device_resets(9)
  • struct ti_sci_msg_req_set_clock_state(9)
  • struct ti_sci_msg_req_get_clock_state(9)
  • struct ti_sci_msg_resp_get_clock_state(9)
  • struct ti_sci_msg_req_set_clock_parent(9)
  • struct ti_sci_msg_req_get_clock_parent(9)
  • struct ti_sci_msg_resp_get_clock_parent(9)
  • struct ti_sci_msg_req_get_clock_num_parents(9)
  • struct ti_sci_msg_resp_get_clock_num_parents(9)
  • struct ti_sci_msg_req_query_clock_freq(9)
  • struct ti_sci_msg_resp_query_clock_freq(9)
  • struct ti_sci_msg_req_set_clock_freq(9)
  • struct ti_sci_msg_req_get_clock_freq(9)
  • struct ti_sci_msg_resp_get_clock_freq(9)
  • struct ti_sci_msg_req_prepare_sleep(9)
  • struct ti_sci_msg_resp_lpm_wake_reason(9)
  • struct ti_sci_msg_req_lpm_set_device_constraint(9)
  • struct ti_sci_msg_req_lpm_set_latency_constraint(9)
  • struct ti_sci_msg_req_get_resource_range(9)
  • struct ti_sci_msg_resp_get_resource_range(9)
  • struct ti_sci_msg_req_manage_irq(9)
  • struct ti_sci_msg_rm_ring_cfg_req(9)
  • struct ti_sci_msg_psil_pair(9)
  • struct ti_sci_msg_psil_unpair(9)
  • struct ti_sci_msg_udmap_rx_flow_cfg(9)
  • struct rm_ti_sci_msg_udmap_rx_flow_opt_cfg(9)
  • struct ti_sci_msg_rm_udmap_tx_ch_cfg_req(9)
  • struct ti_sci_msg_rm_udmap_rx_ch_cfg_req(9)
  • struct ti_sci_msg_rm_udmap_flow_cfg_req(9)
  • struct ti_sci_msg_req_proc_request(9)
  • struct ti_sci_msg_req_proc_release(9)
  • struct ti_sci_msg_req_proc_handover(9)
  • struct ti_sci_msg_req_set_config(9)
  • struct ti_sci_msg_req_set_ctrl(9)
  • struct ti_sci_msg_req_get_status(9)
  • struct ti_sci_msg_resp_get_status(9)

genuine question: is that not the longest SEE ALSO you've ever seen?? go off king πŸ‘‘

and that's the whole page, bestie 🧚 from ./drivers/firmware, dated October 2026 β€” literally a future icon πŸ’œ mwah, go isolate some IO responsibly πŸ“

πŸ“¦ where this page comes from