author | Suman Anna <s-anna@ti.com> | |
Wed, 16 Mar 2016 19:49:18 +0000 (14:49 -0500) | ||
committer | Suman Anna <s-anna@ti.com> | |
Mon, 4 Mar 2019 16:02:38 +0000 (10:02 -0600) | ||
commit | 8ffd3fdfbed9d414543a69bea94882a1059b57de | |
tree | 58b909b94ed3a7677b21d0effe91bd2fb179a1ae | tree | snapshot (tar.xz tar.gz zip) |
parent | 8122fe7982d28ec50e3030c40703589b7e7e0f57 | commit | diff |
ARM: OMAP2+: Extend rproc pdata-quirks for IPUs & DSP1 on DRA7
The remote processors on DRA7xx requires similar device management
pdata-quirks (reset control, clocking, dmtimer API wrappers for
enabling both system and watchdog timers) as the IPU and DSP
processors on OMAP4/OMAP5. All these pdata ops are identical to
the ones used on OMAP4/OMAP5, so extend the existing rproc pdata
quirks to the most common remote processor subsystems on DRA7xx
family of SoCs - IPU1, IPU2 and DSP1.
The pdata quirks need to match the starting address in the auxdata
for the respective processors, as the same compatible string is used
for all the instances of the remote processor of the same type. The
pdata quirks will be removed once the dependencies against arch/arm
layers are resolved.
Signed-off-by: Suman Anna <s-anna@ti.com>
The remote processors on DRA7xx requires similar device management
pdata-quirks (reset control, clocking, dmtimer API wrappers for
enabling both system and watchdog timers) as the IPU and DSP
processors on OMAP4/OMAP5. All these pdata ops are identical to
the ones used on OMAP4/OMAP5, so extend the existing rproc pdata
quirks to the most common remote processor subsystems on DRA7xx
family of SoCs - IPU1, IPU2 and DSP1.
The pdata quirks need to match the starting address in the auxdata
for the respective processors, as the same compatible string is used
for all the instances of the remote processor of the same type. The
pdata quirks will be removed once the dependencies against arch/arm
layers are resolved.
Signed-off-by: Suman Anna <s-anna@ti.com>
arch/arm/mach-omap2/pdata-quirks.c | diff | blob | history |