linux-kernel - Extending OPP Functionality

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <7fac345a60d692e55a6390bd3557b29d.squirrel@www.codeaurora.org>
Date:	Mon, 5 Dec 2011 17:12:29 -0800 (PST)
From:	khugans@...eaurora.org
To:	nm@...com
Cc:	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
	skannan@...eaurora.org, mattw@...eaurora.org,
	jchokshi@...eaurora.org, sboyd@...eaurora.org
Subject: Extending OPP Functionality

Hi Nishanth Menon,

We have a number of drivers that manage power/performance levels in their
own ways and we are looking for a way to consolidate these similar
implementations in one place.  We want to scale multiple voltage levels,
clocks and bandwidth requests along with each other. For example our L2
depends on two power rail voltages.

Weve observed that OPP tackles this for single voltage-frequency pair,
but doesnt manage additional data that may be associated with
performance/power levels.  Would it make sense to extend OPP to handle
implementation-specific data pointers to handle this generically?

Thanks,
Khugan

--
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/