Jean Pihet <jean.pi...@newoldbits.com> writes: > On Thu, Nov 17, 2011 at 10:29 PM, Kevin Hilman <khil...@ti.com> wrote: >> jean.pi...@newoldbits.com writes: >> >>> From: Jean Pihet <j-pi...@ti.com> >>> >>> The MPU latency figures for cpuidle include the MPU itself and also >>> the peripherals needed for the MPU to execute instructions (e.g. >>> main memory, caches, IRQ controller, MMU etc). On OMAP3 those >>> peripherals belong to the MPU and CORE power domains and so the >>> cpuidle C-states are a combination of MPU and CORE states. >>> >>> This patch implements the relation between the cpuidle and per- >>> device PM QoS frameworks in the OMAP3 specific idle callbacks. >>> >>> The chosen C-state shall satisfy the following conditions: >>> . the 'valid' field is enabled, >>> . it satisfies the enable_off_mode flag, >> >> Not directly related to this patch, but is there any reason to keep the >> 'enable_off_mode' flag after this series? > enable_off_mode could be removed completely after this series unless > there is a need to prevent OFF mode for debug reasons.
Great. For debug reasons, we can just as easily set constraints to prevent off mode, so I would like to see it disappear. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
