STRUCT TI_SCI_MSG_REQ_SET_DEVICE_RESETS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ struct ti_sci_msg_req_set_device_resets(9) πŸ¦‹

okay bestie, welcome to the Kernel API Manual πŸ’– β€” this is the page for struct ti_sci_msg_req_set_device_resets, and it's literally all about setting the desired resets configuration of the device. slay.


✨ NAME ✨

struct ti_sci_msg_req_set_device_resets β€” set the desired resets configuration of the device πŸŽ€


🌈 SYNOPSIS 🌈

struct ti_sci_msg_req_set_device_resets {
    struct ti_sci_msg_hdr hdr;
    u32 id;
    u32 resets;
};

πŸ’… Members πŸ’…

  • hdr β€” generic header, the little intro bit 🫢
  • id β€” tells you which device to modify, like the device's @ in the group chat πŸ‘‘
  • resets β€” a bit field of resets for the device. The meaning, behavior, and usage of the reset flags are device specific. 0 for a bit indicates releasing the reset represented by that bit, while 1 indicates keeping it held. no cap, that's the whole vibe check on this field πŸŽ€

πŸ”₯ Description πŸ”₯

Request type is TI_SCI_MSG_SET_DEVICE_RESETS, responded with a generic ACK/NACK message. periodt. πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/firmware/ti_sci.h

  • 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_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_req_set_io_isolation(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)

okay bestie, that's the whole page β€” source/version: ./drivers/firmware, dated October 2026. you ate that, fr fr πŸ’–βœ¨

πŸ“¦ where this page comes from