ti_sci_cmd_clk_is_auto(9)

👑 ti_sci_cmd_clk_is_auto(9) — Kernel API Manual energy ✨

okay so bestie, we're diving into the Kernel API Manual today and the star of the show is ti_sci_cmd_clk_is_auto — literally the glow-up check for your clocks 🌸

---

💖 NAME 💖

ti_sci_cmd_clk_is_auto — Is the clock being auto managed

Like, is this clock out here living its best life on autopilot or not? That's the whole vibe check 🦋

---

✨ SYNOPSIS ✨

int ti_sci_cmd_clk_is_auto (const struct ti_sci_handle *handle , u32
dev_id , u32 clk_id , bool *req_state );

---

🎀 ARGUMENTS 🎀

• handle — pointer to TI SCI handle. Yes bestie, the whole SCI handle, no shortcuts 💅
• dev_id — Device identifier this request is for. Gotta tell it which device we're talking about 🫶
• clk_id — Clock identifier for the device for this request. Each device has it's own set of clock inputs. This indexes which clock input to modify. iykyk — every device has its own little clock family and you're picking which one 👑
• req_state — state indicating if the clock is auto managed. This is where the answer lands, so it can tell you the truth fr fr 📩

---

🌈 RETURN 🌈

0 if all went well, else returns appropriate error value. Slay when it's zero, and when it's not… well, it's giving error, handle it with grace 😭

---

🦋 SEE ALSO 🦋

Kernel file ./drivers/firmware/ti_sci.c — and the whole iconic 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_debug_show(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_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)

---

No cap: the return value is your whole answer here. 0 means all good, anything else means read the error and deal with it 💀

---

mwah 💋 that's the whole page!! this cutie lives in ./drivers/firmware, dated October 2026, and it's filed under Kernel API Manual as ti_sci_cmd_clk_is_auto(9) — periodt, go check your clocks bestie 🎀💜