linux-kernel - Re: [PATCH] OMAP4: DMTIMER: enable autoidle mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20110701072610.GD23145@atomide.com>
Date:	Fri, 1 Jul 2011 00:26:10 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	"K, Ambresh" <ambresh@...com>
Cc:	"DebBarma, Tarun Kanti" <tarun.kanti@...com>,
	linux-omap <linux-omap@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] OMAP4: DMTIMER: enable autoidle mode

* K, Ambresh <ambresh@...com> [110615 21:41]:
> On Wed, Jun 15, 2011 at 9:39 PM, DebBarma, Tarun Kanti
> <tarun.kanti@...com>wrote:
> > >
> > > Currently autoidle is only enabled for OMAP2/3; by enabling autoidle,
> > > the automatic L4 clock gating strategy is applied based on L4 activity,
> > > otherwise L4 clock to module will be a free running.

Applying this into devel-fixes.

> > > -     /* Enable autoidle on OMAP2 / OMAP3 */
> > > -     if (cpu_is_omap24xx() || cpu_is_omap34xx())
> > > +     /* Enable autoidle on OMAP2 CPUs. */
> > > +     if (cpu_class_is_omap2())
> > >               l |= 0x1 << 0;
> > BTW, in the hwmod adaptation series this is taken care by the framework.
> >
> 
> Ok!

That should be a trivial update. Let's first merge this fix so L4 can
autoidle on omap4.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/