Home
last modified time | relevance | path

Searched full:hwmod (Results 1 – 25 of 53) sorted by relevance

123

/linux-6.12.1/arch/arm/mach-omap2/
Domap_hwmod.h22 * - implement default hwmod SMS/SDRC flags?
155 * struct omap_hwmod_rst_info - IPs reset lines use by hwmod
161 * locally to the hwmod.
170 * struct omap_hwmod_opt_clk - optional clocks used by this hwmod
205 * interface to interact with the hwmod. Used to add sleep dependencies
290 * struct omap_hwmod_class_sysconfig - hwmod class OCP_SYS* data
353 * by the common clock framework and not hwmod.
397 * SDRAM controller, etc. XXX probably belongs outside the main hwmod file
400 * controller, etc. XXX probably belongs outside the main hwmod file
415 * enabled. This prevents the hwmod code from being able to
[all …]
Domap_hwmod.c32 * OMAP hwmod provides a consistent way to describe the on-chip
35 * hardware database. OMAP hwmod provides a standard, consistent API
37 * hwmod provides a way for other core code, such as the Linux device
41 * Using hwmod
43 * Drivers won't call hwmod functions directly. That is done by the
47 * currently how hwmod data is communicated to drivers and to the
51 * From a layering perspective, here is where the OMAP hwmod code
82 * The OMAP hwmod code also will attempt to reset and idle all on-chip
91 * The hwmod code considers modules to be in one of several activity
93 * are registered via the hwmod code, proceed to the REGISTERED state.
[all …]
Domap_hwmod_3xxx_data.c2141 * XXX Should be connected to an IPSS hwmod, not the L3 directly;
2142 * but this will probably require some additional hwmod core support,
2154 * XXX Should be connected to an IPSS hwmod, not the L4_CORE directly;
2155 * but this will probably require some additional hwmod core support,
2182 * XXX Should be connected to an IPSS hwmod, not the L3 directly;
2183 * but this will probably require some additional hwmod core support,
2195 * XXX Should be connected to an IPSS hwmod, not the L4_CORE directly;
2196 * but this will probably require some additional hwmod core support,
2338 /* crypto hwmod links */
2362 /* 3430ES1-only hwmod links */
[all …]
Domap_hwmod_common_data.c26 * To be used by hwmod structure to specify the sysconfig offsets
42 * To be used by hwmod structure to specify the sysconfig offsets if the
Domap_hwmod_common_data.h3 * omap_hwmod_common_data.h - OMAP hwmod common macros and declarations
80 /* OMAP hwmod classes - forward declarations */
DMakefile10 hwmod-common = omap_hwmod.o \
18 obj-$(CONFIG_ARCH_OMAP2) += $(omap-2-3-common) $(hwmod-common)
19 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
194 # hwmod data
Domap_device.c96 * _add_hwmod_clocks_clkdev - Add clkdev entry for hwmod optional clocks
101 * For the main clock and every optional clock present per hwmod per
169 dev_err(&pdev->dev, "Cannot lookup hwmod '%s'\n", in omap_device_build_from_dt()
380 dev_warn(dev, "%s: FIXME: missing hwmod/omap_dev info\n", __func__); in _od_fail_runtime_suspend()
386 dev_warn(dev, "%s: FIXME: missing hwmod/omap_dev info\n", __func__); in _od_fail_runtime_resume()
/linux-6.12.1/Documentation/devicetree/bindings/arm/omap/
Domap.txt10 For the moment just point to the existing hwmod, the next step will be
11 to move data from hwmod to device-tree representation.
17 - ti,hwmods: list of hwmod names (ascii strings), that comes from the OMAP
19 one hwmod.
Dcounter.txt6 - ti,hwmods: Name of the hwmod associated to the counter, which is typically
Ddmm.txt14 - ti,hwmods: Name of the hwmod associated to DMM, which is typically "dmm"
Dl3-noc.txt13 - ti,hwmods: "l3_main_1", ... One hwmod for each noc domain.
/linux-6.12.1/include/clocksource/
Dtimer-ti-dm.h8 * Platform device conversion and hwmod support.
55 /* timer capabilities used in hwmod database */
/linux-6.12.1/Documentation/devicetree/bindings/net/
Dcpsw.txt64 resources from TI, omap hwmod data base during device registration.
65 Future plan is to migrate hwmod data base contents into device tree
Dti,davinci-mdio.yaml49 description: TI hwmod name
/linux-6.12.1/Documentation/devicetree/bindings/watchdog/
Domap-wdt.txt5 - ti,hwmods : Name of the hwmod associated to the WDT
/linux-6.12.1/Documentation/devicetree/bindings/sound/
Domap-dmic.txt9 - ti,hwmods: Name of the hwmod associated with OMAP dmic IP
Domap-mcbsp.txt19 - ti,hwmods: Name of the hwmod associated to the McBSP port
/linux-6.12.1/Documentation/devicetree/bindings/mfd/
Domap-usb-tll.txt8 - ti,hwmod : must contain "usb_tll_hs"
/linux-6.12.1/Documentation/devicetree/bindings/crypto/
Domap-aes.txt12 - ti,hwmods: Name of the hwmod associated with the AES module
Domap-des.txt6 - ti,hwmods: Name of the hwmod associated with the DES module
Dti,omap-sham.yaml32 description: Name of the hwmod associated with the SHAM module
/linux-6.12.1/include/linux/platform_data/
Di2c-omap.h13 * code using these constants in the hwmod class definition.
/linux-6.12.1/Documentation/devicetree/bindings/mtd/
Dti,elm.yaml42 Name of the HWMOD associated with ELM. This is for legacy
/linux-6.12.1/Documentation/devicetree/bindings/rng/
Domap_rng.yaml22 description: Name of the hwmod associated with the RNG module
/linux-6.12.1/Documentation/devicetree/bindings/remoteproc/
Dwkup_m3_rproc.txt27 - ti,hwmods: Name of the hwmod associated with the wkupm3 device.

123