| author | Suman Anna <s-anna@ti.com> | |
| Thu, 14 Feb 2019 21:27:16 +0000 (15:27 -0600) | ||
| committer | Suman Anna <s-anna@ti.com> | |
| Sun, 24 Feb 2019 01:20:49 +0000 (19:20 -0600) | ||
| commit | d7da1cae0372643978066723f98fed32b057fe41 | |
| tree | 8454c68db2531944fe4ea661e485bf623e838872 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 9202afc760d14356e296f54222ed222085c834bc | commit | diff |
ARM: OMAP2+: use pdata quirks for PRUSS reset lines on AM335x
The omap_device API is needed to perform the reset management for
any IP instances with PRCM RSTCTRL registers (hard reset lines).
This API is limited to the mach-omap2 layer, and cannot be exposed
to drivers layer directly. So use platform data ops and pdata quirks
for the PRUSS IP in AM335x SoCs to plumb the required omap_device
API. The PRUSS SoC bus driver can then use these pdata ops to
achieve the required reset functionality.
This is being implemented this way as there is no separate reset
driver at the moment.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Keerthy <j-keerthy@ti.com>
The omap_device API is needed to perform the reset management for
any IP instances with PRCM RSTCTRL registers (hard reset lines).
This API is limited to the mach-omap2 layer, and cannot be exposed
to drivers layer directly. So use platform data ops and pdata quirks
for the PRUSS IP in AM335x SoCs to plumb the required omap_device
API. The PRUSS SoC bus driver can then use these pdata ops to
achieve the required reset functionality.
This is being implemented this way as there is no separate reset
driver at the moment.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Keerthy <j-keerthy@ti.com>
| arch/arm/mach-omap2/pdata-quirks.c | diff | blob | history |