From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@opensource.wolfsonmicro.com (Mark Brown) Date: Tue, 24 Jan 2012 20:17:49 +0000 Subject: [PATCH v3 0/7] Add common cpuidle code for consolidation. In-Reply-To: <871uqoj23b.fsf@ti.com> References: <1327379854-12403-1-git-send-email-rob.lee@linaro.org> <871uqoj23b.fsf@ti.com> Message-ID: <20120124201749.GC1135@opensource.wolfsonmicro.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Jan 24, 2012 at 12:08:08PM -0800, Kevin Hilman wrote: > Robert Lee writes: > > Besides just code consolidation, a > > default "WFI" state is now used with default parameters that different from your > > original paramenters. The assumption is that if you have a WFI only idle state, > > the parameters in the new default WFI are more realistic as a true WFI only > > hardware state incurs minimal latency(<1us) or power penalty to enter and exit. > > If your platform actually performs other platform specific functionality upon > > entering WFI and the default parameters do not accurately reflect the > > exit_latency and target_residency given in the common default state, please > > say so. > I'm not sure what you mean by "WFI only". On OMAP, WFI is the entry > point for all the idle states, with varying latencies. The latencies > are then dependent on how the states are programmed for the various > power domains. Upon WFI, the hardware then takes over puts the > powerdomains to their programmed states. The default state in the patches is set up with parameters for a state that literally only does the WFI and has no other hardware actions taken adding latencies. I asked for this because the existing drivers for most of the SoCs out there currently only support that basic idle state and when doing something more complex (which most of the SoCs actually can do in hardware) it's still likely to get used during bringup of the feature. If there's varying levels of idle state then the SoC specific code would need to enumerate them and their varying latencies so that the core can figure out which one to enter. This isn't a problem, it's a good thing, but most SoCs haven't got so far as to need it yet. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: