Hi, On Thu, 18 Oct 2012, Tero Kristo wrote: > From: Rajendra Nayak <rnayak@xxxxxx> > > OMAP4 has module specific context lost registers which makes it now > possible to have module level context loss count, instead of relying > on the powerdomain level context count. > > Add 2 private hwmod api's to update/clear the hwmod/module specific > context lost counters/register. > > Update the module specific context_lost_counter and clear the hardware > bits just after enabling the module. > > omap_hwmod_get_context_loss_count() now returns the hwmod context loss > count them on platforms where they exist (OMAP4), else fall back on > the pwrdm level counters for older platforms. > > Signed-off-by: Rajendra Nayak <rnayak@xxxxxx> > [paul@xxxxxxxxx: added function kerneldoc, fixed structure kerneldoc, > rearranged structure to avoid memory waste, marked fns as OMAP4-specific, > prevent fn entry on non-OMAP4 chips, reduced indentation, merged update > and clear, merged patches] > [t-kristo@xxxxxx: added support for arch specific hwmod ops, and changed > the no context offset indicator to USHRT_MAX] > Signed-off-by: Tero Kristo <t-kristo@xxxxxx> > [paul@xxxxxxxxx: use NO_CONTEXT_LOSS_BIT flag rather than USHRT_MAX; > convert unsigned context lost counter to int to match the return type; > get rid of hwmod_ops in favor of the existing soc_ops mechanism] > Signed-off-by: Paul Walmsley <paul@xxxxxxxxx> Thanks, re-queued for 3.8. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
