omap_hwmod_...module_range(9)

💖 NAME 💖

omap_hwmod_parse_module_range — map module IO range from device tree. 🗺️✨

okay so this page is from the Kernel API Manual, and its page title is omap_hwmod_...module_range(9). The NAME section is doing exactly what it says on the tin, bestie. 💅

---

✨ SYNOPSIS ✨

int omap_hwmod_parse_module_range (struct omap_hwmod *oh , struct
       device_node *np , struct resource *res );

That's the signature, copied with care: omap_hwmod_parse_module_range, with oh, np, and res as the arguments. 🎀

---

🫶 ARGUMENTS 🫶

• oh — struct omap_hwmod *
• np — struct device_node *
• res — -- undescribed -- (that's genuinely all the page gives us here, bestie — no invented lore 💀)

---

🦋 DESCRIPTION 🦋

Parse the device tree range an interconnect target module provides for its child device IP blocks. That's the whole mood. 🌈

This way we can support the old "ti,hwmods" property with just dts data, without a need for platform data for IO resources. And plot twist: we don't need all the child IP device nodes available in the dts. periodt. 💖

---

🔥 SEE ALSO 🔥

Kernel file: ./arch/arm/mach-omap2/omap_hwmod.c — and then the whole reference squad, in order:

• struct clkctrl_provider(9)
• struct omap_hwmod_reset(9)
• struct omap_hwmod_soc_ops(9)
• _update_sysc_cache(9)
• _write_sysconfig(9)
• _set_master_standbymode(9)
• _set_slave_idlemode(9)
• _set_clockactivity(9)
• _set_softreset(9)
• _clear_softreset(9)
• _wait_softreset_complete(9)
• _set_dmadisable(9)
• _set_module_autoidle(9)
• _enable_wakeup(9)
• _add_initiator_dep(9)
• _del_initiator_dep(9)
• _init_main_clk(9)
• _init_interface_clks(9)
• _init_opt_clks(9)
• _enable_clocks(9)
• _omap4_clkctrl_managed_by_clkfwk(9)
• _omap4_has_clkctrl_clock(9)
• _disable_clocks(9)
• _omap4_enable_module(9)
• _omap4_wait_target_disable(9)
• _save_mpu_port_index(9)
• _find_mpu_rt_port(9)
• _enable_sysc(9)
• _idle_sysc(9)
• _shutdown_sysc(9)
• _lookup(9)
• _init_clkdm(9)
• _init_clocks(9)
• _lookup_hardreset(9)
• _assert_hardreset(9)
• _deassert_hardreset(9)
• _read_hardreset(9)
• _are_all_hardreset_lines_asserted(9)
• _are_any_hardreset_lines_asserted(9)
• _omap4_disable_module(9)
• _ocp_softreset(9)
• _reset(9)
• _omap4_update_context_lost(9)
• _omap4_get_context_lost(9)
• _enable(9)
• _idle(9)
• _shutdown(9)
• of_dev_hwmod_lookup(9)
• omap_hwmod_fix_mpu_rt_idx(9)
• _init_mpu_rt_base(9)
• _init(9)
• _setup_iclk_autoidle(9)
• _setup_reset(9)
• _setup_postsetup(9)
• _setup(9)
• _register(9)
• _add_link(9)
• _register_link(9)
• _omap2xxx_3xxx_wait_target_ready(9)
• _omap4_wait_target_ready(9)
• _omap2_assert_hardreset(9)
• _omap2_deassert_hardreset(9)
• _omap2_is_hardreset_asserted(9)
• _omap4_assert_hardreset(9)
• _omap4_deassert_hardreset(9)
• _omap4_is_hardreset_asserted(9)
• _omap4_disable_direct_prcm(9)
• _am33xx_deassert_hardreset(9)
• omap_hwmod_softreset(9)
• omap_hwmod_lookup(9)
• omap_hwmod_for_each(9)
• omap_hwmod_register_links(9)
• _ensure_mpu_hwmod_is_setup(9)
• omap_hwmod_setup_one(9)
• omap_hwmod_check_sysc(9)
• omap_hwmod_init_regbits(9)
• omap_hwmod_init_reg_offs(9)
• omap_hwmod_init_sysc_flags(9)
• omap_hwmod_init_idlemodes(9)
• omap_hwmod_check_module(9)
• omap_hwmod_allocate_module(9)
• omap_hwmod_init_module(9)
• omap_hwmod_setup_earlycon_flags(9)
• omap_hwmod_setup_all(9)
• omap_hwmod_enable(9)
• omap_hwmod_idle(9)
• omap_hwmod_shutdown(9)
• omap_hwmod_get_mpu_rt_va(9)
• omap_hwmod_assert_hardreset(9)
• omap_hwmod_deassert_hardreset(9)
• omap_hwmod_for_each_by_class(9)
• omap_hwmod_set_postsetup_state(9)
• omap_hwmod_init(9)

---

okay that's the page, bestie! Source path on the footer: ./arch/arm/mach-omap2; date: October 2026; page: omap_hwmod_...module_range(9) from the Kernel API Manual. bye, mwah 💋✨