Add D2D clockdomain on OMAP3 ES2+
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | OMAP3 PM: convert open-coded iterator to use pwrdm_for_each_clkdm()arch/ | +18 | 0 replies | |
| 2/2 | OMAP3 clockdomains: include D2D clockdomain on 34xx ES2+arch/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Add D2D clockdomain on OMAP3 ES2+
Hello,
This patch series adds D2D (die-to-die) clockdomain handling into OMAP3 ES2+ builds. It seems the D2D clockdomain logic is still present on the chip and must be manually programmed to allow the CORE_D2D clockdomain to go inactive.
For this to work, the pm34xx.c code also had to be modified to use the pwrdm_for_each_clkdm() iterator, lest the existing for-loop fall off the end of pwrdm->pwrdm_clkdms[]. This also should fix an oops with CONFIG_PM on any 3430ES1 boards out there.
Tested on 3430SDP ES2.0.
- Paul
diffstat:
arch/arm/mach-omap2/clockdomains.h | 9 ++++++++- arch/arm/mach-omap2/pm34xx.c | 23 ++++++++++++++++++----- 2 files changed, 26 insertions(+), 6 deletions(-)
size:
text data bss dec hex filename
3280225 155416 98792 3534433 35ee61 vmlinux.3430sdp.orig 3280305 155416 98792 3534513 35eeb1 vmlinux.3430sdp.patched