From mboxrd@z Thu Jan 1 00:00:00 1970 From: nm@ti.com (Nishanth Menon) Date: Thu, 16 Sep 2010 07:40:42 -0500 Subject: [PATCH 1/4] OMAP: introduce OPP layer for device-specific OPPs In-Reply-To: References: <1284587799-9637-1-git-send-email-khilman@deeprootsystems.com> <1284587799-9637-2-git-send-email-khilman@deeprootsystems.com> Message-ID: <4C92104A.5040901@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Linus Walleij had written, on 09/16/2010 07:19 AM, the following: > 2010/9/15 Kevin Hilman : > >> OMAP SOCs have a standard set of tuples consisting of frequency and >> voltage pairs that the device will support per voltage domain. These >> are called Operating Performance Points or OPPs. >> (...) >> This introduces a common handling OPP mechanism accross all OMAPs. >> As a start this is used for OMAP3. > > OPPs are a generic concept, it's in silicon construction textbooks and all. > Should this code not be made generic instead? You wouldn't make > regulators or even DMA platform-specific these days, so why should > OPPs be? As far as I see this patch : hwmod[1] which is omap specific which inturn depends on omap_device. - this impacts opp_add function in the opp layer. [1] http://marc.info/?l=linux-omap&m=128226580816341&w=2 -- Regards, Nishanth Menon