Home
last modified time | relevance | path

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

12345

/kernel/linux/linux-5.10/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 …]
DMakefile14 hwmod-common = omap_hwmod.o omap_hwmod_reset.o \
19 obj-$(CONFIG_ARCH_OMAP2) += $(omap-2-3-common) $(hwmod-common)
20 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
21 obj-$(CONFIG_ARCH_OMAP4) += $(hwmod-common) $(secure-common)
22 obj-$(CONFIG_SOC_AM33XX) += $(hwmod-common) $(secure-common)
23 obj-$(CONFIG_SOC_OMAP5) += $(hwmod-common) $(secure-common)
24 obj-$(CONFIG_SOC_AM43XX) += $(hwmod-common) $(secure-common)
25 obj-$(CONFIG_SOC_DRA7XX) += $(hwmod-common) $(secure-common)
196 # hwmod data
Domap_device.c90 * _add_hwmod_clocks_clkdev - Add clkdev entry for hwmod optional clocks
95 * For the main clock and every optional clock present per hwmod per
166 dev_err(&pdev->dev, "Cannot lookup hwmod '%s'\n", in omap_device_build_from_dt()
295 * Using the primary hwmod, query the context loss count for this
303 * return the context loss counter for that hwmod, otherwise return
407 dev_warn(dev, "%s: FIXME: missing hwmod/omap_dev info\n", __func__); in _od_fail_runtime_suspend()
413 dev_warn(dev, "%s: FIXME: missing hwmod/omap_dev info\n", __func__); in _od_fail_runtime_resume()
617 * omap_device_get_by_hwmod_name() - convert a hwmod name to
619 * @oh_name: name of the hwmod device
621 * Returns back a struct device * pointer associated with a hwmod
[all …]
Domap_hwmod_reset.c9 * hwmod code to call these functions, which are to be located under
66 * written in respective KICK registers. This is needed for hwmod to write into
87 * registers once hwmod completes its write into sysconfig register.
Domap_hwmod_3xxx_data.c2235 * XXX Should be connected to an IPSS hwmod, not the L3 directly;
2236 * but this will probably require some additional hwmod core support,
2248 * XXX Should be connected to an IPSS hwmod, not the L4_CORE directly;
2249 * but this will probably require some additional hwmod core support,
2276 * XXX Should be connected to an IPSS hwmod, not the L3 directly;
2277 * but this will probably require some additional hwmod core support,
2289 * XXX Should be connected to an IPSS hwmod, not the L4_CORE directly;
2290 * but this will probably require some additional hwmod core support,
2432 /* crypto hwmod links */
2457 /* 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
82 /* OMAP hwmod classes - forward declarations */
/kernel/linux/linux-6.6/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()
/kernel/linux/linux-6.6/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.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/
Di2c-omap.txt23 from omap hwmod data base during device registration.
24 Future plan is to migrate hwmod data base contents into device tree
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/
Domap-spi.txt9 - ti,hwmods: Name of the hwmod associated to the McSPI
25 [hwmod populated DMA resources]
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/can/
Dc_can.txt33 resources from TI, omap hwmod data base during device registration.
34 Future plan is to migrate hwmod data base contents into device tree
/kernel/linux/linux-6.6/include/clocksource/
Dtimer-ti-dm.h8 * Platform device conversion and hwmod support.
55 /* timer capabilities used in hwmod database */
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/
Delm.txt9 - ti,hwmods: Name of the hwmod associated to the elm
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/watchdog/
Domap-wdt.txt5 - ti,hwmods : Name of the hwmod associated to the WDT
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/
Domap-wdt.txt5 - ti,hwmods : Name of the hwmod associated to the WDT
/kernel/linux/linux-6.6/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

12345