Skip to content

ARM: OMAP3PLUS: IO daisychain support fixes

Kevin Hilman linux-arm-kernel linux-omap 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v3 Latest1 of 6 patches 0 repliesNew

1 of 6 patches is in this archive. The cover letter announces 6.

Patches in v3 No applies recorded yet

#Subject and filesSizeRepliesApplied
4/6ARM: OMAP3 PM: Enable IO Wake up+0 -02 replies

Reviews trailers per patch

The patch has no Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchKevin Hilman
SeriesR-b T-b
4/6

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v3 thread

Cover letter [PATCHv3 0/6] ARM: OMAP3PLUS: IO daisychain support fixes
Quoted 25 lines · Tero Kristo

Hi,

The previous version of this set was sent by Vishwanath BS, but as he is busy with other stuff, I am taking over.

Some basic info about this set based on comments received on set v2. IO chain is now enabled always, and a re-trigger for the chain is done during hwmod enable / disable. This means that IO chain is always armed according to the latest pad specific WAKE_ENABLE setting, and if it is modified, the IO chain needs to be re-armed (thus the hooks within omap_hwmod code.) Having IO chain armed all the time allows us to receive IO event interrupts even during non-sleep states if the corresponding hardware module is disabled, and is unable to detect any IO activity itself.

Version 3 contains the following changes:

- global: renamed *_trigger_wuclk_ctrl funcs as *_trigger_io_chain
- patch 3: added trigger WUCLKIN disable at the end of omap4_trigger_io_chain (fix pulled from the omap4 core retention set)
- patch 5: added function pointer for using machine specific io_chain trigger function, initialized during boot
- patch 7 dropped as the support capability for omap3 is now handled as part of patch 5 init

Quoted 3 lines

Tested on omap3 beagle + omap4 blaze boards. Suspend / resume works, and hwmod_io interrupts are generated. Omap4 was tested with the core retention support set.

Reviewed-by Kevin Hilman <[email protected]>

I also tested this on 3430/n900 and verified IO wakeups are working as expected.

Tested-by Kevin Hilman <[email protected]>

Paul, as discussed on IRC, when you're OK with it, this can go through your queue since it's mostly PRM core code.

Kevin

Read the cover letter in its thread