aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/trace-event-scripting.c
diff options
context:
space:
mode:
authorPaul Walmsley <[email protected]>2011-03-04 06:02:15 +0000
committerTony Lindgren <[email protected]>2011-03-09 13:03:15 -0800
commitc39bee8ac4aca750c85609ba0847599b36feb693 (patch)
tree45157eb8ecc3eaa781b10fcc3528434d4b71003a /tools/perf/util/trace-event-scripting.c
parent0640b436e410290193f554dcfd777bcdeee59697 (diff)
OMAP2/3: VENC hwmod: add OCPIF_SWSUP_IDLE flag to interface
According to the hwmod interface data, the DSS submodule "VENC" uses a clock, "dss_54m_fck"/"dss_tv_fck", which the PRCM cannot autoidle. By default, the hwmod code assumes that interface clocks can be autoidled by the PRCM. When the interface clock can't be autoidled by the PRCM, those interfaces must be marked with the OCPIF_SWSUP_IDLE flag. Otherwise, the "interface clock" will always have a non-zero use count, and the device won't enter idle. This problem was observed on N8x0. Fix the immediate problem by marking the VENC interface with the OCPIF_SWSUP_IDLE flag. But it's not clear that "dss_54m_fck"/"dss_tv_fck" is really the correct interface clock for VENC. It may be that the VENC interface should use a hardware-autoidling interface clock. This is the situation on OMAP4, which uses "l3_div_ck" as the VENC interface clock, which can be autoidled by the PRCM. Clarification from TI is needed. Problem found and patch tested on N8x0 by Tony Lindgren <[email protected]>. Signed-off-by: Paul Walmsley <[email protected]> Cc: Tony Lindgren <[email protected]> Cc: Senthilvadivu Guruswamy <[email protected]> Cc: Sumit Semwal <[email protected]> Cc: Kevin Hilman <[email protected]> Cc: BenoĆ®t Cousson <[email protected]> Signed-off-by: Tony Lindgren <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions