ti_sci_debug_show(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ ti_sci_debug_show(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’… and lemme tell you about ti_sci_debug_show β€” she's literally the helper that dumps the debug log. that's it, that's the vibe πŸŽ€


🌸 NAME 🌸

ti_sci_debug_show β€” a lil helper whose whole job is to dump the debug log, no cap 🫢


⭐ SYNOPSIS ⭐

int ti_sci_debug_show (struct seq_file *s , void *unused );

like, that's the whole signature. look at her. iconic.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • s β€” the sequence file pointer, yeah that one πŸ’«
  • unused β€” literally just says "unused." so… unused. she's there, she's not doing anything, she's main character energy anyway πŸ™ˆ

πŸ’– RETURN πŸ’–

returns 0 β€” that's it, that's the whole return value, zero, slay ✨


πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is long long, so buckle up bestie, we're going through all of them πŸ’€ (iykyk)

first up, the kernel file herself:

  • Kernel file ./drivers/firmware/ti_sci.c

and then the whole friend group:

struct ti_sci_xfer(9), struct ti_sci_xfers_info(9), struct ti_sci_desc(9), struct ti_sci_irq(9), struct ti_sci_info(9), ti_sci_debugfs_create(9), ti_sci_dump_header_dbg(9), ti_sci_rx_callback(9), ti_sci_get_one_xfer(9), ti_sci_put_one_xfer(9), ti_sci_do_xfer(9), ti_sci_cmd_get_revision(9), ti_sci_is_response_ack(9), ti_sci_set_device_state(9), ti_sci_get_device_state(9), ti_sci_cmd_get_device(9), ti_sci_cmd_get_device_exclusive(9), ti_sci_cmd_idle_device(9), ti_sci_cmd_idle_device_exclusive(9), ti_sci_cmd_put_device(9), ti_sci_cmd_dev_is_valid(9), ti_sci_cmd_dev_get_clcnt(9), ti_sci_cmd_dev_is_idle(9), ti_sci_cmd_dev_is_stop(9), ti_sci_cmd_dev_is_on(9), ti_sci_cmd_dev_is_trans(9), ti_sci_cmd_set_device_resets(9), ti_sci_cmd_get_device_resets(9), ti_sci_set_clock_state(9), ti_sci_cmd_get_clock_state(9), ti_sci_cmd_get_clock(9), ti_sci_cmd_idle_clock(9), ti_sci_cmd_put_clock(9), ti_sci_cmd_clk_is_auto(9), ti_sci_cmd_clk_is_on(9), ti_sci_cmd_clk_is_off(9), ti_sci_cmd_clk_set_parent(9), ti_sci_cmd_clk_get_parent(9), ti_sci_cmd_clk_get_num_parents(9), ti_sci_cmd_clk_get_match_freq(9), ti_sci_cmd_clk_set_freq(9), ti_sci_cmd_clk_get_freq(9), ti_sci_cmd_prepare_sleep(9), ti_sci_msg_cmd_query_fw_caps(9), ti_sci_cmd_set_io_isolation(9), ti_sci_msg_cmd_lpm_wake_reason(9), ti_sci_cmd_set_device_constraint(9), ti_sci_cmd_set_latency_constraint(9), ti_sci_cmd_lpm_abort(9), ti_sci_get_resource_range(9), ti_sci_cmd_get_resource_range(9), ti_sci_cmd_get_resource_range_from_shost(9), ti_sci_manage_irq(9), ti_sci_irq_hash(9), ti_sci_irq_equal(9), ti_sci_set_irq(9), ti_sci_free_irq(9), ti_sci_cmd_set_irq(9), ti_sci_cmd_set_event_map(9), ti_sci_cmd_free_irq(9), ti_sci_cmd_free_event_map(9), ti_sci_cmd_rm_ring_cfg(9), ti_sci_cmd_rm_psil_pair(9), ti_sci_cmd_rm_psil_unpair(9), ti_sci_cmd_rm_udmap_tx_ch_cfg(9), ti_sci_cmd_rm_udmap_rx_ch_cfg(9), ti_sci_cmd_rm_udmap_rx_flow_cfg(9), ti_sci_cmd_proc_request(9), ti_sci_cmd_proc_release(9), ti_sci_cmd_proc_handover(9), ti_sci_cmd_proc_set_config(9), ti_sci_cmd_proc_set_control(9), ti_sci_cmd_proc_get_status(9), ti_sci_get_handle(9), ti_sci_put_handle(9), devm_ti_sci_get_handle(9), ti_sci_get_by_phandle(9), devm_ti_sci_get_by_phandle(9), ti_sci_get_free_resource(9), ti_sci_release_resource(9), ti_sci_get_num_resources(9), devm_ti_sci_get_resource_sets(9), devm_ti_sci_get_of_resource(9), devm_ti_sci_get_resource(9)

literally the whole extended universe of ti_sci functions, go read them all, they ate πŸ”₯


and that's the page bestie πŸ’œ this little cutie lives over in ./drivers/firmware, and she was documented back in October 2026 β€” so go forth, dump that debug log, and remember: 0 is a perfectly valid return value and you are a perfectly valid person πŸŒˆβ­πŸ“

πŸ“¦ where this page comes from