devm_ti_sci_get_of_resource(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, we're in the Kernel API Manual and this is the devm_ti_sci_get_of_resource(9) page β€” it's giving β€œgrab the TISCI resource that belongs to this device” energy, and honestly? iconic πŸ’–βœ¨

🌸 NAME 🌸

devm_ti_sci_get_of_resource β€” Get a TISCI resource assigned to a device 🫢

✨ SYNOPSIS ✨

lowkey just this signature, no cap:

struct ti_sci_resource * devm_ti_sci_get_of_resource (const struct ti_sci_handle *handle , struct device *dev , u32 dev_id , char *of_prop );

πŸŽ€ ARGUMENTS πŸŽ€

  • handle β€” TISCI handle. that's the main character you pass in 🫑
  • dev β€” Device pointer to which the resource is assigned. yes, this device bestie.
  • dev_id β€” TISCI device id to which the resource is assigned. it's an id, periodt.
  • of_prop β€” property name by which the resource are represented. yep, that's the property-name string.

πŸ’« RETURN πŸ’«

Pointer to ti_sci_resource if all went well else appropriate error pointer. so if it slays, you get the pointer; if not, you get an appropriate error pointer 😭🫢

🌈 SEE ALSO 🌈

Kernel file ./drivers/firmware/ti_sci.c β€” plus the whole TISCI ensemble: 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_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_resource(9).


okay bye bestie! source/version: ./drivers/firmware; date: October 2026; page: devm_ti_sci_get_of_resource(9) β€” mwah πŸ’‹πŸ’–

πŸ“¦ where this page comes from