ext Rajendra Nayak wrote:
This patch checks for the return values of omap_pm_vddx_get_opp()
in SR driver and acts accordingly. With no SRF layer enabled the OMAP-PM layer
api is unable to return the current OPP.
Signed-off-by: Rajendra Nayak <rna...@ti.com>
---
arch/arm/mach-omap2/smartreflex.c | 42 +++++++++++++++++++++++++++++++++---
1 files changed, 38 insertions(+), 4 deletions(-)
+ if (!omap_pm_vdd1_get_opp())
+ /* Assume Nominal OPP as current OPP unknown */
+ vsel = mpu_opps[VDD1_OPP3].vsel;
+ else
+ vsel = mpu_opps[omap_pm_vdd1_get_opp()].vsel;
+
Hi Rajendra,
By this approach, what will be the implications if the bootloader had set the
OPP to something different than your assumption?
I think the best approach would be to modify the PM layer to at least return
correct OPP and Frequency values. What do you think?
We should not expect every driver using X_get_opp to assume the OPP if it
returns error.
Please see this thread to see the alternative solution.
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg12021.html
I know it uses resource framework even if we set PM_NONE or PM_NOOP, but only
for getting the correct OPP/frequency values.
regards,
-roger
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
