ti_sci_cmd_clk_is_on(9)

💅 ti_sci_cmd_clk_is_on(9) — like, is the clock ON or not, bestie?

okay so this is a page straight out of the Kernel API Manual, and it's literally just the vibe check for a clock. one question, one answer, no drama. ✨

---

🌸 NAME 🌸

ti_sci_cmd_clk_is_on — Is the clock ON 🕐👀

---

🎀 SYNOPSIS 🎀

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

---

✨ ARGUMENTS ✨

• handle — pointer to the TI SCI handle. this is your golden ticket to the whole subsystem, bestie 🎟️
• dev_id — the Device identifier this request is for
• clk_id — the Clock identifier for the device for this request. here's the tea: each device has its own set of clock inputs, and this number indexes which clock input you're modifying ☕⏰
• req_state — state indicating if the clock is managed by us and enabled (i.e. we are the main character here 👑)
• curr_state — state indicating if the clock is ready for operation (like, actually functioning, not just saying it is 💀)

---

🔥 RETURN 🔥

0 if all went well — slay, no notes 💖 — otherwise it returns the appropriate error value. so if you get anything that isn't 0, that's your sign 😭

---

🦋 SEE ALSO 🦋

Kernel file ./drivers/firmware/ti_sci.c, plus the whole extended 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_auto(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)

like I said. whole friend group. iykyk 🫶

---

ngl the entire function is one question: is it on? but the answer lives in two bool * out-params, so read them carefully before you @ anyone 🧚

---

that's the whole page, bestie — go forth and check those clocks 💜

✧･ﾟ signed, sealed, and shipped from ./drivers/firmware in October 2026 — ti_sci_cmd_clk_is_on(9), Kernel API Manual, iconic as always 🎀✨