2019-06-04 08:11:33 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-only
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/*
|
|
|
|
* Generic OPP Interface
|
|
|
|
*
|
|
|
|
* Copyright (C) 2009-2010 Texas Instruments Incorporated.
|
|
|
|
* Nishanth Menon
|
|
|
|
* Romit Dasgupta
|
|
|
|
* Kevin Hilman
|
|
|
|
*/
|
|
|
|
|
2015-10-17 04:15:18 +00:00
|
|
|
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
|
|
|
|
|
2016-02-09 05:00:38 +00:00
|
|
|
#include <linux/clk.h>
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
#include <linux/errno.h>
|
|
|
|
#include <linux/err.h>
|
2012-01-22 16:23:42 +00:00
|
|
|
#include <linux/device.h>
|
2012-10-22 23:27:44 +00:00
|
|
|
#include <linux/export.h>
|
2017-10-11 07:24:14 +00:00
|
|
|
#include <linux/pm_domain.h>
|
2016-02-09 05:00:33 +00:00
|
|
|
#include <linux/regulator/consumer.h>
|
2022-05-25 09:53:16 +00:00
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/xarray.h>
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2015-09-04 08:17:26 +00:00
|
|
|
#include "opp.h"
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
|
|
|
/*
|
2016-02-16 08:47:53 +00:00
|
|
|
* The root of the list of all opp-tables. All opp_table structures branch off
|
|
|
|
* from here, with each opp_table containing the list of opps it supports in
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* various states of availability.
|
|
|
|
*/
|
2016-05-05 10:50:33 +00:00
|
|
|
LIST_HEAD(opp_tables);
|
2019-11-25 08:27:58 +00:00
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/* Lock to allow exclusive modification to the device and opp lists */
|
2016-02-16 08:47:53 +00:00
|
|
|
DEFINE_MUTEX(opp_table_lock);
|
2020-10-27 11:23:21 +00:00
|
|
|
/* Flag indicating that opp_tables list is being updated at the moment */
|
|
|
|
static bool opp_tables_busy;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2022-05-25 09:53:16 +00:00
|
|
|
/* OPP ID allocator */
|
|
|
|
static DEFINE_XARRAY_ALLOC1(opp_configs);
|
|
|
|
|
2020-10-27 06:19:03 +00:00
|
|
|
static bool _find_opp_dev(const struct device *dev, struct opp_table *opp_table)
|
2015-07-29 10:53:04 +00:00
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_device *opp_dev;
|
2020-10-27 06:19:03 +00:00
|
|
|
bool found = false;
|
2015-07-29 10:53:04 +00:00
|
|
|
|
2020-10-27 06:19:03 +00:00
|
|
|
mutex_lock(&opp_table->lock);
|
2016-02-16 08:47:53 +00:00
|
|
|
list_for_each_entry(opp_dev, &opp_table->dev_list, node)
|
2020-10-27 06:19:03 +00:00
|
|
|
if (opp_dev->dev == dev) {
|
|
|
|
found = true;
|
|
|
|
break;
|
|
|
|
}
|
2015-07-29 10:53:04 +00:00
|
|
|
|
2020-10-27 06:19:03 +00:00
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
return found;
|
2015-07-29 10:53:04 +00:00
|
|
|
}
|
|
|
|
|
2017-02-06 14:29:55 +00:00
|
|
|
static struct opp_table *_find_opp_table_unlocked(struct device *dev)
|
2017-01-23 04:41:48 +00:00
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
|
|
|
|
list_for_each_entry(opp_table, &opp_tables, node) {
|
2020-10-27 06:19:03 +00:00
|
|
|
if (_find_opp_dev(dev, opp_table)) {
|
2017-01-23 04:41:48 +00:00
|
|
|
_get_opp_table_kref(opp_table);
|
|
|
|
return opp_table;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return ERR_PTR(-ENODEV);
|
|
|
|
}
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/**
|
2016-02-16 08:47:53 +00:00
|
|
|
* _find_opp_table() - find opp_table struct using device pointer
|
|
|
|
* @dev: device pointer used to lookup OPP table
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
2017-01-23 04:41:49 +00:00
|
|
|
* Search OPP table for one containing matching device.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
2016-02-16 08:47:53 +00:00
|
|
|
* Return: pointer to 'struct opp_table' if found, otherwise -ENODEV or
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* -EINVAL based on type of error.
|
|
|
|
*
|
2017-01-23 04:41:48 +00:00
|
|
|
* The callers must call dev_pm_opp_put_opp_table() after the table is used.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*/
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *_find_opp_table(struct device *dev)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2015-08-12 10:29:39 +00:00
|
|
|
if (IS_ERR_OR_NULL(dev)) {
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
pr_err("%s: Invalid parameters\n", __func__);
|
|
|
|
return ERR_PTR(-EINVAL);
|
|
|
|
}
|
|
|
|
|
2017-01-23 04:41:48 +00:00
|
|
|
mutex_lock(&opp_table_lock);
|
|
|
|
opp_table = _find_opp_table_unlocked(dev);
|
|
|
|
mutex_unlock(&opp_table_lock);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2017-01-23 04:41:48 +00:00
|
|
|
return opp_table;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
|
|
|
|
2022-06-10 04:57:51 +00:00
|
|
|
/*
|
|
|
|
* Returns true if multiple clocks aren't there, else returns false with WARN.
|
|
|
|
*
|
|
|
|
* We don't force clk_count == 1 here as there are users who don't have a clock
|
|
|
|
* representation in the OPP table and manage the clock configuration themselves
|
|
|
|
* in an platform specific way.
|
|
|
|
*/
|
|
|
|
static bool assert_single_clk(struct opp_table *opp_table)
|
|
|
|
{
|
|
|
|
return !WARN_ON(opp_table->clk_count > 1);
|
|
|
|
}
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/**
|
2015-09-10 17:09:29 +00:00
|
|
|
* dev_pm_opp_get_voltage() - Gets the voltage corresponding to an opp
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* @opp: opp for which voltage has to be returned for
|
|
|
|
*
|
2014-12-24 17:22:57 +00:00
|
|
|
* Return: voltage in micro volt corresponding to the opp, else
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* return 0
|
|
|
|
*
|
2016-12-01 10:58:19 +00:00
|
|
|
* This is useful only for devices with single power supply.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*/
|
2013-09-19 21:03:51 +00:00
|
|
|
unsigned long dev_pm_opp_get_voltage(struct dev_pm_opp *opp)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2017-01-23 04:41:49 +00:00
|
|
|
if (IS_ERR_OR_NULL(opp)) {
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
pr_err("%s: Invalid parameters\n", __func__);
|
2017-01-23 04:41:49 +00:00
|
|
|
return 0;
|
|
|
|
}
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
return opp->supplies[0].u_volt;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
2013-09-19 21:03:50 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_voltage);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2022-05-31 07:54:21 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_get_supplies() - Gets the supply information corresponding to an opp
|
|
|
|
* @opp: opp for which voltage has to be returned for
|
|
|
|
* @supplies: Placeholder for copying the supply information.
|
|
|
|
*
|
|
|
|
* Return: negative error number on failure, 0 otherwise on success after
|
|
|
|
* setting @supplies.
|
|
|
|
*
|
|
|
|
* This can be used for devices with any number of power supplies. The caller
|
|
|
|
* must ensure the @supplies array must contain space for each regulator.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_get_supplies(struct dev_pm_opp *opp,
|
|
|
|
struct dev_pm_opp_supply *supplies)
|
|
|
|
{
|
|
|
|
if (IS_ERR_OR_NULL(opp) || !supplies) {
|
|
|
|
pr_err("%s: Invalid parameters\n", __func__);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
memcpy(supplies, opp->supplies,
|
|
|
|
sizeof(*supplies) * opp->opp_table->regulator_count);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_supplies);
|
|
|
|
|
2022-03-02 11:29:14 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_get_power() - Gets the power corresponding to an opp
|
|
|
|
* @opp: opp for which power has to be returned for
|
|
|
|
*
|
|
|
|
* Return: power in micro watt corresponding to the opp, else
|
|
|
|
* return 0
|
|
|
|
*
|
|
|
|
* This is useful only for devices with single power supply.
|
|
|
|
*/
|
|
|
|
unsigned long dev_pm_opp_get_power(struct dev_pm_opp *opp)
|
|
|
|
{
|
|
|
|
unsigned long opp_power = 0;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
if (IS_ERR_OR_NULL(opp)) {
|
|
|
|
pr_err("%s: Invalid parameters\n", __func__);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
for (i = 0; i < opp->opp_table->regulator_count; i++)
|
|
|
|
opp_power += opp->supplies[i].u_watt;
|
|
|
|
|
|
|
|
return opp_power;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_power);
|
|
|
|
|
2023-07-20 05:40:53 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_get_freq_indexed() - Gets the frequency corresponding to an
|
|
|
|
* available opp with specified index
|
|
|
|
* @opp: opp for which frequency has to be returned for
|
|
|
|
* @index: index of the frequency within the required opp
|
|
|
|
*
|
|
|
|
* Return: frequency in hertz corresponding to the opp with specified index,
|
|
|
|
* else return 0
|
|
|
|
*/
|
|
|
|
unsigned long dev_pm_opp_get_freq_indexed(struct dev_pm_opp *opp, u32 index)
|
|
|
|
{
|
|
|
|
if (IS_ERR_OR_NULL(opp) || index >= opp->opp_table->clk_count) {
|
|
|
|
pr_err("%s: Invalid parameters\n", __func__);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return opp->rates[index];
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_freq_indexed);
|
|
|
|
|
2019-01-10 04:02:02 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_get_level() - Gets the level corresponding to an available opp
|
|
|
|
* @opp: opp for which level value has to be returned for
|
|
|
|
*
|
|
|
|
* Return: level read from device tree corresponding to the opp, else
|
|
|
|
* return 0.
|
|
|
|
*/
|
|
|
|
unsigned int dev_pm_opp_get_level(struct dev_pm_opp *opp)
|
|
|
|
{
|
|
|
|
if (IS_ERR_OR_NULL(opp) || !opp->available) {
|
|
|
|
pr_err("%s: Invalid parameters\n", __func__);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return opp->level;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_level);
|
|
|
|
|
2021-01-18 00:55:19 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_get_required_pstate() - Gets the required performance state
|
|
|
|
* corresponding to an available opp
|
|
|
|
* @opp: opp for which performance state has to be returned for
|
|
|
|
* @index: index of the required opp
|
|
|
|
*
|
|
|
|
* Return: performance state read from device tree corresponding to the
|
|
|
|
* required opp, else return 0.
|
|
|
|
*/
|
|
|
|
unsigned int dev_pm_opp_get_required_pstate(struct dev_pm_opp *opp,
|
|
|
|
unsigned int index)
|
|
|
|
{
|
|
|
|
if (IS_ERR_OR_NULL(opp) || !opp->available ||
|
2023-07-21 12:46:33 +00:00
|
|
|
index >= opp->opp_table->required_opp_count) {
|
2021-01-18 00:55:19 +00:00
|
|
|
pr_err("%s: Invalid parameters\n", __func__);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2019-11-25 08:27:58 +00:00
|
|
|
/* required-opps not fully initialized yet */
|
2023-07-21 12:46:33 +00:00
|
|
|
if (lazy_linking_pending(opp->opp_table))
|
2019-11-25 08:27:58 +00:00
|
|
|
return 0;
|
|
|
|
|
2023-06-14 10:27:43 +00:00
|
|
|
/* The required OPP table must belong to a genpd */
|
2023-07-21 12:46:33 +00:00
|
|
|
if (unlikely(!opp->opp_table->required_opp_tables[index]->is_genpd)) {
|
2023-06-14 10:27:43 +00:00
|
|
|
pr_err("%s: Performance state is only valid for genpds.\n", __func__);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2023-06-14 09:59:32 +00:00
|
|
|
return opp->required_opps[index]->level;
|
2021-01-18 00:55:19 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_required_pstate);
|
|
|
|
|
2015-07-09 15:43:35 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_is_turbo() - Returns if opp is turbo OPP or not
|
|
|
|
* @opp: opp for which turbo mode is being verified
|
|
|
|
*
|
|
|
|
* Turbo OPPs are not for normal use, and can be enabled (under certain
|
|
|
|
* conditions) for short duration of times to finish high throughput work
|
|
|
|
* quickly. Running on them for longer times may overheat the chip.
|
|
|
|
*
|
|
|
|
* Return: true if opp is turbo opp, else false.
|
|
|
|
*/
|
|
|
|
bool dev_pm_opp_is_turbo(struct dev_pm_opp *opp)
|
|
|
|
{
|
2017-01-23 04:41:49 +00:00
|
|
|
if (IS_ERR_OR_NULL(opp) || !opp->available) {
|
2015-07-09 15:43:35 +00:00
|
|
|
pr_err("%s: Invalid parameters\n", __func__);
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
return opp->turbo;
|
2015-07-09 15:43:35 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_is_turbo);
|
|
|
|
|
2015-07-29 10:53:03 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_get_max_clock_latency() - Get max clock latency in nanoseconds
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
*
|
|
|
|
* Return: This function returns the max clock latency in nanoseconds.
|
|
|
|
*/
|
|
|
|
unsigned long dev_pm_opp_get_max_clock_latency(struct device *dev)
|
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table;
|
2015-07-29 10:53:03 +00:00
|
|
|
unsigned long clock_latency_ns;
|
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table))
|
2017-01-23 04:41:48 +00:00
|
|
|
return 0;
|
|
|
|
|
|
|
|
clock_latency_ns = opp_table->clock_latency_ns_max;
|
|
|
|
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2015-07-29 10:53:03 +00:00
|
|
|
|
|
|
|
return clock_latency_ns;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_max_clock_latency);
|
|
|
|
|
2016-02-09 05:00:35 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_get_max_volt_latency() - Get max voltage latency in nanoseconds
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
*
|
|
|
|
* Return: This function returns the max voltage latency in nanoseconds.
|
|
|
|
*/
|
|
|
|
unsigned long dev_pm_opp_get_max_volt_latency(struct device *dev)
|
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table;
|
2016-02-09 05:00:35 +00:00
|
|
|
struct dev_pm_opp *opp;
|
2017-05-23 04:02:11 +00:00
|
|
|
struct regulator *reg;
|
2016-02-09 05:00:35 +00:00
|
|
|
unsigned long latency_ns = 0;
|
2016-12-01 10:58:19 +00:00
|
|
|
int ret, i, count;
|
|
|
|
struct {
|
|
|
|
unsigned long min;
|
|
|
|
unsigned long max;
|
|
|
|
} *uV;
|
|
|
|
|
2017-01-23 04:41:51 +00:00
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table))
|
|
|
|
return 0;
|
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
/* Regulator may not be required for the device */
|
2018-12-11 11:02:47 +00:00
|
|
|
if (!opp_table->regulators)
|
2017-01-23 04:41:51 +00:00
|
|
|
goto put_opp_table;
|
2016-12-01 10:58:19 +00:00
|
|
|
|
2018-12-11 11:02:47 +00:00
|
|
|
count = opp_table->regulator_count;
|
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
uV = kmalloc_array(count, sizeof(*uV), GFP_KERNEL);
|
|
|
|
if (!uV)
|
2017-05-23 04:02:11 +00:00
|
|
|
goto put_opp_table;
|
2016-02-09 05:00:35 +00:00
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
for (i = 0; i < count; i++) {
|
|
|
|
uV[i].min = ~0;
|
|
|
|
uV[i].max = 0;
|
2016-02-09 05:00:35 +00:00
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
list_for_each_entry(opp, &opp_table->opp_list, node) {
|
2016-12-01 10:58:19 +00:00
|
|
|
if (!opp->available)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
if (opp->supplies[i].u_volt_min < uV[i].min)
|
|
|
|
uV[i].min = opp->supplies[i].u_volt_min;
|
|
|
|
if (opp->supplies[i].u_volt_max > uV[i].max)
|
|
|
|
uV[i].max = opp->supplies[i].u_volt_max;
|
|
|
|
}
|
2016-02-09 05:00:35 +00:00
|
|
|
}
|
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
mutex_unlock(&opp_table->lock);
|
2016-02-09 05:00:35 +00:00
|
|
|
|
|
|
|
/*
|
2016-02-16 08:47:53 +00:00
|
|
|
* The caller needs to ensure that opp_table (and hence the regulator)
|
2016-02-09 05:00:35 +00:00
|
|
|
* isn't freed, while we are executing this routine.
|
|
|
|
*/
|
2017-02-20 18:57:57 +00:00
|
|
|
for (i = 0; i < count; i++) {
|
2017-05-23 04:02:11 +00:00
|
|
|
reg = opp_table->regulators[i];
|
2016-12-01 10:58:19 +00:00
|
|
|
ret = regulator_set_voltage_time(reg, uV[i].min, uV[i].max);
|
|
|
|
if (ret > 0)
|
|
|
|
latency_ns += ret * 1000;
|
|
|
|
}
|
|
|
|
|
|
|
|
kfree(uV);
|
2017-01-23 04:41:51 +00:00
|
|
|
put_opp_table:
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2016-02-09 05:00:35 +00:00
|
|
|
|
|
|
|
return latency_ns;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_max_volt_latency);
|
|
|
|
|
2016-02-09 05:00:36 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_get_max_transition_latency() - Get max transition latency in
|
|
|
|
* nanoseconds
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
*
|
|
|
|
* Return: This function returns the max transition latency, in nanoseconds, to
|
|
|
|
* switch from one OPP to other.
|
|
|
|
*/
|
|
|
|
unsigned long dev_pm_opp_get_max_transition_latency(struct device *dev)
|
|
|
|
{
|
|
|
|
return dev_pm_opp_get_max_volt_latency(dev) +
|
|
|
|
dev_pm_opp_get_max_clock_latency(dev);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_max_transition_latency);
|
|
|
|
|
2015-09-08 16:41:01 +00:00
|
|
|
/**
|
2017-01-02 09:11:02 +00:00
|
|
|
* dev_pm_opp_get_suspend_opp_freq() - Get frequency of suspend opp in Hz
|
2015-09-08 16:41:01 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
*
|
2017-01-02 09:11:02 +00:00
|
|
|
* Return: This function returns the frequency of the OPP marked as suspend_opp
|
|
|
|
* if one is available, else returns 0;
|
2015-09-08 16:41:01 +00:00
|
|
|
*/
|
2017-01-02 09:11:02 +00:00
|
|
|
unsigned long dev_pm_opp_get_suspend_opp_freq(struct device *dev)
|
2015-09-08 16:41:01 +00:00
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table;
|
2017-01-02 09:11:02 +00:00
|
|
|
unsigned long freq = 0;
|
2015-09-08 16:41:01 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_table = _find_opp_table(dev);
|
2017-01-23 04:41:48 +00:00
|
|
|
if (IS_ERR(opp_table))
|
|
|
|
return 0;
|
2017-01-02 09:11:02 +00:00
|
|
|
|
2017-01-23 04:41:48 +00:00
|
|
|
if (opp_table->suspend_opp && opp_table->suspend_opp->available)
|
|
|
|
freq = dev_pm_opp_get_freq(opp_table->suspend_opp);
|
|
|
|
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2015-09-08 16:41:01 +00:00
|
|
|
|
2017-01-02 09:11:02 +00:00
|
|
|
return freq;
|
2015-09-08 16:41:01 +00:00
|
|
|
}
|
2017-01-02 09:11:02 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_suspend_opp_freq);
|
2015-09-08 16:41:01 +00:00
|
|
|
|
2018-04-06 09:05:45 +00:00
|
|
|
int _get_opp_count(struct opp_table *opp_table)
|
|
|
|
{
|
|
|
|
struct dev_pm_opp *opp;
|
|
|
|
int count = 0;
|
|
|
|
|
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
|
|
|
|
list_for_each_entry(opp, &opp_table->opp_list, node) {
|
|
|
|
if (opp->available)
|
|
|
|
count++;
|
|
|
|
}
|
|
|
|
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/**
|
2016-02-16 08:47:53 +00:00
|
|
|
* dev_pm_opp_get_opp_count() - Get number of opps available in the opp table
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
*
|
2014-12-24 17:22:57 +00:00
|
|
|
* Return: This function returns the number of available opps if there are any,
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* else returns 0 if none or the corresponding error value.
|
|
|
|
*/
|
2013-09-19 21:03:50 +00:00
|
|
|
int dev_pm_opp_get_opp_count(struct device *dev)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table;
|
2018-04-06 09:05:45 +00:00
|
|
|
int count;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table)) {
|
|
|
|
count = PTR_ERR(opp_table);
|
2017-09-29 17:39:49 +00:00
|
|
|
dev_dbg(dev, "%s: OPP table not found (%d)\n",
|
2014-12-16 23:09:38 +00:00
|
|
|
__func__, count);
|
2018-10-03 09:52:03 +00:00
|
|
|
return count;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
|
|
|
|
2018-04-06 09:05:45 +00:00
|
|
|
count = _get_opp_count(opp_table);
|
2017-01-23 04:41:48 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
return count;
|
|
|
|
}
|
2013-09-19 21:03:50 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_opp_count);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2022-06-02 07:33:05 +00:00
|
|
|
/* Helpers to read keys */
|
|
|
|
static unsigned long _read_freq(struct dev_pm_opp *opp, int index)
|
|
|
|
{
|
2023-07-21 09:05:08 +00:00
|
|
|
return opp->rates[index];
|
2022-06-02 07:33:05 +00:00
|
|
|
}
|
|
|
|
|
2022-06-02 07:35:45 +00:00
|
|
|
static unsigned long _read_level(struct dev_pm_opp *opp, int index)
|
|
|
|
{
|
|
|
|
return opp->level;
|
|
|
|
}
|
|
|
|
|
2022-06-02 07:35:45 +00:00
|
|
|
static unsigned long _read_bw(struct dev_pm_opp *opp, int index)
|
|
|
|
{
|
|
|
|
return opp->bandwidth[index].peak;
|
|
|
|
}
|
|
|
|
|
2022-06-02 07:33:05 +00:00
|
|
|
/* Generic comparison helpers */
|
|
|
|
static bool _compare_exact(struct dev_pm_opp **opp, struct dev_pm_opp *temp_opp,
|
|
|
|
unsigned long opp_key, unsigned long key)
|
|
|
|
{
|
|
|
|
if (opp_key == key) {
|
|
|
|
*opp = temp_opp;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool _compare_ceil(struct dev_pm_opp **opp, struct dev_pm_opp *temp_opp,
|
|
|
|
unsigned long opp_key, unsigned long key)
|
|
|
|
{
|
|
|
|
if (opp_key >= key) {
|
|
|
|
*opp = temp_opp;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool _compare_floor(struct dev_pm_opp **opp, struct dev_pm_opp *temp_opp,
|
|
|
|
unsigned long opp_key, unsigned long key)
|
|
|
|
{
|
|
|
|
if (opp_key > key)
|
|
|
|
return true;
|
|
|
|
|
|
|
|
*opp = temp_opp;
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Generic key finding helpers */
|
|
|
|
static struct dev_pm_opp *_opp_table_find_key(struct opp_table *opp_table,
|
|
|
|
unsigned long *key, int index, bool available,
|
|
|
|
unsigned long (*read)(struct dev_pm_opp *opp, int index),
|
|
|
|
bool (*compare)(struct dev_pm_opp **opp, struct dev_pm_opp *temp_opp,
|
2022-06-10 04:10:30 +00:00
|
|
|
unsigned long opp_key, unsigned long key),
|
|
|
|
bool (*assert)(struct opp_table *opp_table))
|
2022-06-02 07:33:05 +00:00
|
|
|
{
|
|
|
|
struct dev_pm_opp *temp_opp, *opp = ERR_PTR(-ERANGE);
|
|
|
|
|
2022-06-10 04:10:30 +00:00
|
|
|
/* Assert that the requirement is met */
|
|
|
|
if (assert && !assert(opp_table))
|
|
|
|
return ERR_PTR(-EINVAL);
|
|
|
|
|
2022-06-02 07:33:05 +00:00
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
|
|
|
|
list_for_each_entry(temp_opp, &opp_table->opp_list, node) {
|
|
|
|
if (temp_opp->available == available) {
|
|
|
|
if (compare(&opp, temp_opp, read(temp_opp, index), *key))
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Increment the reference count of OPP */
|
|
|
|
if (!IS_ERR(opp)) {
|
|
|
|
*key = read(opp, index);
|
|
|
|
dev_pm_opp_get(opp);
|
|
|
|
}
|
|
|
|
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
|
|
|
|
return opp;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct dev_pm_opp *
|
|
|
|
_find_key(struct device *dev, unsigned long *key, int index, bool available,
|
|
|
|
unsigned long (*read)(struct dev_pm_opp *opp, int index),
|
|
|
|
bool (*compare)(struct dev_pm_opp **opp, struct dev_pm_opp *temp_opp,
|
2022-06-10 04:10:30 +00:00
|
|
|
unsigned long opp_key, unsigned long key),
|
|
|
|
bool (*assert)(struct opp_table *opp_table))
|
2022-06-02 07:33:05 +00:00
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
struct dev_pm_opp *opp;
|
|
|
|
|
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table)) {
|
|
|
|
dev_err(dev, "%s: OPP table not found (%ld)\n", __func__,
|
|
|
|
PTR_ERR(opp_table));
|
|
|
|
return ERR_CAST(opp_table);
|
|
|
|
}
|
|
|
|
|
|
|
|
opp = _opp_table_find_key(opp_table, key, index, available, read,
|
2022-06-10 04:10:30 +00:00
|
|
|
compare, assert);
|
2022-06-02 07:33:05 +00:00
|
|
|
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
|
|
|
|
|
|
|
return opp;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct dev_pm_opp *_find_key_exact(struct device *dev,
|
|
|
|
unsigned long key, int index, bool available,
|
2022-06-10 04:10:30 +00:00
|
|
|
unsigned long (*read)(struct dev_pm_opp *opp, int index),
|
|
|
|
bool (*assert)(struct opp_table *opp_table))
|
2022-06-02 07:33:05 +00:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
* The value of key will be updated here, but will be ignored as the
|
|
|
|
* caller doesn't need it.
|
|
|
|
*/
|
2022-06-10 04:10:30 +00:00
|
|
|
return _find_key(dev, &key, index, available, read, _compare_exact,
|
|
|
|
assert);
|
2022-06-02 07:33:05 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static struct dev_pm_opp *_opp_table_find_key_ceil(struct opp_table *opp_table,
|
|
|
|
unsigned long *key, int index, bool available,
|
2022-06-10 04:10:30 +00:00
|
|
|
unsigned long (*read)(struct dev_pm_opp *opp, int index),
|
|
|
|
bool (*assert)(struct opp_table *opp_table))
|
2022-06-02 07:33:05 +00:00
|
|
|
{
|
|
|
|
return _opp_table_find_key(opp_table, key, index, available, read,
|
2022-06-10 04:10:30 +00:00
|
|
|
_compare_ceil, assert);
|
2022-06-02 07:33:05 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static struct dev_pm_opp *_find_key_ceil(struct device *dev, unsigned long *key,
|
|
|
|
int index, bool available,
|
2022-06-10 04:10:30 +00:00
|
|
|
unsigned long (*read)(struct dev_pm_opp *opp, int index),
|
|
|
|
bool (*assert)(struct opp_table *opp_table))
|
2022-06-02 07:33:05 +00:00
|
|
|
{
|
2022-06-10 04:10:30 +00:00
|
|
|
return _find_key(dev, key, index, available, read, _compare_ceil,
|
|
|
|
assert);
|
2022-06-02 07:33:05 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static struct dev_pm_opp *_find_key_floor(struct device *dev,
|
|
|
|
unsigned long *key, int index, bool available,
|
2022-06-10 04:10:30 +00:00
|
|
|
unsigned long (*read)(struct dev_pm_opp *opp, int index),
|
|
|
|
bool (*assert)(struct opp_table *opp_table))
|
2022-06-02 07:33:05 +00:00
|
|
|
{
|
2022-06-10 04:10:30 +00:00
|
|
|
return _find_key(dev, key, index, available, read, _compare_floor,
|
|
|
|
assert);
|
2022-06-02 07:33:05 +00:00
|
|
|
}
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/**
|
2013-09-19 21:03:50 +00:00
|
|
|
* dev_pm_opp_find_freq_exact() - search for an exact frequency
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @freq: frequency to search for
|
2011-02-25 22:46:18 +00:00
|
|
|
* @available: true/false - match for available opp
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
2016-02-16 08:47:53 +00:00
|
|
|
* Return: Searches for exact match in the opp table and returns pointer to the
|
2014-12-24 17:22:57 +00:00
|
|
|
* matching opp if found, else returns ERR_PTR in case of error and should
|
|
|
|
* be handled using IS_ERR. Error return values can be:
|
2012-10-24 20:00:12 +00:00
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
|
|
|
* Note: available is a modifier for the search. if available=true, then the
|
|
|
|
* match is for exact matching frequency and is available in the stored OPP
|
|
|
|
* table. if false, the match is for exact frequency which is not available.
|
|
|
|
*
|
|
|
|
* This provides a mechanism to enable an opp which is not available currently
|
|
|
|
* or the opposite as well.
|
|
|
|
*
|
2017-01-23 04:41:47 +00:00
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*/
|
2013-09-19 21:03:51 +00:00
|
|
|
struct dev_pm_opp *dev_pm_opp_find_freq_exact(struct device *dev,
|
2022-06-02 07:33:05 +00:00
|
|
|
unsigned long freq, bool available)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2022-06-10 04:57:51 +00:00
|
|
|
return _find_key_exact(dev, freq, 0, available, _read_freq,
|
|
|
|
assert_single_clk);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
2013-09-19 21:03:50 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_freq_exact);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2023-07-21 08:11:20 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_find_freq_exact_indexed() - Search for an exact freq for the
|
|
|
|
* clock corresponding to the index
|
|
|
|
* @dev: Device for which we do this operation
|
|
|
|
* @freq: frequency to search for
|
|
|
|
* @index: Clock index
|
|
|
|
* @available: true/false - match for available opp
|
|
|
|
*
|
|
|
|
* Search for the matching exact OPP for the clock corresponding to the
|
|
|
|
* specified index from a starting freq for a device.
|
|
|
|
*
|
|
|
|
* Return: matching *opp , else returns ERR_PTR in case of error and should be
|
|
|
|
* handled using IS_ERR. Error return values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*/
|
|
|
|
struct dev_pm_opp *
|
|
|
|
dev_pm_opp_find_freq_exact_indexed(struct device *dev, unsigned long freq,
|
|
|
|
u32 index, bool available)
|
|
|
|
{
|
|
|
|
return _find_key_exact(dev, freq, index, available, _read_freq, NULL);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_freq_exact_indexed);
|
|
|
|
|
2016-07-25 06:11:16 +00:00
|
|
|
static noinline struct dev_pm_opp *_find_freq_ceil(struct opp_table *opp_table,
|
|
|
|
unsigned long *freq)
|
|
|
|
{
|
2022-06-10 04:10:30 +00:00
|
|
|
return _opp_table_find_key_ceil(opp_table, freq, 0, true, _read_freq,
|
2022-06-10 04:57:51 +00:00
|
|
|
assert_single_clk);
|
2016-07-25 06:11:16 +00:00
|
|
|
}
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/**
|
2013-09-19 21:03:50 +00:00
|
|
|
* dev_pm_opp_find_freq_ceil() - Search for an rounded ceil freq
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @freq: Start frequency
|
|
|
|
*
|
|
|
|
* Search for the matching ceil *available* OPP from a starting freq
|
|
|
|
* for a device.
|
|
|
|
*
|
2014-12-24 17:22:57 +00:00
|
|
|
* Return: matching *opp and refreshes *freq accordingly, else returns
|
2012-10-24 20:00:12 +00:00
|
|
|
* ERR_PTR in case of error and should be handled using IS_ERR. Error return
|
|
|
|
* values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
2017-01-23 04:41:47 +00:00
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*/
|
2013-09-19 21:03:51 +00:00
|
|
|
struct dev_pm_opp *dev_pm_opp_find_freq_ceil(struct device *dev,
|
|
|
|
unsigned long *freq)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2022-06-10 04:57:51 +00:00
|
|
|
return _find_key_ceil(dev, freq, 0, true, _read_freq, assert_single_clk);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
2013-09-19 21:03:50 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_freq_ceil);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2023-07-20 05:40:52 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_find_freq_ceil_indexed() - Search for a rounded ceil freq for the
|
|
|
|
* clock corresponding to the index
|
|
|
|
* @dev: Device for which we do this operation
|
|
|
|
* @freq: Start frequency
|
|
|
|
* @index: Clock index
|
|
|
|
*
|
|
|
|
* Search for the matching ceil *available* OPP for the clock corresponding to
|
|
|
|
* the specified index from a starting freq for a device.
|
|
|
|
*
|
|
|
|
* Return: matching *opp and refreshes *freq accordingly, else returns
|
|
|
|
* ERR_PTR in case of error and should be handled using IS_ERR. Error return
|
|
|
|
* values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*/
|
|
|
|
struct dev_pm_opp *
|
|
|
|
dev_pm_opp_find_freq_ceil_indexed(struct device *dev, unsigned long *freq,
|
|
|
|
u32 index)
|
|
|
|
{
|
|
|
|
return _find_key_ceil(dev, freq, index, true, _read_freq, NULL);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_freq_ceil_indexed);
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/**
|
2013-09-19 21:03:50 +00:00
|
|
|
* dev_pm_opp_find_freq_floor() - Search for a rounded floor freq
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @freq: Start frequency
|
|
|
|
*
|
|
|
|
* Search for the matching floor *available* OPP from a starting freq
|
|
|
|
* for a device.
|
|
|
|
*
|
2014-12-24 17:22:57 +00:00
|
|
|
* Return: matching *opp and refreshes *freq accordingly, else returns
|
2012-10-24 20:00:12 +00:00
|
|
|
* ERR_PTR in case of error and should be handled using IS_ERR. Error return
|
|
|
|
* values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
2017-01-23 04:41:47 +00:00
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*/
|
2013-09-19 21:03:51 +00:00
|
|
|
struct dev_pm_opp *dev_pm_opp_find_freq_floor(struct device *dev,
|
|
|
|
unsigned long *freq)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2022-06-10 04:57:51 +00:00
|
|
|
return _find_key_floor(dev, freq, 0, true, _read_freq, assert_single_clk);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
2013-09-19 21:03:50 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_freq_floor);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2023-07-20 05:40:52 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_find_freq_floor_indexed() - Search for a rounded floor freq for the
|
|
|
|
* clock corresponding to the index
|
|
|
|
* @dev: Device for which we do this operation
|
|
|
|
* @freq: Start frequency
|
|
|
|
* @index: Clock index
|
|
|
|
*
|
|
|
|
* Search for the matching floor *available* OPP for the clock corresponding to
|
|
|
|
* the specified index from a starting freq for a device.
|
|
|
|
*
|
|
|
|
* Return: matching *opp and refreshes *freq accordingly, else returns
|
|
|
|
* ERR_PTR in case of error and should be handled using IS_ERR. Error return
|
|
|
|
* values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*/
|
|
|
|
struct dev_pm_opp *
|
|
|
|
dev_pm_opp_find_freq_floor_indexed(struct device *dev, unsigned long *freq,
|
|
|
|
u32 index)
|
|
|
|
{
|
|
|
|
return _find_key_floor(dev, freq, index, true, _read_freq, NULL);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_freq_floor_indexed);
|
|
|
|
|
2022-05-04 10:10:22 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_find_level_exact() - search for an exact level
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @level: level to search for
|
|
|
|
*
|
|
|
|
* Return: Searches for exact match in the opp table and returns pointer to the
|
|
|
|
* matching opp if found, else returns ERR_PTR in case of error and should
|
|
|
|
* be handled using IS_ERR. Error return values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*/
|
|
|
|
struct dev_pm_opp *dev_pm_opp_find_level_exact(struct device *dev,
|
|
|
|
unsigned int level)
|
|
|
|
{
|
2022-06-10 04:10:30 +00:00
|
|
|
return _find_key_exact(dev, level, 0, true, _read_level, NULL);
|
2022-05-04 10:10:22 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_level_exact);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dev_pm_opp_find_level_ceil() - search for an rounded up level
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @level: level to search for
|
|
|
|
*
|
|
|
|
* Return: Searches for rounded up match in the opp table and returns pointer
|
|
|
|
* to the matching opp if found, else returns ERR_PTR in case of error and
|
|
|
|
* should be handled using IS_ERR. Error return values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*/
|
|
|
|
struct dev_pm_opp *dev_pm_opp_find_level_ceil(struct device *dev,
|
|
|
|
unsigned int *level)
|
|
|
|
{
|
2022-06-02 07:35:45 +00:00
|
|
|
unsigned long temp = *level;
|
|
|
|
struct dev_pm_opp *opp;
|
2022-05-04 10:10:22 +00:00
|
|
|
|
2022-06-10 04:10:30 +00:00
|
|
|
opp = _find_key_ceil(dev, &temp, 0, true, _read_level, NULL);
|
2022-06-02 07:35:45 +00:00
|
|
|
*level = temp;
|
2022-05-04 10:10:22 +00:00
|
|
|
return opp;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_level_ceil);
|
|
|
|
|
2023-09-07 06:00:31 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_find_level_floor() - Search for a rounded floor level
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @level: Start level
|
|
|
|
*
|
|
|
|
* Search for the matching floor *available* OPP from a starting level
|
|
|
|
* for a device.
|
|
|
|
*
|
|
|
|
* Return: matching *opp and refreshes *level accordingly, else returns
|
|
|
|
* ERR_PTR in case of error and should be handled using IS_ERR. Error return
|
|
|
|
* values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*/
|
|
|
|
struct dev_pm_opp *dev_pm_opp_find_level_floor(struct device *dev,
|
|
|
|
unsigned long *level)
|
|
|
|
{
|
|
|
|
return _find_key_floor(dev, level, 0, true, _read_level, NULL);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_level_floor);
|
|
|
|
|
2022-05-04 08:17:32 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_find_bw_ceil() - Search for a rounded ceil bandwidth
|
|
|
|
* @dev: device for which we do this operation
|
2022-05-26 13:20:35 +00:00
|
|
|
* @bw: start bandwidth
|
2022-05-04 08:17:32 +00:00
|
|
|
* @index: which bandwidth to compare, in case of OPPs with several values
|
|
|
|
*
|
|
|
|
* Search for the matching floor *available* OPP from a starting bandwidth
|
|
|
|
* for a device.
|
|
|
|
*
|
|
|
|
* Return: matching *opp and refreshes *bw accordingly, else returns
|
|
|
|
* ERR_PTR in case of error and should be handled using IS_ERR. Error return
|
|
|
|
* values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*/
|
2022-06-02 07:35:45 +00:00
|
|
|
struct dev_pm_opp *dev_pm_opp_find_bw_ceil(struct device *dev, unsigned int *bw,
|
|
|
|
int index)
|
2022-05-04 08:17:32 +00:00
|
|
|
{
|
2022-06-02 07:35:45 +00:00
|
|
|
unsigned long temp = *bw;
|
|
|
|
struct dev_pm_opp *opp;
|
2022-05-04 08:17:32 +00:00
|
|
|
|
2022-06-10 04:10:30 +00:00
|
|
|
opp = _find_key_ceil(dev, &temp, index, true, _read_bw, NULL);
|
2022-06-02 07:35:45 +00:00
|
|
|
*bw = temp;
|
2022-05-04 08:17:32 +00:00
|
|
|
return opp;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_bw_ceil);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dev_pm_opp_find_bw_floor() - Search for a rounded floor bandwidth
|
|
|
|
* @dev: device for which we do this operation
|
2022-05-26 13:20:35 +00:00
|
|
|
* @bw: start bandwidth
|
2022-05-04 08:17:32 +00:00
|
|
|
* @index: which bandwidth to compare, in case of OPPs with several values
|
|
|
|
*
|
|
|
|
* Search for the matching floor *available* OPP from a starting bandwidth
|
|
|
|
* for a device.
|
|
|
|
*
|
|
|
|
* Return: matching *opp and refreshes *bw accordingly, else returns
|
|
|
|
* ERR_PTR in case of error and should be handled using IS_ERR. Error return
|
|
|
|
* values can be:
|
|
|
|
* EINVAL: for bad pointer
|
|
|
|
* ERANGE: no match found for search
|
|
|
|
* ENODEV: if device not found in list of registered devices
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*/
|
|
|
|
struct dev_pm_opp *dev_pm_opp_find_bw_floor(struct device *dev,
|
|
|
|
unsigned int *bw, int index)
|
|
|
|
{
|
2022-06-02 07:35:45 +00:00
|
|
|
unsigned long temp = *bw;
|
|
|
|
struct dev_pm_opp *opp;
|
2022-05-04 08:17:32 +00:00
|
|
|
|
2022-06-10 04:10:30 +00:00
|
|
|
opp = _find_key_floor(dev, &temp, index, true, _read_bw, NULL);
|
2022-06-02 07:35:45 +00:00
|
|
|
*bw = temp;
|
2022-05-04 08:17:32 +00:00
|
|
|
return opp;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_find_bw_floor);
|
|
|
|
|
2016-02-09 05:00:39 +00:00
|
|
|
static int _set_opp_voltage(struct device *dev, struct regulator *reg,
|
2016-12-01 10:58:18 +00:00
|
|
|
struct dev_pm_opp_supply *supply)
|
2016-02-09 05:00:39 +00:00
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
/* Regulator not available for device */
|
|
|
|
if (IS_ERR(reg)) {
|
|
|
|
dev_dbg(dev, "%s: regulator not available: %ld\n", __func__,
|
|
|
|
PTR_ERR(reg));
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2016-12-01 10:58:18 +00:00
|
|
|
dev_dbg(dev, "%s: voltages (mV): %lu %lu %lu\n", __func__,
|
|
|
|
supply->u_volt_min, supply->u_volt, supply->u_volt_max);
|
2016-02-09 05:00:39 +00:00
|
|
|
|
2016-12-01 10:58:18 +00:00
|
|
|
ret = regulator_set_voltage_triplet(reg, supply->u_volt_min,
|
|
|
|
supply->u_volt, supply->u_volt_max);
|
2016-02-09 05:00:39 +00:00
|
|
|
if (ret)
|
|
|
|
dev_err(dev, "%s: failed to set voltage (%lu %lu %lu mV): %d\n",
|
2016-12-01 10:58:18 +00:00
|
|
|
__func__, supply->u_volt_min, supply->u_volt,
|
|
|
|
supply->u_volt_max, ret);
|
2016-02-09 05:00:39 +00:00
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
static int
|
|
|
|
_opp_config_clk_single(struct device *dev, struct opp_table *opp_table,
|
|
|
|
struct dev_pm_opp *opp, void *data, bool scaling_down)
|
2016-12-01 10:58:20 +00:00
|
|
|
{
|
2022-06-03 09:31:30 +00:00
|
|
|
unsigned long *target = data;
|
|
|
|
unsigned long freq;
|
2016-12-01 10:58:20 +00:00
|
|
|
int ret;
|
|
|
|
|
2022-06-03 09:31:30 +00:00
|
|
|
/* One of target and opp must be available */
|
|
|
|
if (target) {
|
|
|
|
freq = *target;
|
|
|
|
} else if (opp) {
|
2022-06-10 06:32:04 +00:00
|
|
|
freq = opp->rates[0];
|
2022-06-03 09:31:30 +00:00
|
|
|
} else {
|
|
|
|
WARN_ON(1);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = clk_set_rate(opp_table->clk, freq);
|
2016-12-01 10:58:20 +00:00
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "%s: failed to set clock rate: %d\n", __func__,
|
|
|
|
ret);
|
2022-06-03 09:31:30 +00:00
|
|
|
} else {
|
|
|
|
opp_table->rate_clk_single = freq;
|
2016-12-01 10:58:20 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2022-06-10 07:07:25 +00:00
|
|
|
/*
|
|
|
|
* Simple implementation for configuring multiple clocks. Configure clocks in
|
|
|
|
* the order in which they are present in the array while scaling up.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_config_clks_simple(struct device *dev,
|
|
|
|
struct opp_table *opp_table, struct dev_pm_opp *opp, void *data,
|
|
|
|
bool scaling_down)
|
|
|
|
{
|
|
|
|
int ret, i;
|
|
|
|
|
|
|
|
if (scaling_down) {
|
|
|
|
for (i = opp_table->clk_count - 1; i >= 0; i--) {
|
|
|
|
ret = clk_set_rate(opp_table->clks[i], opp->rates[i]);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "%s: failed to set clock rate: %d\n", __func__,
|
|
|
|
ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
for (i = 0; i < opp_table->clk_count; i++) {
|
|
|
|
ret = clk_set_rate(opp_table->clks[i], opp->rates[i]);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "%s: failed to set clock rate: %d\n", __func__,
|
|
|
|
ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-08-15 12:44:37 +00:00
|
|
|
return 0;
|
2022-06-10 07:07:25 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_config_clks_simple);
|
|
|
|
|
2022-05-31 07:19:19 +00:00
|
|
|
static int _opp_config_regulator_single(struct device *dev,
|
|
|
|
struct dev_pm_opp *old_opp, struct dev_pm_opp *new_opp,
|
|
|
|
struct regulator **regulators, unsigned int count)
|
2016-12-01 10:58:20 +00:00
|
|
|
{
|
2022-05-31 07:19:19 +00:00
|
|
|
struct regulator *reg = regulators[0];
|
2016-12-01 10:58:20 +00:00
|
|
|
int ret;
|
|
|
|
|
|
|
|
/* This function only supports single regulator per device */
|
2022-05-31 07:19:19 +00:00
|
|
|
if (WARN_ON(count > 1)) {
|
2016-12-01 10:58:20 +00:00
|
|
|
dev_err(dev, "multiple regulators are not supported\n");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2022-05-31 07:19:19 +00:00
|
|
|
ret = _set_opp_voltage(dev, reg, new_opp->supplies);
|
2016-12-01 10:58:20 +00:00
|
|
|
if (ret)
|
2022-05-31 07:19:19 +00:00
|
|
|
return ret;
|
2016-12-01 10:58:20 +00:00
|
|
|
|
2019-07-19 15:05:32 +00:00
|
|
|
/*
|
|
|
|
* Enable the regulator after setting its voltages, otherwise it breaks
|
|
|
|
* some boot-enabled regulators.
|
|
|
|
*/
|
2022-05-31 07:19:19 +00:00
|
|
|
if (unlikely(!new_opp->opp_table->enabled)) {
|
2019-07-19 15:05:32 +00:00
|
|
|
ret = regulator_enable(reg);
|
|
|
|
if (ret < 0)
|
|
|
|
dev_warn(dev, "Failed to enable regulator: %d", ret);
|
|
|
|
}
|
|
|
|
|
2016-12-01 10:58:20 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2020-05-27 04:03:44 +00:00
|
|
|
static int _set_opp_bw(const struct opp_table *opp_table,
|
2021-01-21 09:57:55 +00:00
|
|
|
struct dev_pm_opp *opp, struct device *dev)
|
2020-05-27 04:03:44 +00:00
|
|
|
{
|
|
|
|
u32 avg, peak;
|
|
|
|
int i, ret;
|
|
|
|
|
|
|
|
if (!opp_table->paths)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
for (i = 0; i < opp_table->path_count; i++) {
|
2021-01-21 09:57:55 +00:00
|
|
|
if (!opp) {
|
2020-05-27 04:03:44 +00:00
|
|
|
avg = 0;
|
|
|
|
peak = 0;
|
|
|
|
} else {
|
|
|
|
avg = opp->bandwidth[i].avg;
|
|
|
|
peak = opp->bandwidth[i].peak;
|
|
|
|
}
|
|
|
|
ret = icc_set_bw(opp_table->paths[i], avg, peak);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "Failed to %s bandwidth[%d]: %d\n",
|
2021-01-21 09:57:55 +00:00
|
|
|
opp ? "set" : "remove", i, ret);
|
2020-05-27 04:03:44 +00:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2023-02-22 11:06:38 +00:00
|
|
|
static int _set_performance_state(struct device *dev, struct device *pd_dev,
|
|
|
|
struct dev_pm_opp *opp, int i)
|
2020-07-30 08:01:44 +00:00
|
|
|
{
|
2023-06-14 09:59:32 +00:00
|
|
|
unsigned int pstate = likely(opp) ? opp->required_opps[i]->level: 0;
|
2020-07-30 08:01:44 +00:00
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (!pd_dev)
|
|
|
|
return 0;
|
|
|
|
|
2023-09-25 13:17:11 +00:00
|
|
|
ret = dev_pm_domain_set_performance_state(pd_dev, pstate);
|
2020-07-30 08:01:44 +00:00
|
|
|
if (ret) {
|
2022-06-03 09:57:55 +00:00
|
|
|
dev_err(dev, "Failed to set performance state of %s: %d (%d)\n",
|
2020-07-30 08:01:44 +00:00
|
|
|
dev_name(pd_dev), pstate, ret);
|
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2023-02-22 11:06:38 +00:00
|
|
|
static int _opp_set_required_opps_generic(struct device *dev,
|
|
|
|
struct opp_table *opp_table, struct dev_pm_opp *opp, bool scaling_down)
|
|
|
|
{
|
|
|
|
dev_err(dev, "setting required-opps isn't supported for non-genpd devices\n");
|
|
|
|
return -ENOENT;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int _opp_set_required_opps_genpd(struct device *dev,
|
|
|
|
struct opp_table *opp_table, struct dev_pm_opp *opp, bool scaling_down)
|
2018-06-14 04:33:26 +00:00
|
|
|
{
|
2023-02-22 11:06:37 +00:00
|
|
|
struct device **genpd_virt_devs =
|
|
|
|
opp_table->genpd_virt_devs ? opp_table->genpd_virt_devs : &dev;
|
2023-10-12 06:20:59 +00:00
|
|
|
int index, target, delta, ret;
|
2023-10-13 05:34:38 +00:00
|
|
|
|
|
|
|
/* Scaling up? Set required OPPs in normal order, else reverse */
|
|
|
|
if (!scaling_down) {
|
|
|
|
index = 0;
|
|
|
|
target = opp_table->required_opp_count;
|
|
|
|
delta = 1;
|
|
|
|
} else {
|
|
|
|
index = opp_table->required_opp_count - 1;
|
|
|
|
target = -1;
|
|
|
|
delta = -1;
|
|
|
|
}
|
2018-06-14 04:33:26 +00:00
|
|
|
|
2023-10-13 05:34:38 +00:00
|
|
|
while (index != target) {
|
|
|
|
ret = _set_performance_state(dev, genpd_virt_devs[index], opp, index);
|
|
|
|
if (ret)
|
2023-10-12 06:20:59 +00:00
|
|
|
return ret;
|
2023-10-13 05:34:38 +00:00
|
|
|
|
|
|
|
index += delta;
|
2018-06-14 04:33:26 +00:00
|
|
|
}
|
2020-07-30 08:01:45 +00:00
|
|
|
|
2023-10-12 06:20:59 +00:00
|
|
|
return 0;
|
2018-06-14 04:33:26 +00:00
|
|
|
}
|
|
|
|
|
2023-02-22 11:06:38 +00:00
|
|
|
/* This is only called for PM domain for now */
|
|
|
|
static int _set_required_opps(struct device *dev, struct opp_table *opp_table,
|
|
|
|
struct dev_pm_opp *opp, bool up)
|
|
|
|
{
|
|
|
|
/* required-opps not fully initialized yet */
|
|
|
|
if (lazy_linking_pending(opp_table))
|
|
|
|
return -EBUSY;
|
|
|
|
|
|
|
|
if (opp_table->set_required_opps)
|
|
|
|
return opp_table->set_required_opps(dev, opp_table, opp, up);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Update set_required_opps handler */
|
|
|
|
void _update_set_required_opps(struct opp_table *opp_table)
|
|
|
|
{
|
|
|
|
/* Already set */
|
|
|
|
if (opp_table->set_required_opps)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* All required OPPs will belong to genpd or none */
|
|
|
|
if (opp_table->required_opp_tables[0]->is_genpd)
|
|
|
|
opp_table->set_required_opps = _opp_set_required_opps_genpd;
|
|
|
|
else
|
|
|
|
opp_table->set_required_opps = _opp_set_required_opps_generic;
|
|
|
|
}
|
|
|
|
|
2023-09-25 13:17:12 +00:00
|
|
|
static int _set_opp_level(struct device *dev, struct opp_table *opp_table,
|
|
|
|
struct dev_pm_opp *opp)
|
|
|
|
{
|
|
|
|
unsigned int level = 0;
|
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
if (opp) {
|
|
|
|
if (!opp->level)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
level = opp->level;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Request a new performance state through the device's PM domain. */
|
|
|
|
ret = dev_pm_domain_set_performance_state(dev, level);
|
|
|
|
if (ret)
|
|
|
|
dev_err(dev, "Failed to set performance state %u (%d)\n", level,
|
|
|
|
ret);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2021-01-20 10:46:48 +00:00
|
|
|
static void _find_current_opp(struct device *dev, struct opp_table *opp_table)
|
|
|
|
{
|
|
|
|
struct dev_pm_opp *opp = ERR_PTR(-ENODEV);
|
|
|
|
unsigned long freq;
|
|
|
|
|
|
|
|
if (!IS_ERR(opp_table->clk)) {
|
|
|
|
freq = clk_get_rate(opp_table->clk);
|
|
|
|
opp = _find_freq_ceil(opp_table, &freq);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Unable to find the current OPP ? Pick the first from the list since
|
|
|
|
* it is in ascending order, otherwise rest of the code will need to
|
|
|
|
* make special checks to validate current_opp.
|
|
|
|
*/
|
|
|
|
if (IS_ERR(opp)) {
|
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
opp = list_first_entry(&opp_table->opp_list, struct dev_pm_opp, node);
|
|
|
|
dev_pm_opp_get(opp);
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
}
|
|
|
|
|
|
|
|
opp_table->current_opp = opp;
|
|
|
|
}
|
|
|
|
|
2021-01-21 06:38:45 +00:00
|
|
|
static int _disable_opp_table(struct device *dev, struct opp_table *opp_table)
|
2020-08-13 04:18:04 +00:00
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (!opp_table->enabled)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Some drivers need to support cases where some platforms may
|
|
|
|
* have OPP table for the device, while others don't and
|
|
|
|
* opp_set_rate() just needs to behave like clk_set_rate().
|
|
|
|
*/
|
|
|
|
if (!_get_opp_count(opp_table))
|
|
|
|
return 0;
|
|
|
|
|
2021-01-21 09:57:55 +00:00
|
|
|
ret = _set_opp_bw(opp_table, NULL, dev);
|
2020-08-13 04:18:04 +00:00
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
if (opp_table->regulators)
|
|
|
|
regulator_disable(opp_table->regulators[0]);
|
|
|
|
|
2023-09-25 13:17:12 +00:00
|
|
|
ret = _set_opp_level(dev, opp_table, NULL);
|
|
|
|
if (ret)
|
|
|
|
goto out;
|
|
|
|
|
2020-07-30 08:01:45 +00:00
|
|
|
ret = _set_required_opps(dev, opp_table, NULL, false);
|
2020-08-13 04:18:04 +00:00
|
|
|
|
2023-09-25 13:17:12 +00:00
|
|
|
out:
|
2020-08-13 04:18:04 +00:00
|
|
|
opp_table->enabled = false;
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2021-01-21 06:42:09 +00:00
|
|
|
static int _set_opp(struct device *dev, struct opp_table *opp_table,
|
2022-06-03 09:31:30 +00:00
|
|
|
struct dev_pm_opp *opp, void *clk_data, bool forced)
|
2016-02-09 05:00:39 +00:00
|
|
|
{
|
2021-01-21 06:42:09 +00:00
|
|
|
struct dev_pm_opp *old_opp;
|
2021-01-21 10:30:12 +00:00
|
|
|
int scaling_down, ret;
|
2016-02-09 05:00:39 +00:00
|
|
|
|
2021-01-21 06:42:09 +00:00
|
|
|
if (unlikely(!opp))
|
|
|
|
return _disable_opp_table(dev, opp_table);
|
2020-04-08 13:46:27 +00:00
|
|
|
|
2021-01-20 10:46:48 +00:00
|
|
|
/* Find the currently set OPP if we don't know already */
|
|
|
|
if (unlikely(!opp_table->current_opp))
|
|
|
|
_find_current_opp(dev, opp_table);
|
2016-02-09 05:00:39 +00:00
|
|
|
|
2021-01-20 10:46:48 +00:00
|
|
|
old_opp = opp_table->current_opp;
|
|
|
|
|
|
|
|
/* Return early if nothing to do */
|
2022-06-03 09:31:30 +00:00
|
|
|
if (!forced && old_opp == opp && opp_table->enabled) {
|
2023-05-20 17:00:35 +00:00
|
|
|
dev_dbg_ratelimited(dev, "%s: OPPs are same, nothing to do\n", __func__);
|
2021-01-21 06:42:09 +00:00
|
|
|
return 0;
|
2016-02-09 05:00:39 +00:00
|
|
|
}
|
|
|
|
|
2021-01-21 10:30:12 +00:00
|
|
|
dev_dbg(dev, "%s: switching OPP: Freq %lu -> %lu Hz, Level %u -> %u, Bw %u -> %u\n",
|
2022-06-10 06:32:04 +00:00
|
|
|
__func__, old_opp->rates[0], opp->rates[0], old_opp->level,
|
|
|
|
opp->level, old_opp->bandwidth ? old_opp->bandwidth[0].peak : 0,
|
2021-01-21 10:30:12 +00:00
|
|
|
opp->bandwidth ? opp->bandwidth[0].peak : 0);
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
scaling_down = _opp_compare_key(opp_table, old_opp, opp);
|
2021-01-21 10:30:12 +00:00
|
|
|
if (scaling_down == -1)
|
|
|
|
scaling_down = 0;
|
2016-12-01 10:58:19 +00:00
|
|
|
|
2018-06-14 04:33:26 +00:00
|
|
|
/* Scaling up? Configure required OPPs before frequency */
|
2021-01-21 10:30:12 +00:00
|
|
|
if (!scaling_down) {
|
2020-07-30 08:01:45 +00:00
|
|
|
ret = _set_required_opps(dev, opp_table, opp, true);
|
2021-01-28 10:00:00 +00:00
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "Failed to set required opps: %d\n", ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2023-09-25 13:17:12 +00:00
|
|
|
ret = _set_opp_level(dev, opp_table, opp);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
2021-01-28 10:00:00 +00:00
|
|
|
ret = _set_opp_bw(opp_table, opp, dev);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "Failed to set bw: %d\n", ret);
|
2021-01-21 06:42:09 +00:00
|
|
|
return ret;
|
2021-01-28 10:00:00 +00:00
|
|
|
}
|
2022-07-04 08:15:08 +00:00
|
|
|
|
|
|
|
if (opp_table->config_regulators) {
|
|
|
|
ret = opp_table->config_regulators(dev, old_opp, opp,
|
|
|
|
opp_table->regulators,
|
|
|
|
opp_table->regulator_count);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "Failed to set regulator voltages: %d\n",
|
|
|
|
ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
2018-06-14 04:33:26 +00:00
|
|
|
}
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
if (opp_table->config_clks) {
|
|
|
|
ret = opp_table->config_clks(dev, opp_table, opp, clk_data, scaling_down);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
}
|
2021-01-28 10:00:00 +00:00
|
|
|
|
2018-06-14 04:33:26 +00:00
|
|
|
/* Scaling down? Configure required OPPs after frequency */
|
2021-01-28 10:00:00 +00:00
|
|
|
if (scaling_down) {
|
2022-07-04 08:15:08 +00:00
|
|
|
if (opp_table->config_regulators) {
|
|
|
|
ret = opp_table->config_regulators(dev, old_opp, opp,
|
|
|
|
opp_table->regulators,
|
|
|
|
opp_table->regulator_count);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "Failed to set regulator voltages: %d\n",
|
|
|
|
ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-01-28 10:00:00 +00:00
|
|
|
ret = _set_opp_bw(opp_table, opp, dev);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(dev, "Failed to set bw: %d\n", ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2023-09-25 13:17:12 +00:00
|
|
|
ret = _set_opp_level(dev, opp_table, opp);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
2020-07-30 08:01:45 +00:00
|
|
|
ret = _set_required_opps(dev, opp_table, opp, false);
|
2021-01-28 10:00:00 +00:00
|
|
|
if (ret) {
|
2018-06-14 04:33:26 +00:00
|
|
|
dev_err(dev, "Failed to set required opps: %d\n", ret);
|
2021-01-28 10:00:00 +00:00
|
|
|
return ret;
|
|
|
|
}
|
2016-12-01 10:58:19 +00:00
|
|
|
}
|
|
|
|
|
2021-01-28 10:00:00 +00:00
|
|
|
opp_table->enabled = true;
|
|
|
|
dev_pm_opp_put(old_opp);
|
2021-01-20 10:46:48 +00:00
|
|
|
|
2021-01-28 10:00:00 +00:00
|
|
|
/* Make sure current_opp doesn't get freed */
|
|
|
|
dev_pm_opp_get(opp);
|
|
|
|
opp_table->current_opp = opp;
|
2020-05-12 12:53:23 +00:00
|
|
|
|
2021-01-21 06:42:09 +00:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dev_pm_opp_set_rate() - Configure new OPP based on frequency
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @target_freq: frequency to achieve
|
|
|
|
*
|
|
|
|
* This configures the power-supplies to the levels specified by the OPP
|
|
|
|
* corresponding to the target_freq, and programs the clock to a value <=
|
|
|
|
* target_freq, as rounded by clk_round_rate(). Device wanting to run at fmax
|
|
|
|
* provided by the opp, should have already rounded to the target OPP's
|
|
|
|
* frequency.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_set_rate(struct device *dev, unsigned long target_freq)
|
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
unsigned long freq = 0, temp_freq;
|
|
|
|
struct dev_pm_opp *opp = NULL;
|
2022-06-03 09:31:30 +00:00
|
|
|
bool forced = false;
|
2021-01-21 06:42:09 +00:00
|
|
|
int ret;
|
|
|
|
|
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table)) {
|
|
|
|
dev_err(dev, "%s: device's opp table doesn't exist\n", __func__);
|
|
|
|
return PTR_ERR(opp_table);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (target_freq) {
|
|
|
|
/*
|
|
|
|
* For IO devices which require an OPP on some platforms/SoCs
|
|
|
|
* while just needing to scale the clock on some others
|
|
|
|
* we look for empty OPP tables with just a clock handle and
|
|
|
|
* scale only the clk. This makes dev_pm_opp_set_rate()
|
|
|
|
* equivalent to a clk_set_rate()
|
|
|
|
*/
|
|
|
|
if (!_get_opp_count(opp_table)) {
|
2022-06-10 06:32:04 +00:00
|
|
|
ret = opp_table->config_clks(dev, opp_table, NULL,
|
|
|
|
&target_freq, false);
|
2021-01-21 06:42:09 +00:00
|
|
|
goto put_opp_table;
|
|
|
|
}
|
|
|
|
|
|
|
|
freq = clk_round_rate(opp_table->clk, target_freq);
|
|
|
|
if ((long)freq <= 0)
|
|
|
|
freq = target_freq;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The clock driver may support finer resolution of the
|
|
|
|
* frequencies than the OPP table, don't update the frequency we
|
|
|
|
* pass to clk_set_rate() here.
|
|
|
|
*/
|
|
|
|
temp_freq = freq;
|
|
|
|
opp = _find_freq_ceil(opp_table, &temp_freq);
|
|
|
|
if (IS_ERR(opp)) {
|
|
|
|
ret = PTR_ERR(opp);
|
|
|
|
dev_err(dev, "%s: failed to find OPP for freq %lu (%d)\n",
|
|
|
|
__func__, freq, ret);
|
|
|
|
goto put_opp_table;
|
|
|
|
}
|
2022-06-03 09:31:30 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* An OPP entry specifies the highest frequency at which other
|
|
|
|
* properties of the OPP entry apply. Even if the new OPP is
|
|
|
|
* same as the old one, we may still reach here for a different
|
|
|
|
* value of the frequency. In such a case, do not abort but
|
|
|
|
* configure the hardware to the desired frequency forcefully.
|
|
|
|
*/
|
|
|
|
forced = opp_table->rate_clk_single != target_freq;
|
2021-01-21 06:42:09 +00:00
|
|
|
}
|
|
|
|
|
2022-06-03 09:31:30 +00:00
|
|
|
ret = _set_opp(dev, opp_table, opp, &target_freq, forced);
|
2021-01-21 06:42:09 +00:00
|
|
|
|
|
|
|
if (target_freq)
|
|
|
|
dev_pm_opp_put(opp);
|
2022-06-03 09:31:30 +00:00
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
put_opp_table:
|
2017-01-23 04:41:48 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2017-01-23 04:41:49 +00:00
|
|
|
return ret;
|
2016-02-09 05:00:39 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_set_rate);
|
|
|
|
|
2021-01-21 06:45:36 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_set_opp() - Configure device for OPP
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @opp: OPP to set to
|
|
|
|
*
|
|
|
|
* This configures the device based on the properties of the OPP passed to this
|
|
|
|
* routine.
|
|
|
|
*
|
|
|
|
* Return: 0 on success, a negative error number otherwise.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_set_opp(struct device *dev, struct dev_pm_opp *opp)
|
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table)) {
|
|
|
|
dev_err(dev, "%s: device opp doesn't exist\n", __func__);
|
|
|
|
return PTR_ERR(opp_table);
|
|
|
|
}
|
|
|
|
|
2022-06-03 09:31:30 +00:00
|
|
|
ret = _set_opp(dev, opp_table, opp, NULL, false);
|
2021-01-21 06:45:36 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_set_opp);
|
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
/* OPP-dev Helpers */
|
|
|
|
static void _remove_opp_dev(struct opp_device *opp_dev,
|
|
|
|
struct opp_table *opp_table)
|
2015-07-29 10:53:04 +00:00
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_debug_unregister(opp_dev, opp_table);
|
|
|
|
list_del(&opp_dev->node);
|
2017-01-23 04:41:49 +00:00
|
|
|
kfree(opp_dev);
|
2015-07-29 10:53:04 +00:00
|
|
|
}
|
|
|
|
|
2020-10-22 06:42:27 +00:00
|
|
|
struct opp_device *_add_opp_dev(const struct device *dev,
|
|
|
|
struct opp_table *opp_table)
|
2015-07-29 10:53:04 +00:00
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_device *opp_dev;
|
2015-07-29 10:53:04 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_dev = kzalloc(sizeof(*opp_dev), GFP_KERNEL);
|
|
|
|
if (!opp_dev)
|
2015-07-29 10:53:04 +00:00
|
|
|
return NULL;
|
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
/* Initialize opp-dev */
|
|
|
|
opp_dev->dev = dev;
|
2018-08-03 01:35:21 +00:00
|
|
|
|
2020-10-22 06:42:27 +00:00
|
|
|
mutex_lock(&opp_table->lock);
|
2017-01-23 04:41:49 +00:00
|
|
|
list_add(&opp_dev->node, &opp_table->dev_list);
|
2020-10-22 06:42:27 +00:00
|
|
|
mutex_unlock(&opp_table->lock);
|
2015-07-29 10:53:04 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
/* Create debugfs entries for the opp_table */
|
2019-01-22 15:21:17 +00:00
|
|
|
opp_debug_register(opp_dev, opp_table);
|
2018-09-07 03:31:54 +00:00
|
|
|
|
|
|
|
return opp_dev;
|
|
|
|
}
|
|
|
|
|
2018-09-05 10:47:14 +00:00
|
|
|
static struct opp_table *_allocate_opp_table(struct device *dev, int index)
|
2014-12-10 04:15:34 +00:00
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table;
|
|
|
|
struct opp_device *opp_dev;
|
2016-02-09 05:00:38 +00:00
|
|
|
int ret;
|
2014-12-10 04:15:34 +00:00
|
|
|
|
|
|
|
/*
|
2016-02-16 08:47:53 +00:00
|
|
|
* Allocate a new OPP table. In the infrequent case where a new
|
2014-12-10 04:15:34 +00:00
|
|
|
* device is needed to be added, we pay this penalty.
|
|
|
|
*/
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_table = kzalloc(sizeof(*opp_table), GFP_KERNEL);
|
|
|
|
if (!opp_table)
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
return ERR_PTR(-ENOMEM);
|
2014-12-10 04:15:34 +00:00
|
|
|
|
2018-08-03 01:35:21 +00:00
|
|
|
mutex_init(&opp_table->lock);
|
2016-02-16 08:47:53 +00:00
|
|
|
INIT_LIST_HEAD(&opp_table->dev_list);
|
2019-11-25 08:27:58 +00:00
|
|
|
INIT_LIST_HEAD(&opp_table->lazy);
|
2015-07-29 10:53:04 +00:00
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
opp_table->clk = ERR_PTR(-ENODEV);
|
|
|
|
|
2018-12-11 11:09:36 +00:00
|
|
|
/* Mark regulator count uninitialized */
|
|
|
|
opp_table->regulator_count = -1;
|
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_dev = _add_opp_dev(dev, opp_table);
|
|
|
|
if (!opp_dev) {
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
ret = -ENOMEM;
|
|
|
|
goto err;
|
2015-07-29 10:53:04 +00:00
|
|
|
}
|
|
|
|
|
2018-09-05 10:47:14 +00:00
|
|
|
_of_init_opp_table(opp_table, dev, index);
|
2016-02-09 05:00:37 +00:00
|
|
|
|
2020-05-12 12:53:21 +00:00
|
|
|
/* Find interconnect path(s) for the device */
|
|
|
|
ret = dev_pm_opp_of_find_icc_paths(dev, opp_table);
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
if (ret) {
|
|
|
|
if (ret == -EPROBE_DEFER)
|
2021-01-28 06:35:22 +00:00
|
|
|
goto remove_opp_dev;
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
|
2020-05-12 12:53:21 +00:00
|
|
|
dev_warn(dev, "%s: Error finding interconnect paths: %d\n",
|
|
|
|
__func__, ret);
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
}
|
2020-05-12 12:53:21 +00:00
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
BLOCKING_INIT_NOTIFIER_HEAD(&opp_table->head);
|
2016-02-16 08:47:53 +00:00
|
|
|
INIT_LIST_HEAD(&opp_table->opp_list);
|
2017-01-23 04:41:42 +00:00
|
|
|
kref_init(&opp_table->kref);
|
2014-12-10 04:15:34 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
return opp_table;
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
|
2020-12-24 10:49:27 +00:00
|
|
|
remove_opp_dev:
|
2023-05-30 15:54:46 +00:00
|
|
|
_of_clear_opp_table(opp_table);
|
2020-12-24 10:49:27 +00:00
|
|
|
_remove_opp_dev(opp_dev, opp_table);
|
2023-05-30 15:54:46 +00:00
|
|
|
mutex_destroy(&opp_table->lock);
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
err:
|
|
|
|
kfree(opp_table);
|
|
|
|
return ERR_PTR(ret);
|
2014-12-10 04:15:34 +00:00
|
|
|
}
|
|
|
|
|
2017-01-23 04:41:42 +00:00
|
|
|
void _get_opp_table_kref(struct opp_table *opp_table)
|
2017-01-02 09:11:04 +00:00
|
|
|
{
|
2017-01-23 04:41:42 +00:00
|
|
|
kref_get(&opp_table->kref);
|
|
|
|
}
|
|
|
|
|
2021-01-28 06:35:22 +00:00
|
|
|
static struct opp_table *_update_opp_table_clk(struct device *dev,
|
|
|
|
struct opp_table *opp_table,
|
|
|
|
bool getclk)
|
|
|
|
{
|
2021-01-29 10:42:04 +00:00
|
|
|
int ret;
|
|
|
|
|
2021-01-28 06:35:22 +00:00
|
|
|
/*
|
2022-06-10 06:32:04 +00:00
|
|
|
* Return early if we don't need to get clk or we have already done it
|
2021-01-28 06:35:22 +00:00
|
|
|
* earlier.
|
|
|
|
*/
|
2022-06-10 06:32:04 +00:00
|
|
|
if (!getclk || IS_ERR(opp_table) || !IS_ERR(opp_table->clk) ||
|
|
|
|
opp_table->clks)
|
2021-01-28 06:35:22 +00:00
|
|
|
return opp_table;
|
|
|
|
|
|
|
|
/* Find clk for the device */
|
|
|
|
opp_table->clk = clk_get(dev, NULL);
|
|
|
|
|
2021-01-29 10:42:04 +00:00
|
|
|
ret = PTR_ERR_OR_ZERO(opp_table->clk);
|
2022-06-10 06:32:04 +00:00
|
|
|
if (!ret) {
|
|
|
|
opp_table->config_clks = _opp_config_clk_single;
|
|
|
|
opp_table->clk_count = 1;
|
2021-01-29 10:42:04 +00:00
|
|
|
return opp_table;
|
2022-06-10 06:32:04 +00:00
|
|
|
}
|
2021-01-28 06:35:22 +00:00
|
|
|
|
2021-01-29 10:42:04 +00:00
|
|
|
if (ret == -ENOENT) {
|
2022-06-10 06:32:04 +00:00
|
|
|
/*
|
|
|
|
* There are few platforms which don't want the OPP core to
|
|
|
|
* manage device's clock settings. In such cases neither the
|
|
|
|
* platform provides the clks explicitly to us, nor the DT
|
|
|
|
* contains a valid clk entry. The OPP nodes in DT may still
|
|
|
|
* contain "opp-hz" property though, which we need to parse and
|
|
|
|
* allow the platform to find an OPP based on freq later on.
|
|
|
|
*
|
|
|
|
* This is a simple solution to take care of such corner cases,
|
|
|
|
* i.e. make the clk_count 1, which lets us allocate space for
|
|
|
|
* frequency in opp->rates and also parse the entries in DT.
|
|
|
|
*/
|
|
|
|
opp_table->clk_count = 1;
|
|
|
|
|
2021-01-28 06:35:22 +00:00
|
|
|
dev_dbg(dev, "%s: Couldn't find clock: %d\n", __func__, ret);
|
2021-01-29 10:42:04 +00:00
|
|
|
return opp_table;
|
2021-01-28 06:35:22 +00:00
|
|
|
}
|
|
|
|
|
2021-01-29 10:42:04 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
|
|
|
dev_err_probe(dev, ret, "Couldn't find clock\n");
|
|
|
|
|
|
|
|
return ERR_PTR(ret);
|
2021-01-28 06:35:22 +00:00
|
|
|
}
|
|
|
|
|
2020-10-27 11:23:21 +00:00
|
|
|
/*
|
|
|
|
* We need to make sure that the OPP table for a device doesn't get added twice,
|
|
|
|
* if this routine gets called in parallel with the same device pointer.
|
|
|
|
*
|
|
|
|
* The simplest way to enforce that is to perform everything (find existing
|
|
|
|
* table and if not found, create a new one) under the opp_table_lock, so only
|
|
|
|
* one creator gets access to the same. But that expands the critical section
|
|
|
|
* under the lock and may end up causing circular dependencies with frameworks
|
|
|
|
* like debugfs, interconnect or clock framework as they may be direct or
|
|
|
|
* indirect users of OPP core.
|
|
|
|
*
|
|
|
|
* And for that reason we have to go for a bit tricky implementation here, which
|
|
|
|
* uses the opp_tables_busy flag to indicate if another creator is in the middle
|
|
|
|
* of adding an OPP table and others should wait for it to finish.
|
|
|
|
*/
|
2021-01-28 06:35:22 +00:00
|
|
|
struct opp_table *_add_opp_table_indexed(struct device *dev, int index,
|
|
|
|
bool getclk)
|
2017-01-23 04:41:42 +00:00
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
|
2020-10-27 11:23:21 +00:00
|
|
|
again:
|
2017-01-23 04:41:42 +00:00
|
|
|
mutex_lock(&opp_table_lock);
|
|
|
|
|
2017-01-23 04:41:48 +00:00
|
|
|
opp_table = _find_opp_table_unlocked(dev);
|
|
|
|
if (!IS_ERR(opp_table))
|
2017-01-23 04:41:42 +00:00
|
|
|
goto unlock;
|
|
|
|
|
2020-10-27 11:23:21 +00:00
|
|
|
/*
|
|
|
|
* The opp_tables list or an OPP table's dev_list is getting updated by
|
|
|
|
* another user, wait for it to finish.
|
|
|
|
*/
|
|
|
|
if (unlikely(opp_tables_busy)) {
|
|
|
|
mutex_unlock(&opp_table_lock);
|
|
|
|
cpu_relax();
|
|
|
|
goto again;
|
|
|
|
}
|
|
|
|
|
|
|
|
opp_tables_busy = true;
|
2018-09-07 03:31:54 +00:00
|
|
|
opp_table = _managed_opp(dev, index);
|
2020-10-27 11:23:21 +00:00
|
|
|
|
|
|
|
/* Drop the lock to reduce the size of critical section */
|
|
|
|
mutex_unlock(&opp_table_lock);
|
|
|
|
|
2018-09-07 03:31:54 +00:00
|
|
|
if (opp_table) {
|
2020-10-22 06:42:27 +00:00
|
|
|
if (!_add_opp_dev(dev, opp_table)) {
|
2018-09-07 03:31:54 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
opp_table = ERR_PTR(-ENOMEM);
|
2018-09-07 03:31:54 +00:00
|
|
|
}
|
2020-10-27 11:23:21 +00:00
|
|
|
|
|
|
|
mutex_lock(&opp_table_lock);
|
|
|
|
} else {
|
|
|
|
opp_table = _allocate_opp_table(dev, index);
|
|
|
|
|
|
|
|
mutex_lock(&opp_table_lock);
|
|
|
|
if (!IS_ERR(opp_table))
|
|
|
|
list_add(&opp_table->node, &opp_tables);
|
2018-09-07 03:31:54 +00:00
|
|
|
}
|
|
|
|
|
2020-10-27 11:23:21 +00:00
|
|
|
opp_tables_busy = false;
|
2017-01-23 04:41:42 +00:00
|
|
|
|
|
|
|
unlock:
|
|
|
|
mutex_unlock(&opp_table_lock);
|
|
|
|
|
2021-01-28 06:35:22 +00:00
|
|
|
return _update_opp_table_clk(dev, opp_table, getclk);
|
2017-01-23 04:41:42 +00:00
|
|
|
}
|
2018-09-05 10:47:14 +00:00
|
|
|
|
2021-01-28 06:35:22 +00:00
|
|
|
static struct opp_table *_add_opp_table(struct device *dev, bool getclk)
|
2018-09-05 10:47:14 +00:00
|
|
|
{
|
2021-01-28 06:35:22 +00:00
|
|
|
return _add_opp_table_indexed(dev, 0, getclk);
|
2018-09-05 10:47:14 +00:00
|
|
|
}
|
2017-01-23 04:41:42 +00:00
|
|
|
|
2020-11-06 05:07:16 +00:00
|
|
|
struct opp_table *dev_pm_opp_get_opp_table(struct device *dev)
|
2018-09-05 10:47:14 +00:00
|
|
|
{
|
2020-11-06 05:07:16 +00:00
|
|
|
return _find_opp_table(dev);
|
2018-09-05 10:47:14 +00:00
|
|
|
}
|
2020-11-06 05:07:16 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_get_opp_table);
|
2018-09-05 10:47:14 +00:00
|
|
|
|
2017-01-23 04:41:45 +00:00
|
|
|
static void _opp_table_kref_release(struct kref *kref)
|
2017-01-23 04:41:42 +00:00
|
|
|
{
|
|
|
|
struct opp_table *opp_table = container_of(kref, struct opp_table, kref);
|
2018-09-12 07:05:19 +00:00
|
|
|
struct opp_device *opp_dev, *temp;
|
2020-05-12 12:53:21 +00:00
|
|
|
int i;
|
2017-01-02 09:11:04 +00:00
|
|
|
|
2020-10-22 06:56:08 +00:00
|
|
|
/* Drop the lock as soon as we can */
|
|
|
|
list_del(&opp_table->node);
|
|
|
|
mutex_unlock(&opp_table_lock);
|
|
|
|
|
2021-01-20 10:46:48 +00:00
|
|
|
if (opp_table->current_opp)
|
|
|
|
dev_pm_opp_put(opp_table->current_opp);
|
|
|
|
|
2018-06-07 09:20:43 +00:00
|
|
|
_of_clear_opp_table(opp_table);
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
/* Release automatically acquired single clk */
|
2017-01-02 09:11:04 +00:00
|
|
|
if (!IS_ERR(opp_table->clk))
|
|
|
|
clk_put(opp_table->clk);
|
|
|
|
|
2020-05-12 12:53:21 +00:00
|
|
|
if (opp_table->paths) {
|
|
|
|
for (i = 0; i < opp_table->path_count; i++)
|
|
|
|
icc_put(opp_table->paths[i]);
|
|
|
|
kfree(opp_table->paths);
|
|
|
|
}
|
|
|
|
|
2018-09-12 07:05:19 +00:00
|
|
|
WARN_ON(!list_empty(&opp_table->opp_list));
|
2017-01-02 09:11:04 +00:00
|
|
|
|
2023-06-14 07:20:20 +00:00
|
|
|
list_for_each_entry_safe(opp_dev, temp, &opp_table->dev_list, node)
|
2018-09-12 07:05:19 +00:00
|
|
|
_remove_opp_dev(opp_dev, opp_table);
|
2017-01-02 09:11:04 +00:00
|
|
|
|
2017-01-23 04:41:41 +00:00
|
|
|
mutex_destroy(&opp_table->lock);
|
2017-01-23 04:41:49 +00:00
|
|
|
kfree(opp_table);
|
2017-01-23 04:41:42 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void dev_pm_opp_put_opp_table(struct opp_table *opp_table)
|
|
|
|
{
|
|
|
|
kref_put_mutex(&opp_table->kref, _opp_table_kref_release,
|
|
|
|
&opp_table_lock);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_put_opp_table);
|
|
|
|
|
2017-01-02 09:11:01 +00:00
|
|
|
void _opp_free(struct dev_pm_opp *opp)
|
2017-01-02 09:10:59 +00:00
|
|
|
{
|
|
|
|
kfree(opp);
|
|
|
|
}
|
|
|
|
|
2020-11-19 05:54:32 +00:00
|
|
|
static void _opp_kref_release(struct kref *kref)
|
2014-11-27 03:24:06 +00:00
|
|
|
{
|
2020-11-19 05:54:32 +00:00
|
|
|
struct dev_pm_opp *opp = container_of(kref, struct dev_pm_opp, kref);
|
|
|
|
struct opp_table *opp_table = opp->opp_table;
|
|
|
|
|
|
|
|
list_del(&opp->node);
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
|
2014-11-27 03:24:06 +00:00
|
|
|
/*
|
|
|
|
* Notify the changes in the availability of the operable
|
|
|
|
* frequency/voltage list.
|
|
|
|
*/
|
2017-01-23 04:41:49 +00:00
|
|
|
blocking_notifier_call_chain(&opp_table->head, OPP_EVENT_REMOVE, opp);
|
2022-07-18 13:36:32 +00:00
|
|
|
_of_clear_opp(opp_table, opp);
|
2015-11-11 02:29:01 +00:00
|
|
|
opp_debug_remove_one(opp);
|
2017-01-23 04:41:49 +00:00
|
|
|
kfree(opp);
|
2019-01-04 09:44:33 +00:00
|
|
|
}
|
2014-11-27 03:24:06 +00:00
|
|
|
|
2017-11-29 09:48:36 +00:00
|
|
|
void dev_pm_opp_get(struct dev_pm_opp *opp)
|
2017-01-23 04:41:47 +00:00
|
|
|
{
|
|
|
|
kref_get(&opp->kref);
|
|
|
|
}
|
|
|
|
|
2017-01-23 04:41:46 +00:00
|
|
|
void dev_pm_opp_put(struct dev_pm_opp *opp)
|
|
|
|
{
|
2020-11-19 05:54:32 +00:00
|
|
|
kref_put_mutex(&opp->kref, _opp_kref_release, &opp->opp_table->lock);
|
2017-01-23 04:41:46 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_put);
|
|
|
|
|
2014-11-27 03:24:06 +00:00
|
|
|
/**
|
2016-02-16 08:47:53 +00:00
|
|
|
* dev_pm_opp_remove() - Remove an OPP from OPP table
|
2014-11-27 03:24:06 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @freq: OPP to remove with matching 'freq'
|
|
|
|
*
|
2016-02-16 08:47:53 +00:00
|
|
|
* This function removes an opp from the opp table.
|
2014-11-27 03:24:06 +00:00
|
|
|
*/
|
|
|
|
void dev_pm_opp_remove(struct device *dev, unsigned long freq)
|
|
|
|
{
|
2022-03-24 07:18:15 +00:00
|
|
|
struct dev_pm_opp *opp = NULL, *iter;
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table;
|
2014-11-27 03:24:06 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table))
|
2017-01-23 04:41:48 +00:00
|
|
|
return;
|
2014-11-27 03:24:06 +00:00
|
|
|
|
2022-06-10 04:57:51 +00:00
|
|
|
if (!assert_single_clk(opp_table))
|
|
|
|
goto put_table;
|
|
|
|
|
2017-01-23 04:41:41 +00:00
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
|
2022-03-24 07:18:15 +00:00
|
|
|
list_for_each_entry(iter, &opp_table->opp_list, node) {
|
2022-06-10 06:32:04 +00:00
|
|
|
if (iter->rates[0] == freq) {
|
2022-03-24 07:18:15 +00:00
|
|
|
opp = iter;
|
2014-11-27 03:24:06 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-01-23 04:41:41 +00:00
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
|
2022-03-24 07:18:15 +00:00
|
|
|
if (opp) {
|
2017-01-23 04:41:48 +00:00
|
|
|
dev_pm_opp_put(opp);
|
2018-08-02 08:53:09 +00:00
|
|
|
|
|
|
|
/* Drop the reference taken by dev_pm_opp_add() */
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2017-01-23 04:41:48 +00:00
|
|
|
} else {
|
2014-11-27 03:24:06 +00:00
|
|
|
dev_warn(dev, "%s: Couldn't find OPP with freq: %lu\n",
|
|
|
|
__func__, freq);
|
|
|
|
}
|
|
|
|
|
2022-06-10 04:57:51 +00:00
|
|
|
put_table:
|
2018-08-02 08:53:09 +00:00
|
|
|
/* Drop the reference taken by _find_opp_table() */
|
2017-01-23 04:41:48 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2014-11-27 03:24:06 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_remove);
|
|
|
|
|
2020-11-19 05:54:32 +00:00
|
|
|
static struct dev_pm_opp *_opp_get_next(struct opp_table *opp_table,
|
|
|
|
bool dynamic)
|
|
|
|
{
|
|
|
|
struct dev_pm_opp *opp = NULL, *temp;
|
|
|
|
|
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
list_for_each_entry(temp, &opp_table->opp_list, node) {
|
2021-03-04 15:07:34 +00:00
|
|
|
/*
|
|
|
|
* Refcount must be dropped only once for each OPP by OPP core,
|
|
|
|
* do that with help of "removed" flag.
|
|
|
|
*/
|
|
|
|
if (!temp->removed && dynamic == temp->dynamic) {
|
2020-11-19 05:54:32 +00:00
|
|
|
opp = temp;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
return opp;
|
|
|
|
}
|
|
|
|
|
2021-03-04 15:07:34 +00:00
|
|
|
/*
|
|
|
|
* Can't call dev_pm_opp_put() from under the lock as debugfs removal needs to
|
|
|
|
* happen lock less to avoid circular dependency issues. This routine must be
|
|
|
|
* called without the opp_table->lock held.
|
|
|
|
*/
|
|
|
|
static void _opp_remove_all(struct opp_table *opp_table, bool dynamic)
|
2019-11-11 11:05:03 +00:00
|
|
|
{
|
2020-11-19 05:54:32 +00:00
|
|
|
struct dev_pm_opp *opp;
|
2019-11-11 11:05:03 +00:00
|
|
|
|
2021-03-04 15:07:34 +00:00
|
|
|
while ((opp = _opp_get_next(opp_table, dynamic))) {
|
|
|
|
opp->removed = true;
|
|
|
|
dev_pm_opp_put(opp);
|
|
|
|
|
|
|
|
/* Drop the references taken by dev_pm_opp_add() */
|
|
|
|
if (dynamic)
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
bool _opp_remove_all_static(struct opp_table *opp_table)
|
|
|
|
{
|
2019-11-11 11:05:03 +00:00
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
|
2020-08-31 07:33:06 +00:00
|
|
|
if (!opp_table->parsed_static_opps) {
|
2020-11-19 05:54:32 +00:00
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
return false;
|
2020-08-31 07:33:06 +00:00
|
|
|
}
|
|
|
|
|
2020-11-19 05:54:32 +00:00
|
|
|
if (--opp_table->parsed_static_opps) {
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
return true;
|
2019-11-11 11:05:03 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
mutex_unlock(&opp_table->lock);
|
2020-08-31 07:33:06 +00:00
|
|
|
|
2021-03-04 15:07:34 +00:00
|
|
|
_opp_remove_all(opp_table, false);
|
2020-11-19 05:54:32 +00:00
|
|
|
return true;
|
2019-11-11 11:05:03 +00:00
|
|
|
}
|
|
|
|
|
2019-01-04 09:44:33 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_remove_all_dynamic() - Remove all dynamically created OPPs
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
*
|
|
|
|
* This function removes all dynamically created OPPs from the opp table.
|
|
|
|
*/
|
|
|
|
void dev_pm_opp_remove_all_dynamic(struct device *dev)
|
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
|
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table))
|
|
|
|
return;
|
|
|
|
|
2021-03-04 15:07:34 +00:00
|
|
|
_opp_remove_all(opp_table, true);
|
2019-01-04 09:44:33 +00:00
|
|
|
|
|
|
|
/* Drop the reference taken by _find_opp_table() */
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_remove_all_dynamic);
|
|
|
|
|
2022-06-09 10:05:36 +00:00
|
|
|
struct dev_pm_opp *_opp_allocate(struct opp_table *opp_table)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2015-07-29 10:53:01 +00:00
|
|
|
struct dev_pm_opp *opp;
|
2022-06-10 06:32:04 +00:00
|
|
|
int supply_count, supply_size, icc_size, clk_size;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
/* Allocate space for at least one supply */
|
2022-06-09 10:05:36 +00:00
|
|
|
supply_count = opp_table->regulator_count > 0 ?
|
|
|
|
opp_table->regulator_count : 1;
|
2020-05-12 12:53:21 +00:00
|
|
|
supply_size = sizeof(*opp->supplies) * supply_count;
|
2022-06-10 06:32:04 +00:00
|
|
|
clk_size = sizeof(*opp->rates) * opp_table->clk_count;
|
2022-06-09 10:05:36 +00:00
|
|
|
icc_size = sizeof(*opp->bandwidth) * opp_table->path_count;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
/* allocate new OPP node and supplies structures */
|
2022-06-10 06:32:04 +00:00
|
|
|
opp = kzalloc(sizeof(*opp) + supply_size + clk_size + icc_size, GFP_KERNEL);
|
2017-01-02 09:11:01 +00:00
|
|
|
if (!opp)
|
2015-07-29 10:53:01 +00:00
|
|
|
return NULL;
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
/* Put the supplies, bw and clock at the end of the OPP structure */
|
2016-12-01 10:58:19 +00:00
|
|
|
opp->supplies = (struct dev_pm_opp_supply *)(opp + 1);
|
2022-06-10 06:32:04 +00:00
|
|
|
|
|
|
|
opp->rates = (unsigned long *)(opp->supplies + supply_count);
|
|
|
|
|
2020-05-12 12:53:21 +00:00
|
|
|
if (icc_size)
|
2022-06-10 06:32:04 +00:00
|
|
|
opp->bandwidth = (struct dev_pm_opp_icc_bw *)(opp->rates + opp_table->clk_count);
|
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
INIT_LIST_HEAD(&opp->node);
|
|
|
|
|
2015-07-29 10:53:01 +00:00
|
|
|
return opp;
|
|
|
|
}
|
|
|
|
|
2016-02-09 05:00:34 +00:00
|
|
|
static bool _opp_supported_by_regulators(struct dev_pm_opp *opp,
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table)
|
2016-02-09 05:00:34 +00:00
|
|
|
{
|
2016-12-01 10:58:19 +00:00
|
|
|
struct regulator *reg;
|
|
|
|
int i;
|
|
|
|
|
2018-12-11 11:02:47 +00:00
|
|
|
if (!opp_table->regulators)
|
|
|
|
return true;
|
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
for (i = 0; i < opp_table->regulator_count; i++) {
|
|
|
|
reg = opp_table->regulators[i];
|
|
|
|
|
|
|
|
if (!regulator_is_supported_voltage(reg,
|
|
|
|
opp->supplies[i].u_volt_min,
|
|
|
|
opp->supplies[i].u_volt_max)) {
|
|
|
|
pr_warn("%s: OPP minuV: %lu maxuV: %lu, not supported by regulator\n",
|
|
|
|
__func__, opp->supplies[i].u_volt_min,
|
|
|
|
opp->supplies[i].u_volt_max);
|
|
|
|
return false;
|
|
|
|
}
|
2016-02-09 05:00:34 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
static int _opp_compare_rate(struct opp_table *opp_table,
|
|
|
|
struct dev_pm_opp *opp1, struct dev_pm_opp *opp2)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < opp_table->clk_count; i++) {
|
|
|
|
if (opp1->rates[i] != opp2->rates[i])
|
|
|
|
return opp1->rates[i] < opp2->rates[i] ? -1 : 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Same rates for both OPPs */
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2022-07-05 06:20:47 +00:00
|
|
|
static int _opp_compare_bw(struct opp_table *opp_table, struct dev_pm_opp *opp1,
|
|
|
|
struct dev_pm_opp *opp2)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < opp_table->path_count; i++) {
|
|
|
|
if (opp1->bandwidth[i].peak != opp2->bandwidth[i].peak)
|
|
|
|
return opp1->bandwidth[i].peak < opp2->bandwidth[i].peak ? -1 : 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Same bw for both OPPs */
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2022-06-10 05:02:50 +00:00
|
|
|
/*
|
|
|
|
* Returns
|
|
|
|
* 0: opp1 == opp2
|
|
|
|
* 1: opp1 > opp2
|
|
|
|
* -1: opp1 < opp2
|
|
|
|
*/
|
2022-06-10 06:32:04 +00:00
|
|
|
int _opp_compare_key(struct opp_table *opp_table, struct dev_pm_opp *opp1,
|
|
|
|
struct dev_pm_opp *opp2)
|
2020-05-12 12:53:19 +00:00
|
|
|
{
|
2022-06-10 06:32:04 +00:00
|
|
|
int ret;
|
|
|
|
|
|
|
|
ret = _opp_compare_rate(opp_table, opp1, opp2);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
2022-07-05 06:20:47 +00:00
|
|
|
ret = _opp_compare_bw(opp_table, opp1, opp2);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
2022-06-10 06:32:04 +00:00
|
|
|
|
2020-05-12 12:53:19 +00:00
|
|
|
if (opp1->level != opp2->level)
|
|
|
|
return opp1->level < opp2->level ? -1 : 1;
|
2022-06-10 06:32:04 +00:00
|
|
|
|
|
|
|
/* Duplicate OPPs */
|
2020-05-12 12:53:19 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-04-06 09:05:45 +00:00
|
|
|
static int _opp_is_duplicate(struct device *dev, struct dev_pm_opp *new_opp,
|
|
|
|
struct opp_table *opp_table,
|
|
|
|
struct list_head **head)
|
2015-07-29 10:53:01 +00:00
|
|
|
{
|
|
|
|
struct dev_pm_opp *opp;
|
2020-05-12 12:53:19 +00:00
|
|
|
int opp_cmp;
|
2015-07-29 10:53:01 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Insert new OPP in order of increasing frequency and discard if
|
|
|
|
* already present.
|
|
|
|
*
|
2016-02-16 08:47:53 +00:00
|
|
|
* Need to use &opp_table->opp_list in the condition part of the 'for'
|
2015-07-29 10:53:01 +00:00
|
|
|
* loop, don't replace it with head otherwise it will become an infinite
|
|
|
|
* loop.
|
|
|
|
*/
|
2017-01-23 04:41:49 +00:00
|
|
|
list_for_each_entry(opp, &opp_table->opp_list, node) {
|
2022-06-10 06:32:04 +00:00
|
|
|
opp_cmp = _opp_compare_key(opp_table, new_opp, opp);
|
2020-05-12 12:53:19 +00:00
|
|
|
if (opp_cmp > 0) {
|
2018-04-06 09:05:45 +00:00
|
|
|
*head = &opp->node;
|
2015-07-29 10:53:01 +00:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2020-05-12 12:53:19 +00:00
|
|
|
if (opp_cmp < 0)
|
2018-04-06 09:05:45 +00:00
|
|
|
return 0;
|
2015-07-29 10:53:01 +00:00
|
|
|
|
|
|
|
/* Duplicate OPPs */
|
2015-07-29 10:53:04 +00:00
|
|
|
dev_warn(dev, "%s: duplicate OPPs detected. Existing: freq: %lu, volt: %lu, enabled: %d. New: freq: %lu, volt: %lu, enabled: %d\n",
|
2022-06-10 06:32:04 +00:00
|
|
|
__func__, opp->rates[0], opp->supplies[0].u_volt,
|
|
|
|
opp->available, new_opp->rates[0],
|
2016-12-01 10:58:19 +00:00
|
|
|
new_opp->supplies[0].u_volt, new_opp->available);
|
2015-07-29 10:53:01 +00:00
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
/* Should we compare voltages for all regulators here ? */
|
2018-04-06 09:05:45 +00:00
|
|
|
return opp->available &&
|
|
|
|
new_opp->supplies[0].u_volt == opp->supplies[0].u_volt ? -EBUSY : -EEXIST;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2019-11-25 08:27:58 +00:00
|
|
|
void _required_opps_available(struct dev_pm_opp *opp, int count)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < count; i++) {
|
|
|
|
if (opp->required_opps[i]->available)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
opp->available = false;
|
|
|
|
pr_warn("%s: OPP not supported by required OPP %pOF (%lu)\n",
|
2022-06-10 06:32:04 +00:00
|
|
|
__func__, opp->required_opps[i]->np, opp->rates[0]);
|
2019-11-25 08:27:58 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-04-06 09:05:45 +00:00
|
|
|
/*
|
|
|
|
* Returns:
|
|
|
|
* 0: On success. And appropriate error message for duplicate OPPs.
|
|
|
|
* -EBUSY: For OPP with same freq/volt and is available. The callers of
|
|
|
|
* _opp_add() must return 0 if they receive -EBUSY from it. This is to make
|
|
|
|
* sure we don't print error messages unnecessarily if different parts of
|
|
|
|
* kernel try to initialize the OPP table.
|
|
|
|
* -EEXIST: For OPP with same freq but different volt or is unavailable. This
|
|
|
|
* should be considered an error by the callers of _opp_add().
|
|
|
|
*/
|
|
|
|
int _opp_add(struct device *dev, struct dev_pm_opp *new_opp,
|
2022-06-08 06:27:24 +00:00
|
|
|
struct opp_table *opp_table)
|
2018-04-06 09:05:45 +00:00
|
|
|
{
|
|
|
|
struct list_head *head;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
head = &opp_table->opp_list;
|
2017-01-23 04:41:41 +00:00
|
|
|
|
2021-01-18 00:55:13 +00:00
|
|
|
ret = _opp_is_duplicate(dev, new_opp, opp_table, &head);
|
|
|
|
if (ret) {
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
return ret;
|
2015-07-29 10:53:01 +00:00
|
|
|
}
|
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
list_add(&new_opp->node, head);
|
2017-01-23 04:41:41 +00:00
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
|
|
|
|
new_opp->opp_table = opp_table;
|
2017-01-23 04:41:46 +00:00
|
|
|
kref_init(&new_opp->kref);
|
2015-07-29 10:53:01 +00:00
|
|
|
|
2019-01-22 15:21:17 +00:00
|
|
|
opp_debug_create_one(new_opp, opp_table);
|
2015-11-11 02:29:01 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
if (!_opp_supported_by_regulators(new_opp, opp_table)) {
|
2016-02-09 05:00:34 +00:00
|
|
|
new_opp->available = false;
|
|
|
|
dev_warn(dev, "%s: OPP not supported by regulators (%lu)\n",
|
2022-06-10 06:32:04 +00:00
|
|
|
__func__, new_opp->rates[0]);
|
2016-02-09 05:00:34 +00:00
|
|
|
}
|
|
|
|
|
2019-11-25 08:27:58 +00:00
|
|
|
/* required-opps not fully initialized yet */
|
|
|
|
if (lazy_linking_pending(opp_table))
|
|
|
|
return 0;
|
2021-01-18 00:55:14 +00:00
|
|
|
|
2019-11-25 08:27:58 +00:00
|
|
|
_required_opps_available(new_opp, opp_table->required_opp_count);
|
2021-01-18 00:55:14 +00:00
|
|
|
|
2015-07-29 10:53:01 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2014-12-24 17:22:57 +00:00
|
|
|
/**
|
2015-10-15 16:12:44 +00:00
|
|
|
* _opp_add_v1() - Allocate a OPP based on v1 bindings.
|
2017-01-02 09:11:01 +00:00
|
|
|
* @opp_table: OPP table
|
2014-12-24 17:22:57 +00:00
|
|
|
* @dev: device for which we do this operation
|
2023-09-25 13:17:09 +00:00
|
|
|
* @data: The OPP data for the OPP to add
|
2014-12-24 17:22:57 +00:00
|
|
|
* @dynamic: Dynamically added OPPs.
|
|
|
|
*
|
2016-02-16 08:47:53 +00:00
|
|
|
* This function adds an opp definition to the opp table and returns status.
|
2014-12-24 17:22:57 +00:00
|
|
|
* The opp is made available by default and it can be controlled using
|
|
|
|
* dev_pm_opp_enable/disable functions and may be removed by dev_pm_opp_remove.
|
|
|
|
*
|
2015-09-04 08:17:24 +00:00
|
|
|
* NOTE: "dynamic" parameter impacts OPPs added by the dev_pm_opp_of_add_table
|
|
|
|
* and freed by dev_pm_opp_of_remove_table.
|
2014-12-24 17:22:57 +00:00
|
|
|
*
|
|
|
|
* Return:
|
|
|
|
* 0 On success OR
|
|
|
|
* Duplicate OPPs (both freq and volt are same) and opp->available
|
|
|
|
* -EEXIST Freq are same and volt are different OR
|
|
|
|
* Duplicate OPPs (both freq and volt are same) and !opp->available
|
|
|
|
* -ENOMEM Memory allocation failure
|
|
|
|
*/
|
2017-01-02 09:11:01 +00:00
|
|
|
int _opp_add_v1(struct opp_table *opp_table, struct device *dev,
|
2023-09-25 13:17:09 +00:00
|
|
|
struct dev_pm_opp_data *data, bool dynamic)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2015-07-29 10:53:01 +00:00
|
|
|
struct dev_pm_opp *new_opp;
|
2023-09-25 13:17:09 +00:00
|
|
|
unsigned long tol, u_volt = data->u_volt;
|
2014-12-10 04:15:35 +00:00
|
|
|
int ret;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2022-06-10 04:57:51 +00:00
|
|
|
if (!assert_single_clk(opp_table))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2017-01-02 09:11:01 +00:00
|
|
|
new_opp = _opp_allocate(opp_table);
|
|
|
|
if (!new_opp)
|
|
|
|
return -ENOMEM;
|
2015-07-29 10:53:01 +00:00
|
|
|
|
2014-11-25 10:34:17 +00:00
|
|
|
/* populate the opp table */
|
2023-09-25 13:17:09 +00:00
|
|
|
new_opp->rates[0] = data->freq;
|
2023-09-25 13:17:10 +00:00
|
|
|
new_opp->level = data->level;
|
2016-02-16 08:47:53 +00:00
|
|
|
tol = u_volt * opp_table->voltage_tolerance_v1 / 100;
|
2016-12-01 10:58:19 +00:00
|
|
|
new_opp->supplies[0].u_volt = u_volt;
|
|
|
|
new_opp->supplies[0].u_volt_min = u_volt - tol;
|
|
|
|
new_opp->supplies[0].u_volt_max = u_volt + tol;
|
2014-11-25 10:34:17 +00:00
|
|
|
new_opp->available = true;
|
2015-07-29 10:53:01 +00:00
|
|
|
new_opp->dynamic = dynamic;
|
2014-11-25 10:34:17 +00:00
|
|
|
|
2022-06-08 06:27:24 +00:00
|
|
|
ret = _opp_add(dev, new_opp, opp_table);
|
2017-01-02 09:10:55 +00:00
|
|
|
if (ret) {
|
|
|
|
/* Don't return error for duplicate OPPs */
|
|
|
|
if (ret == -EBUSY)
|
|
|
|
ret = 0;
|
2014-12-10 04:15:35 +00:00
|
|
|
goto free_opp;
|
2017-01-02 09:10:55 +00:00
|
|
|
}
|
2014-05-22 05:06:26 +00:00
|
|
|
|
2011-09-30 20:35:12 +00:00
|
|
|
/*
|
|
|
|
* Notify the changes in the availability of the operable
|
|
|
|
* frequency/voltage list.
|
|
|
|
*/
|
2017-01-23 04:41:49 +00:00
|
|
|
blocking_notifier_call_chain(&opp_table->head, OPP_EVENT_ADD, new_opp);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
return 0;
|
2014-12-10 04:15:35 +00:00
|
|
|
|
|
|
|
free_opp:
|
2017-01-02 09:11:01 +00:00
|
|
|
_opp_free(new_opp);
|
|
|
|
|
2014-12-10 04:15:35 +00:00
|
|
|
return ret;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
2014-11-25 10:34:18 +00:00
|
|
|
|
2023-09-27 10:58:37 +00:00
|
|
|
/*
|
2015-12-09 02:31:46 +00:00
|
|
|
* This is required only for the V2 bindings, and it enables a platform to
|
|
|
|
* specify the hierarchy of versions it supports. OPP layer will then enable
|
|
|
|
* OPPs, which are available for those versions, based on its 'opp-supported-hw'
|
|
|
|
* property.
|
|
|
|
*/
|
2022-05-26 04:06:27 +00:00
|
|
|
static int _opp_set_supported_hw(struct opp_table *opp_table,
|
|
|
|
const u32 *versions, unsigned int count)
|
2015-12-09 02:31:46 +00:00
|
|
|
{
|
2018-05-22 11:08:08 +00:00
|
|
|
/* Another CPU that shares the OPP table has set the property ? */
|
|
|
|
if (opp_table->supported_hw)
|
2022-05-26 04:06:27 +00:00
|
|
|
return 0;
|
2015-12-09 02:31:46 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_table->supported_hw = kmemdup(versions, count * sizeof(*versions),
|
2015-12-09 02:31:46 +00:00
|
|
|
GFP_KERNEL);
|
2022-05-26 04:06:27 +00:00
|
|
|
if (!opp_table->supported_hw)
|
|
|
|
return -ENOMEM;
|
2015-12-09 02:31:46 +00:00
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
opp_table->supported_hw_count = count;
|
2017-01-23 04:41:43 +00:00
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
return 0;
|
2015-12-09 02:31:46 +00:00
|
|
|
}
|
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
static void _opp_put_supported_hw(struct opp_table *opp_table)
|
2015-12-09 02:31:46 +00:00
|
|
|
{
|
2022-05-26 04:06:27 +00:00
|
|
|
if (opp_table->supported_hw) {
|
|
|
|
kfree(opp_table->supported_hw);
|
|
|
|
opp_table->supported_hw = NULL;
|
|
|
|
opp_table->supported_hw_count = 0;
|
|
|
|
}
|
2021-03-14 16:33:56 +00:00
|
|
|
}
|
|
|
|
|
2023-09-27 10:58:37 +00:00
|
|
|
/*
|
2015-12-09 02:31:47 +00:00
|
|
|
* This is required only for the V2 bindings, and it enables a platform to
|
|
|
|
* specify the extn to be used for certain property names. The properties to
|
|
|
|
* which the extension will apply are opp-microvolt and opp-microamp. OPP core
|
|
|
|
* should postfix the property name with -<name> while looking for them.
|
|
|
|
*/
|
2022-05-26 04:06:27 +00:00
|
|
|
static int _opp_set_prop_name(struct opp_table *opp_table, const char *name)
|
2015-12-09 02:31:47 +00:00
|
|
|
{
|
2018-05-22 11:08:08 +00:00
|
|
|
/* Another CPU that shares the OPP table has set the property ? */
|
2016-02-16 08:47:53 +00:00
|
|
|
if (!opp_table->prop_name) {
|
2022-05-26 04:06:27 +00:00
|
|
|
opp_table->prop_name = kstrdup(name, GFP_KERNEL);
|
|
|
|
if (!opp_table->prop_name)
|
|
|
|
return -ENOMEM;
|
2015-12-09 02:31:47 +00:00
|
|
|
}
|
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
return 0;
|
2015-12-09 02:31:47 +00:00
|
|
|
}
|
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
static void _opp_put_prop_name(struct opp_table *opp_table)
|
2015-12-09 02:31:47 +00:00
|
|
|
{
|
2022-05-26 04:06:27 +00:00
|
|
|
if (opp_table->prop_name) {
|
|
|
|
kfree(opp_table->prop_name);
|
|
|
|
opp_table->prop_name = NULL;
|
|
|
|
}
|
2015-12-09 02:31:47 +00:00
|
|
|
}
|
|
|
|
|
2023-09-27 10:58:37 +00:00
|
|
|
/*
|
2016-02-09 05:00:33 +00:00
|
|
|
* In order to support OPP switching, OPP layer needs to know the name of the
|
2016-12-01 10:58:19 +00:00
|
|
|
* device's regulators, as the core would be required to switch voltages as
|
|
|
|
* well.
|
2016-02-09 05:00:33 +00:00
|
|
|
*
|
|
|
|
* This must be called before any OPPs are initialized for the device.
|
|
|
|
*/
|
2022-07-04 11:06:26 +00:00
|
|
|
static int _opp_set_regulators(struct opp_table *opp_table, struct device *dev,
|
|
|
|
const char * const names[])
|
2016-02-09 05:00:33 +00:00
|
|
|
{
|
2022-07-04 10:40:39 +00:00
|
|
|
const char * const *temp = names;
|
2016-02-09 05:00:33 +00:00
|
|
|
struct regulator *reg;
|
2022-07-04 10:40:39 +00:00
|
|
|
int count = 0, ret, i;
|
|
|
|
|
|
|
|
/* Count number of regulators */
|
|
|
|
while (*temp++)
|
|
|
|
count++;
|
|
|
|
|
|
|
|
if (!count)
|
2022-07-04 11:06:26 +00:00
|
|
|
return -EINVAL;
|
2016-02-09 05:00:33 +00:00
|
|
|
|
2018-05-22 11:08:08 +00:00
|
|
|
/* Another CPU that shares the OPP table has set the regulators ? */
|
|
|
|
if (opp_table->regulators)
|
2022-07-04 11:06:26 +00:00
|
|
|
return 0;
|
2016-12-01 10:58:19 +00:00
|
|
|
|
|
|
|
opp_table->regulators = kmalloc_array(count,
|
|
|
|
sizeof(*opp_table->regulators),
|
|
|
|
GFP_KERNEL);
|
2022-07-04 11:06:26 +00:00
|
|
|
if (!opp_table->regulators)
|
|
|
|
return -ENOMEM;
|
2016-02-09 05:00:33 +00:00
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
for (i = 0; i < count; i++) {
|
|
|
|
reg = regulator_get_optional(dev, names[i]);
|
|
|
|
if (IS_ERR(reg)) {
|
2022-04-08 11:10:52 +00:00
|
|
|
ret = dev_err_probe(dev, PTR_ERR(reg),
|
|
|
|
"%s: no regulator (%s) found\n",
|
|
|
|
__func__, names[i]);
|
2016-12-01 10:58:19 +00:00
|
|
|
goto free_regulators;
|
|
|
|
}
|
|
|
|
|
|
|
|
opp_table->regulators[i] = reg;
|
|
|
|
}
|
|
|
|
|
|
|
|
opp_table->regulator_count = count;
|
2016-02-09 05:00:33 +00:00
|
|
|
|
2022-05-31 07:19:19 +00:00
|
|
|
/* Set generic config_regulators() for single regulators here */
|
|
|
|
if (count == 1)
|
|
|
|
opp_table->config_regulators = _opp_config_regulator_single;
|
|
|
|
|
2022-07-04 11:06:26 +00:00
|
|
|
return 0;
|
2016-02-09 05:00:33 +00:00
|
|
|
|
2016-12-01 10:58:19 +00:00
|
|
|
free_regulators:
|
2019-10-17 10:27:58 +00:00
|
|
|
while (i != 0)
|
|
|
|
regulator_put(opp_table->regulators[--i]);
|
2016-12-01 10:58:19 +00:00
|
|
|
|
|
|
|
kfree(opp_table->regulators);
|
|
|
|
opp_table->regulators = NULL;
|
2018-12-11 11:09:36 +00:00
|
|
|
opp_table->regulator_count = -1;
|
2016-02-09 05:00:33 +00:00
|
|
|
|
2022-07-04 11:06:26 +00:00
|
|
|
return ret;
|
2016-02-09 05:00:33 +00:00
|
|
|
}
|
|
|
|
|
2022-07-04 11:06:26 +00:00
|
|
|
static void _opp_put_regulators(struct opp_table *opp_table)
|
2016-02-09 05:00:33 +00:00
|
|
|
{
|
2016-12-01 10:58:19 +00:00
|
|
|
int i;
|
|
|
|
|
2018-05-22 11:08:08 +00:00
|
|
|
if (!opp_table->regulators)
|
2022-07-04 11:06:26 +00:00
|
|
|
return;
|
2016-02-09 05:00:33 +00:00
|
|
|
|
2020-08-13 03:08:37 +00:00
|
|
|
if (opp_table->enabled) {
|
2019-07-19 15:05:32 +00:00
|
|
|
for (i = opp_table->regulator_count - 1; i >= 0; i--)
|
|
|
|
regulator_disable(opp_table->regulators[i]);
|
|
|
|
}
|
|
|
|
|
2019-10-17 10:27:58 +00:00
|
|
|
for (i = opp_table->regulator_count - 1; i >= 0; i--)
|
2016-12-01 10:58:19 +00:00
|
|
|
regulator_put(opp_table->regulators[i]);
|
|
|
|
|
|
|
|
kfree(opp_table->regulators);
|
|
|
|
opp_table->regulators = NULL;
|
2018-12-11 11:09:36 +00:00
|
|
|
opp_table->regulator_count = -1;
|
2021-03-14 16:33:55 +00:00
|
|
|
}
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
static void _put_clks(struct opp_table *opp_table, int count)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = count - 1; i >= 0; i--)
|
|
|
|
clk_put(opp_table->clks[i]);
|
|
|
|
|
|
|
|
kfree(opp_table->clks);
|
|
|
|
opp_table->clks = NULL;
|
|
|
|
}
|
|
|
|
|
2023-09-27 10:58:37 +00:00
|
|
|
/*
|
2022-05-26 04:06:27 +00:00
|
|
|
* In order to support OPP switching, OPP layer needs to get pointers to the
|
|
|
|
* clocks for the device. Simple cases work fine without using this routine
|
|
|
|
* (i.e. by passing connection-id as NULL), but for a device with multiple
|
|
|
|
* clocks available, the OPP core needs to know the exact names of the clks to
|
|
|
|
* use.
|
2017-06-21 04:59:13 +00:00
|
|
|
*
|
|
|
|
* This must be called before any OPPs are initialized for the device.
|
|
|
|
*/
|
2022-05-26 04:06:27 +00:00
|
|
|
static int _opp_set_clknames(struct opp_table *opp_table, struct device *dev,
|
2022-06-10 06:32:04 +00:00
|
|
|
const char * const names[],
|
|
|
|
config_clks_t config_clks)
|
2017-06-21 04:59:13 +00:00
|
|
|
{
|
2022-05-26 04:06:27 +00:00
|
|
|
const char * const *temp = names;
|
2022-06-10 06:32:04 +00:00
|
|
|
int count = 0, ret, i;
|
|
|
|
struct clk *clk;
|
2017-06-21 04:59:13 +00:00
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
/* Count number of clks */
|
|
|
|
while (*temp++)
|
|
|
|
count++;
|
2017-06-21 04:59:13 +00:00
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
/*
|
|
|
|
* This is a special case where we have a single clock, whose connection
|
|
|
|
* id name is NULL, i.e. first two entries are NULL in the array.
|
|
|
|
*/
|
|
|
|
if (!count && !names[1])
|
|
|
|
count = 1;
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
/* Fail early for invalid configurations */
|
2022-07-04 15:37:28 +00:00
|
|
|
if (!count || (!config_clks && count > 1))
|
2022-05-26 04:06:27 +00:00
|
|
|
return -EINVAL;
|
2017-06-21 04:59:13 +00:00
|
|
|
|
2022-05-25 09:17:59 +00:00
|
|
|
/* Another CPU that shares the OPP table has set the clkname ? */
|
2022-06-10 06:32:04 +00:00
|
|
|
if (opp_table->clks)
|
2022-05-26 04:06:27 +00:00
|
|
|
return 0;
|
2022-05-25 09:17:59 +00:00
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
opp_table->clks = kmalloc_array(count, sizeof(*opp_table->clks),
|
|
|
|
GFP_KERNEL);
|
|
|
|
if (!opp_table->clks)
|
|
|
|
return -ENOMEM;
|
2017-06-21 04:59:13 +00:00
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
/* Find clks for the device */
|
|
|
|
for (i = 0; i < count; i++) {
|
|
|
|
clk = clk_get(dev, names[i]);
|
|
|
|
if (IS_ERR(clk)) {
|
|
|
|
ret = dev_err_probe(dev, PTR_ERR(clk),
|
|
|
|
"%s: Couldn't find clock with name: %s\n",
|
|
|
|
__func__, names[i]);
|
|
|
|
goto free_clks;
|
|
|
|
}
|
|
|
|
|
|
|
|
opp_table->clks[i] = clk;
|
2017-06-21 04:59:13 +00:00
|
|
|
}
|
|
|
|
|
2022-06-10 06:32:04 +00:00
|
|
|
opp_table->clk_count = count;
|
2022-07-04 15:37:28 +00:00
|
|
|
opp_table->config_clks = config_clks;
|
2022-06-10 06:32:04 +00:00
|
|
|
|
|
|
|
/* Set generic single clk set here */
|
|
|
|
if (count == 1) {
|
2022-07-04 15:37:28 +00:00
|
|
|
if (!opp_table->config_clks)
|
|
|
|
opp_table->config_clks = _opp_config_clk_single;
|
2022-06-10 06:32:04 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* We could have just dropped the "clk" field and used "clks"
|
|
|
|
* everywhere. Instead we kept the "clk" field around for
|
|
|
|
* following reasons:
|
|
|
|
*
|
|
|
|
* - avoiding clks[0] everywhere else.
|
|
|
|
* - not running single clk helpers for multiple clk usecase by
|
|
|
|
* mistake.
|
|
|
|
*
|
|
|
|
* Since this is single-clk case, just update the clk pointer
|
|
|
|
* too.
|
|
|
|
*/
|
|
|
|
opp_table->clk = opp_table->clks[0];
|
|
|
|
}
|
2022-05-25 09:17:59 +00:00
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
return 0;
|
2022-06-10 06:32:04 +00:00
|
|
|
|
|
|
|
free_clks:
|
|
|
|
_put_clks(opp_table, i);
|
|
|
|
return ret;
|
2021-03-14 16:33:54 +00:00
|
|
|
}
|
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
static void _opp_put_clknames(struct opp_table *opp_table)
|
2021-03-14 16:33:54 +00:00
|
|
|
{
|
2022-06-10 06:32:04 +00:00
|
|
|
if (!opp_table->clks)
|
|
|
|
return;
|
|
|
|
|
|
|
|
opp_table->config_clks = NULL;
|
|
|
|
opp_table->clk = ERR_PTR(-ENODEV);
|
|
|
|
|
|
|
|
_put_clks(opp_table, opp_table->clk_count);
|
2021-03-14 16:33:54 +00:00
|
|
|
}
|
|
|
|
|
2023-09-27 10:58:37 +00:00
|
|
|
/*
|
2022-07-04 08:15:08 +00:00
|
|
|
* This is useful to support platforms with multiple regulators per device.
|
|
|
|
*
|
|
|
|
* This must be called before any OPPs are initialized for the device.
|
|
|
|
*/
|
|
|
|
static int _opp_set_config_regulators_helper(struct opp_table *opp_table,
|
|
|
|
struct device *dev, config_regulators_t config_regulators)
|
|
|
|
{
|
|
|
|
/* Another CPU that shares the OPP table has set the helper ? */
|
|
|
|
if (!opp_table->config_regulators)
|
|
|
|
opp_table->config_regulators = config_regulators;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void _opp_put_config_regulators_helper(struct opp_table *opp_table)
|
|
|
|
{
|
|
|
|
if (opp_table->config_regulators)
|
|
|
|
opp_table->config_regulators = NULL;
|
|
|
|
}
|
|
|
|
|
2023-10-12 06:20:59 +00:00
|
|
|
static void _opp_detach_genpd(struct opp_table *opp_table)
|
2019-05-08 09:49:13 +00:00
|
|
|
{
|
|
|
|
int index;
|
|
|
|
|
2020-08-31 05:52:37 +00:00
|
|
|
if (!opp_table->genpd_virt_devs)
|
|
|
|
return;
|
|
|
|
|
2019-05-08 09:49:13 +00:00
|
|
|
for (index = 0; index < opp_table->required_opp_count; index++) {
|
|
|
|
if (!opp_table->genpd_virt_devs[index])
|
|
|
|
continue;
|
|
|
|
|
|
|
|
dev_pm_domain_detach(opp_table->genpd_virt_devs[index], false);
|
|
|
|
opp_table->genpd_virt_devs[index] = NULL;
|
|
|
|
}
|
2019-05-08 10:13:36 +00:00
|
|
|
|
|
|
|
kfree(opp_table->genpd_virt_devs);
|
|
|
|
opp_table->genpd_virt_devs = NULL;
|
2019-05-08 09:49:13 +00:00
|
|
|
}
|
|
|
|
|
2023-09-27 10:58:37 +00:00
|
|
|
/*
|
2018-06-26 10:59:34 +00:00
|
|
|
* Multiple generic power domains for a device are supported with the help of
|
|
|
|
* virtual genpd devices, which are created for each consumer device - genpd
|
|
|
|
* pair. These are the device structures which are attached to the power domain
|
|
|
|
* and are required by the OPP core to set the performance state of the genpd.
|
2019-05-08 09:49:13 +00:00
|
|
|
* The same API also works for the case where single genpd is available and so
|
|
|
|
* we don't need to support that separately.
|
2018-06-26 10:59:34 +00:00
|
|
|
*
|
|
|
|
* This helper will normally be called by the consumer driver of the device
|
2019-05-08 09:49:13 +00:00
|
|
|
* "dev", as only that has details of the genpd names.
|
2018-06-26 10:59:34 +00:00
|
|
|
*
|
2019-05-08 09:49:13 +00:00
|
|
|
* This helper needs to be called once with a list of all genpd to attach.
|
|
|
|
* Otherwise the original device structure will be used instead by the OPP core.
|
2019-07-17 05:50:17 +00:00
|
|
|
*
|
|
|
|
* The order of entries in the names array must match the order in which
|
|
|
|
* "required-opps" are added in DT.
|
2018-06-26 10:59:34 +00:00
|
|
|
*/
|
2022-05-26 04:06:27 +00:00
|
|
|
static int _opp_attach_genpd(struct opp_table *opp_table, struct device *dev,
|
|
|
|
const char * const *names, struct device ***virt_devs)
|
2018-06-26 10:59:34 +00:00
|
|
|
{
|
2019-05-08 09:49:13 +00:00
|
|
|
struct device *virt_dev;
|
2019-07-17 05:50:17 +00:00
|
|
|
int index = 0, ret = -EINVAL;
|
2021-09-26 22:40:24 +00:00
|
|
|
const char * const *name = names;
|
2018-06-26 10:59:34 +00:00
|
|
|
|
2020-08-31 05:52:37 +00:00
|
|
|
if (opp_table->genpd_virt_devs)
|
2022-05-26 04:06:27 +00:00
|
|
|
return 0;
|
2018-06-26 10:59:34 +00:00
|
|
|
|
2019-05-08 10:13:36 +00:00
|
|
|
opp_table->genpd_virt_devs = kcalloc(opp_table->required_opp_count,
|
|
|
|
sizeof(*opp_table->genpd_virt_devs),
|
|
|
|
GFP_KERNEL);
|
|
|
|
if (!opp_table->genpd_virt_devs)
|
2023-10-12 06:20:59 +00:00
|
|
|
return -ENOMEM;
|
2018-06-26 10:59:34 +00:00
|
|
|
|
2019-05-08 09:49:13 +00:00
|
|
|
while (*name) {
|
|
|
|
if (index >= opp_table->required_opp_count) {
|
|
|
|
dev_err(dev, "Index can't be greater than required-opp-count - 1, %s (%d : %d)\n",
|
|
|
|
*name, opp_table->required_opp_count, index);
|
|
|
|
goto err;
|
|
|
|
}
|
2018-06-26 10:59:34 +00:00
|
|
|
|
2019-05-08 09:49:13 +00:00
|
|
|
virt_dev = dev_pm_domain_attach_by_name(dev, *name);
|
2022-05-24 12:31:51 +00:00
|
|
|
if (IS_ERR_OR_NULL(virt_dev)) {
|
2023-07-21 12:46:34 +00:00
|
|
|
ret = virt_dev ? PTR_ERR(virt_dev) : -ENODEV;
|
2019-05-08 09:49:13 +00:00
|
|
|
dev_err(dev, "Couldn't attach to pm_domain: %d\n", ret);
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
|
|
|
opp_table->genpd_virt_devs[index] = virt_dev;
|
2019-07-17 05:50:17 +00:00
|
|
|
index++;
|
2019-05-08 09:49:13 +00:00
|
|
|
name++;
|
2018-06-26 10:59:34 +00:00
|
|
|
}
|
|
|
|
|
2019-07-08 05:54:56 +00:00
|
|
|
if (virt_devs)
|
|
|
|
*virt_devs = opp_table->genpd_virt_devs;
|
2018-06-26 10:59:34 +00:00
|
|
|
|
2022-05-26 04:06:27 +00:00
|
|
|
return 0;
|
2019-05-08 09:49:13 +00:00
|
|
|
|
|
|
|
err:
|
2023-10-12 06:20:59 +00:00
|
|
|
_opp_detach_genpd(opp_table);
|
2022-05-26 04:06:27 +00:00
|
|
|
return ret;
|
2019-05-08 09:49:13 +00:00
|
|
|
|
2018-06-26 10:59:34 +00:00
|
|
|
}
|
|
|
|
|
2022-05-25 09:53:16 +00:00
|
|
|
static void _opp_clear_config(struct opp_config_data *data)
|
|
|
|
{
|
|
|
|
if (data->flags & OPP_CONFIG_GENPD)
|
2022-05-26 04:06:27 +00:00
|
|
|
_opp_detach_genpd(data->opp_table);
|
2022-05-25 09:53:16 +00:00
|
|
|
if (data->flags & OPP_CONFIG_REGULATOR)
|
2022-07-04 11:06:26 +00:00
|
|
|
_opp_put_regulators(data->opp_table);
|
2022-05-25 09:53:16 +00:00
|
|
|
if (data->flags & OPP_CONFIG_SUPPORTED_HW)
|
2022-05-26 04:06:27 +00:00
|
|
|
_opp_put_supported_hw(data->opp_table);
|
2022-07-04 09:27:06 +00:00
|
|
|
if (data->flags & OPP_CONFIG_REGULATOR_HELPER)
|
2022-07-04 08:15:08 +00:00
|
|
|
_opp_put_config_regulators_helper(data->opp_table);
|
2022-05-25 09:53:16 +00:00
|
|
|
if (data->flags & OPP_CONFIG_PROP_NAME)
|
2022-05-26 04:06:27 +00:00
|
|
|
_opp_put_prop_name(data->opp_table);
|
2022-05-25 09:53:16 +00:00
|
|
|
if (data->flags & OPP_CONFIG_CLK)
|
2022-05-26 04:06:27 +00:00
|
|
|
_opp_put_clknames(data->opp_table);
|
2022-05-25 09:53:16 +00:00
|
|
|
|
|
|
|
dev_pm_opp_put_opp_table(data->opp_table);
|
|
|
|
kfree(data);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dev_pm_opp_set_config() - Set OPP configuration for the device.
|
|
|
|
* @dev: Device for which configuration is being set.
|
|
|
|
* @config: OPP configuration.
|
|
|
|
*
|
|
|
|
* This allows all device OPP configurations to be performed at once.
|
|
|
|
*
|
|
|
|
* This must be called before any OPPs are initialized for the device. This may
|
|
|
|
* be called multiple times for the same OPP table, for example once for each
|
|
|
|
* CPU that share the same table. This must be balanced by the same number of
|
|
|
|
* calls to dev_pm_opp_clear_config() in order to free the OPP table properly.
|
|
|
|
*
|
|
|
|
* This returns a token to the caller, which must be passed to
|
|
|
|
* dev_pm_opp_clear_config() to free the resources later. The value of the
|
|
|
|
* returned token will be >= 1 for success and negative for errors. The minimum
|
|
|
|
* value of 1 is chosen here to make it easy for callers to manage the resource.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_set_config(struct device *dev, struct dev_pm_opp_config *config)
|
|
|
|
{
|
2022-05-26 04:06:27 +00:00
|
|
|
struct opp_table *opp_table;
|
2022-05-25 09:53:16 +00:00
|
|
|
struct opp_config_data *data;
|
|
|
|
unsigned int id;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
data = kmalloc(sizeof(*data), GFP_KERNEL);
|
|
|
|
if (!data)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
opp_table = _add_opp_table(dev, false);
|
|
|
|
if (IS_ERR(opp_table)) {
|
|
|
|
kfree(data);
|
|
|
|
return PTR_ERR(opp_table);
|
|
|
|
}
|
|
|
|
|
|
|
|
data->opp_table = opp_table;
|
|
|
|
data->flags = 0;
|
|
|
|
|
|
|
|
/* This should be called before OPPs are initialized */
|
|
|
|
if (WARN_ON(!list_empty(&opp_table->opp_list))) {
|
|
|
|
ret = -EBUSY;
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Configure clocks */
|
|
|
|
if (config->clk_names) {
|
2022-06-10 06:32:04 +00:00
|
|
|
ret = _opp_set_clknames(opp_table, dev, config->clk_names,
|
|
|
|
config->config_clks);
|
2022-05-26 04:06:27 +00:00
|
|
|
if (ret)
|
2022-05-25 09:53:16 +00:00
|
|
|
goto err;
|
|
|
|
|
|
|
|
data->flags |= OPP_CONFIG_CLK;
|
2022-06-10 06:32:04 +00:00
|
|
|
} else if (config->config_clks) {
|
|
|
|
/* Don't allow config callback without clocks */
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto err;
|
2022-05-25 09:53:16 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Configure property names */
|
|
|
|
if (config->prop_name) {
|
2022-05-26 04:06:27 +00:00
|
|
|
ret = _opp_set_prop_name(opp_table, config->prop_name);
|
|
|
|
if (ret)
|
2022-05-25 09:53:16 +00:00
|
|
|
goto err;
|
|
|
|
|
|
|
|
data->flags |= OPP_CONFIG_PROP_NAME;
|
|
|
|
}
|
|
|
|
|
2022-07-04 08:15:08 +00:00
|
|
|
/* Configure config_regulators helper */
|
|
|
|
if (config->config_regulators) {
|
|
|
|
ret = _opp_set_config_regulators_helper(opp_table, dev,
|
|
|
|
config->config_regulators);
|
|
|
|
if (ret)
|
|
|
|
goto err;
|
|
|
|
|
|
|
|
data->flags |= OPP_CONFIG_REGULATOR_HELPER;
|
|
|
|
}
|
|
|
|
|
2022-05-25 09:53:16 +00:00
|
|
|
/* Configure supported hardware */
|
|
|
|
if (config->supported_hw) {
|
2022-05-26 04:06:27 +00:00
|
|
|
ret = _opp_set_supported_hw(opp_table, config->supported_hw,
|
|
|
|
config->supported_hw_count);
|
|
|
|
if (ret)
|
2022-05-25 09:53:16 +00:00
|
|
|
goto err;
|
|
|
|
|
|
|
|
data->flags |= OPP_CONFIG_SUPPORTED_HW;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Configure supplies */
|
|
|
|
if (config->regulator_names) {
|
2022-07-04 11:06:26 +00:00
|
|
|
ret = _opp_set_regulators(opp_table, dev,
|
|
|
|
config->regulator_names);
|
|
|
|
if (ret)
|
2022-05-25 09:53:16 +00:00
|
|
|
goto err;
|
|
|
|
|
|
|
|
data->flags |= OPP_CONFIG_REGULATOR;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Attach genpds */
|
|
|
|
if (config->genpd_names) {
|
2022-05-26 04:06:27 +00:00
|
|
|
ret = _opp_attach_genpd(opp_table, dev, config->genpd_names,
|
|
|
|
config->virt_devs);
|
|
|
|
if (ret)
|
2022-05-25 09:53:16 +00:00
|
|
|
goto err;
|
|
|
|
|
|
|
|
data->flags |= OPP_CONFIG_GENPD;
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = xa_alloc(&opp_configs, &id, data, XA_LIMIT(1, INT_MAX),
|
|
|
|
GFP_KERNEL);
|
|
|
|
if (ret)
|
|
|
|
goto err;
|
|
|
|
|
|
|
|
return id;
|
|
|
|
|
|
|
|
err:
|
|
|
|
_opp_clear_config(data);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_set_config);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dev_pm_opp_clear_config() - Releases resources blocked for OPP configuration.
|
2023-09-27 10:58:37 +00:00
|
|
|
* @token: The token returned by dev_pm_opp_set_config() previously.
|
2022-05-25 09:53:16 +00:00
|
|
|
*
|
|
|
|
* This allows all device OPP configurations to be cleared at once. This must be
|
|
|
|
* called once for each call made to dev_pm_opp_set_config(), in order to free
|
|
|
|
* the OPPs properly.
|
|
|
|
*
|
|
|
|
* Currently the first call itself ends up freeing all the OPP configurations,
|
|
|
|
* while the later ones only drop the OPP table reference. This works well for
|
|
|
|
* now as we would never want to use an half initialized OPP table and want to
|
|
|
|
* remove the configurations together.
|
|
|
|
*/
|
|
|
|
void dev_pm_opp_clear_config(int token)
|
|
|
|
{
|
|
|
|
struct opp_config_data *data;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This lets the callers call this unconditionally and keep their code
|
|
|
|
* simple.
|
|
|
|
*/
|
|
|
|
if (unlikely(token <= 0))
|
|
|
|
return;
|
|
|
|
|
|
|
|
data = xa_erase(&opp_configs, token);
|
|
|
|
if (WARN_ON(!data))
|
|
|
|
return;
|
|
|
|
|
|
|
|
_opp_clear_config(data);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_clear_config);
|
|
|
|
|
|
|
|
static void devm_pm_opp_config_release(void *token)
|
|
|
|
{
|
|
|
|
dev_pm_opp_clear_config((unsigned long)token);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* devm_pm_opp_set_config() - Set OPP configuration for the device.
|
|
|
|
* @dev: Device for which configuration is being set.
|
|
|
|
* @config: OPP configuration.
|
|
|
|
*
|
|
|
|
* This allows all device OPP configurations to be performed at once.
|
|
|
|
* This is a resource-managed variant of dev_pm_opp_set_config().
|
|
|
|
*
|
|
|
|
* Return: 0 on success and errorno otherwise.
|
|
|
|
*/
|
|
|
|
int devm_pm_opp_set_config(struct device *dev, struct dev_pm_opp_config *config)
|
|
|
|
{
|
|
|
|
int token = dev_pm_opp_set_config(dev, config);
|
|
|
|
|
|
|
|
if (token < 0)
|
|
|
|
return token;
|
|
|
|
|
|
|
|
return devm_add_action_or_reset(dev, devm_pm_opp_config_release,
|
|
|
|
(void *) ((unsigned long) token));
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(devm_pm_opp_set_config);
|
|
|
|
|
2021-02-04 08:14:22 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_xlate_required_opp() - Find required OPP for @src_table OPP.
|
|
|
|
* @src_table: OPP table which has @dst_table as one of its required OPP table.
|
|
|
|
* @dst_table: Required OPP table of the @src_table.
|
|
|
|
* @src_opp: OPP from the @src_table.
|
|
|
|
*
|
|
|
|
* This function returns the OPP (present in @dst_table) pointed out by the
|
|
|
|
* "required-opps" property of the @src_opp (present in @src_table).
|
|
|
|
*
|
|
|
|
* The callers are required to call dev_pm_opp_put() for the returned OPP after
|
|
|
|
* use.
|
|
|
|
*
|
|
|
|
* Return: pointer to 'struct dev_pm_opp' on success and errorno otherwise.
|
|
|
|
*/
|
|
|
|
struct dev_pm_opp *dev_pm_opp_xlate_required_opp(struct opp_table *src_table,
|
|
|
|
struct opp_table *dst_table,
|
|
|
|
struct dev_pm_opp *src_opp)
|
|
|
|
{
|
|
|
|
struct dev_pm_opp *opp, *dest_opp = ERR_PTR(-ENODEV);
|
|
|
|
int i;
|
|
|
|
|
|
|
|
if (!src_table || !dst_table || !src_opp ||
|
|
|
|
!src_table->required_opp_tables)
|
|
|
|
return ERR_PTR(-EINVAL);
|
|
|
|
|
|
|
|
/* required-opps not fully initialized yet */
|
|
|
|
if (lazy_linking_pending(src_table))
|
|
|
|
return ERR_PTR(-EBUSY);
|
|
|
|
|
|
|
|
for (i = 0; i < src_table->required_opp_count; i++) {
|
|
|
|
if (src_table->required_opp_tables[i] == dst_table) {
|
|
|
|
mutex_lock(&src_table->lock);
|
|
|
|
|
|
|
|
list_for_each_entry(opp, &src_table->opp_list, node) {
|
|
|
|
if (opp == src_opp) {
|
|
|
|
dest_opp = opp->required_opps[i];
|
|
|
|
dev_pm_opp_get(dest_opp);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
mutex_unlock(&src_table->lock);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (IS_ERR(dest_opp)) {
|
|
|
|
pr_err("%s: Couldn't find matching OPP (%p: %p)\n", __func__,
|
|
|
|
src_table, dst_table);
|
|
|
|
}
|
|
|
|
|
|
|
|
return dest_opp;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_xlate_required_opp);
|
|
|
|
|
2018-11-02 09:06:42 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_xlate_performance_state() - Find required OPP's pstate for src_table.
|
|
|
|
* @src_table: OPP table which has dst_table as one of its required OPP table.
|
|
|
|
* @dst_table: Required OPP table of the src_table.
|
|
|
|
* @pstate: Current performance state of the src_table.
|
|
|
|
*
|
|
|
|
* This Returns pstate of the OPP (present in @dst_table) pointed out by the
|
|
|
|
* "required-opps" property of the OPP (present in @src_table) which has
|
|
|
|
* performance state set to @pstate.
|
|
|
|
*
|
|
|
|
* Return: Zero or positive performance state on success, otherwise negative
|
|
|
|
* value on errors.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_xlate_performance_state(struct opp_table *src_table,
|
|
|
|
struct opp_table *dst_table,
|
|
|
|
unsigned int pstate)
|
|
|
|
{
|
|
|
|
struct dev_pm_opp *opp;
|
|
|
|
int dest_pstate = -EINVAL;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Normally the src_table will have the "required_opps" property set to
|
|
|
|
* point to one of the OPPs in the dst_table, but in some cases the
|
|
|
|
* genpd and its master have one to one mapping of performance states
|
|
|
|
* and so none of them have the "required-opps" property set. Return the
|
|
|
|
* pstate of the src_table as it is in such cases.
|
|
|
|
*/
|
2021-01-18 00:55:23 +00:00
|
|
|
if (!src_table || !src_table->required_opp_count)
|
2018-11-02 09:06:42 +00:00
|
|
|
return pstate;
|
|
|
|
|
2023-06-14 10:27:43 +00:00
|
|
|
/* Both OPP tables must belong to genpds */
|
|
|
|
if (unlikely(!src_table->is_genpd || !dst_table->is_genpd)) {
|
|
|
|
pr_err("%s: Performance state is only valid for genpds.\n", __func__);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2019-11-25 08:27:58 +00:00
|
|
|
/* required-opps not fully initialized yet */
|
|
|
|
if (lazy_linking_pending(src_table))
|
|
|
|
return -EBUSY;
|
|
|
|
|
2018-11-02 09:06:42 +00:00
|
|
|
for (i = 0; i < src_table->required_opp_count; i++) {
|
|
|
|
if (src_table->required_opp_tables[i]->np == dst_table->np)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (unlikely(i == src_table->required_opp_count)) {
|
|
|
|
pr_err("%s: Couldn't find matching OPP table (%p: %p)\n",
|
|
|
|
__func__, src_table, dst_table);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
mutex_lock(&src_table->lock);
|
|
|
|
|
|
|
|
list_for_each_entry(opp, &src_table->opp_list, node) {
|
2023-06-14 09:59:32 +00:00
|
|
|
if (opp->level == pstate) {
|
|
|
|
dest_pstate = opp->required_opps[i]->level;
|
2018-11-02 09:06:42 +00:00
|
|
|
goto unlock;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
pr_err("%s: Couldn't find matching OPP (%p: %p)\n", __func__, src_table,
|
|
|
|
dst_table);
|
|
|
|
|
|
|
|
unlock:
|
|
|
|
mutex_unlock(&src_table->lock);
|
|
|
|
|
|
|
|
return dest_pstate;
|
|
|
|
}
|
|
|
|
|
2014-11-25 10:34:18 +00:00
|
|
|
/**
|
2023-09-25 13:17:09 +00:00
|
|
|
* dev_pm_opp_add_dynamic() - Add an OPP table from a table definitions
|
|
|
|
* @dev: The device for which we do this operation
|
|
|
|
* @data: The OPP data for the OPP to add
|
2014-11-25 10:34:18 +00:00
|
|
|
*
|
2016-02-16 08:47:53 +00:00
|
|
|
* This function adds an opp definition to the opp table and returns status.
|
2014-11-25 10:34:18 +00:00
|
|
|
* The opp is made available by default and it can be controlled using
|
|
|
|
* dev_pm_opp_enable/disable functions.
|
|
|
|
*
|
|
|
|
* Return:
|
2014-12-24 17:22:57 +00:00
|
|
|
* 0 On success OR
|
2014-11-25 10:34:18 +00:00
|
|
|
* Duplicate OPPs (both freq and volt are same) and opp->available
|
2014-12-24 17:22:57 +00:00
|
|
|
* -EEXIST Freq are same and volt are different OR
|
2014-11-25 10:34:18 +00:00
|
|
|
* Duplicate OPPs (both freq and volt are same) and !opp->available
|
2014-12-24 17:22:57 +00:00
|
|
|
* -ENOMEM Memory allocation failure
|
2014-11-25 10:34:18 +00:00
|
|
|
*/
|
2023-09-25 13:17:09 +00:00
|
|
|
int dev_pm_opp_add_dynamic(struct device *dev, struct dev_pm_opp_data *data)
|
2014-11-25 10:34:18 +00:00
|
|
|
{
|
2017-01-02 09:11:01 +00:00
|
|
|
struct opp_table *opp_table;
|
|
|
|
int ret;
|
|
|
|
|
2021-01-28 06:35:22 +00:00
|
|
|
opp_table = _add_opp_table(dev, true);
|
opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER
The OPP core manages various resources, e.g. clocks or interconnect paths.
These resources are looked up when the OPP table is allocated once
dev_pm_opp_get_opp_table() is called the first time (either directly
or indirectly through one of the many helper functions).
At this point, the resources may not be available yet, i.e. looking them
up will result in -EPROBE_DEFER. Unfortunately, dev_pm_opp_get_opp_table()
is currently unable to propagate this error code since it only returns
the allocated OPP table or NULL.
This means that all consumers of the OPP core are required to make sure
that all necessary resources are available. Usually this happens by
requesting them, checking the result and releasing them immediately after.
For example, we have added "dev_pm_opp_of_find_icc_paths(dev, NULL)" to
several drivers now just to make sure the interconnect providers are
ready before the OPP table is allocated. If this call is missing,
the OPP core will only warn about this and then attempt to continue
without interconnect. This will eventually fail horribly, e.g.:
cpu cpu0: _allocate_opp_table: Error finding interconnect paths: -517
... later ...
of: _read_bw: Mismatch between opp-peak-kBps and paths (1 0)
cpu cpu0: _opp_add_static_v2: opp key field not found
cpu cpu0: _of_add_opp_table_v2: Failed to add OPP, -22
This example happens when trying to use interconnects for a CPU OPP
table together with qcom-cpufreq-nvmem.c. qcom-cpufreq-nvmem calls
dev_pm_opp_set_supported_hw(), which ends up allocating the OPP table
early. To fix the problem with the current approach we would need to add
yet another call to dev_pm_opp_of_find_icc_paths(dev, NULL).
But actually qcom-cpufreq-nvmem.c has nothing to do with interconnects...
This commit attempts to make this more robust by allowing
dev_pm_opp_get_opp_table() to return an error pointer. Fixing all
the usages is trivial because the function is usually used indirectly
through another helper (e.g. dev_pm_opp_set_supported_hw() above).
These other helpers already return an error pointer.
The example above then works correctly because set_supported_hw() will
return -EPROBE_DEFER, and qcom-cpufreq-nvmem.c already propagates that
error. It should also be possible to remove the remaining usages of
"dev_pm_opp_of_find_icc_paths(dev, NULL)" from other drivers as well.
Note that this commit currently only handles -EPROBE_DEFER for the
clock/interconnects within _allocate_opp_table(). Other errors are just
ignored as before. Eventually those should be propagated as well.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
[ Viresh: skip checking return value of dev_pm_opp_get_opp_table() for
EPROBE_DEFER in domain.c, fix NULL return value and reorder
code a bit in core.c, and update exynos-asv.c ]
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
2020-07-27 09:30:46 +00:00
|
|
|
if (IS_ERR(opp_table))
|
|
|
|
return PTR_ERR(opp_table);
|
2017-01-02 09:11:01 +00:00
|
|
|
|
2018-12-11 11:09:36 +00:00
|
|
|
/* Fix regulator count for dynamic OPPs */
|
|
|
|
opp_table->regulator_count = 1;
|
|
|
|
|
2023-09-25 13:17:09 +00:00
|
|
|
ret = _opp_add_v1(opp_table, dev, data, true);
|
2018-08-02 08:53:09 +00:00
|
|
|
if (ret)
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2017-01-02 09:11:01 +00:00
|
|
|
|
|
|
|
return ret;
|
2014-11-25 10:34:18 +00:00
|
|
|
}
|
2023-09-25 13:17:09 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_add_dynamic);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
|
|
|
/**
|
2014-12-24 17:22:56 +00:00
|
|
|
* _opp_set_availability() - helper to set the availability of an opp
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @freq: OPP frequency to modify availability
|
|
|
|
* @availability_req: availability status requested for this opp
|
|
|
|
*
|
2017-01-23 04:41:49 +00:00
|
|
|
* Set the availability of an OPP, opp_{enable,disable} share a common logic
|
|
|
|
* which is isolated here.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
2014-12-24 17:22:57 +00:00
|
|
|
* Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
|
2015-09-24 19:28:44 +00:00
|
|
|
* copy operation, returns 0 if no modification was done OR modification was
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* successful.
|
|
|
|
*/
|
2014-12-24 17:22:56 +00:00
|
|
|
static int _opp_set_availability(struct device *dev, unsigned long freq,
|
|
|
|
bool availability_req)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2016-02-16 08:47:53 +00:00
|
|
|
struct opp_table *opp_table;
|
2017-01-23 04:41:50 +00:00
|
|
|
struct dev_pm_opp *tmp_opp, *opp = ERR_PTR(-ENODEV);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
int r = 0;
|
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
/* Find the opp_table */
|
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table)) {
|
|
|
|
r = PTR_ERR(opp_table);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
dev_warn(dev, "%s: Device OPP not found (%d)\n", __func__, r);
|
2017-01-23 04:41:50 +00:00
|
|
|
return r;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
|
|
|
|
2022-06-10 04:57:51 +00:00
|
|
|
if (!assert_single_clk(opp_table)) {
|
|
|
|
r = -EINVAL;
|
|
|
|
goto put_table;
|
|
|
|
}
|
|
|
|
|
2017-01-23 04:41:41 +00:00
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/* Do we have the frequency? */
|
2016-02-16 08:47:53 +00:00
|
|
|
list_for_each_entry(tmp_opp, &opp_table->opp_list, node) {
|
2022-06-10 06:32:04 +00:00
|
|
|
if (tmp_opp->rates[0] == freq) {
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
opp = tmp_opp;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2017-01-23 04:41:41 +00:00
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
if (IS_ERR(opp)) {
|
|
|
|
r = PTR_ERR(opp);
|
|
|
|
goto unlock;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Is update really needed? */
|
|
|
|
if (opp->available == availability_req)
|
|
|
|
goto unlock;
|
|
|
|
|
2017-01-23 04:41:50 +00:00
|
|
|
opp->available = availability_req;
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2017-09-21 17:44:36 +00:00
|
|
|
dev_pm_opp_get(opp);
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
|
2011-09-30 20:35:12 +00:00
|
|
|
/* Notify the change of the OPP availability */
|
|
|
|
if (availability_req)
|
2017-01-23 04:41:49 +00:00
|
|
|
blocking_notifier_call_chain(&opp_table->head, OPP_EVENT_ENABLE,
|
2017-01-23 04:41:50 +00:00
|
|
|
opp);
|
2011-09-30 20:35:12 +00:00
|
|
|
else
|
2017-01-23 04:41:49 +00:00
|
|
|
blocking_notifier_call_chain(&opp_table->head,
|
2017-01-23 04:41:50 +00:00
|
|
|
OPP_EVENT_DISABLE, opp);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2017-09-21 17:44:36 +00:00
|
|
|
dev_pm_opp_put(opp);
|
|
|
|
goto put_table;
|
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
unlock:
|
2017-01-23 04:41:48 +00:00
|
|
|
mutex_unlock(&opp_table->lock);
|
2017-09-21 17:44:36 +00:00
|
|
|
put_table:
|
2017-01-23 04:41:48 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
return r;
|
|
|
|
}
|
|
|
|
|
2019-10-16 14:57:53 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_adjust_voltage() - helper to change the voltage of an OPP
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @freq: OPP frequency to adjust voltage of
|
|
|
|
* @u_volt: new OPP target voltage
|
|
|
|
* @u_volt_min: new OPP min voltage
|
|
|
|
* @u_volt_max: new OPP max voltage
|
|
|
|
*
|
|
|
|
* Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
|
|
|
|
* copy operation, returns 0 if no modifcation was done OR modification was
|
|
|
|
* successful.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_adjust_voltage(struct device *dev, unsigned long freq,
|
|
|
|
unsigned long u_volt, unsigned long u_volt_min,
|
|
|
|
unsigned long u_volt_max)
|
|
|
|
|
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
struct dev_pm_opp *tmp_opp, *opp = ERR_PTR(-ENODEV);
|
|
|
|
int r = 0;
|
|
|
|
|
|
|
|
/* Find the opp_table */
|
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table)) {
|
|
|
|
r = PTR_ERR(opp_table);
|
|
|
|
dev_warn(dev, "%s: Device OPP not found (%d)\n", __func__, r);
|
|
|
|
return r;
|
|
|
|
}
|
|
|
|
|
2022-06-10 04:57:51 +00:00
|
|
|
if (!assert_single_clk(opp_table)) {
|
|
|
|
r = -EINVAL;
|
|
|
|
goto put_table;
|
|
|
|
}
|
|
|
|
|
2019-10-16 14:57:53 +00:00
|
|
|
mutex_lock(&opp_table->lock);
|
|
|
|
|
|
|
|
/* Do we have the frequency? */
|
|
|
|
list_for_each_entry(tmp_opp, &opp_table->opp_list, node) {
|
2022-06-10 06:32:04 +00:00
|
|
|
if (tmp_opp->rates[0] == freq) {
|
2019-10-16 14:57:53 +00:00
|
|
|
opp = tmp_opp;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (IS_ERR(opp)) {
|
|
|
|
r = PTR_ERR(opp);
|
|
|
|
goto adjust_unlock;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Is update really needed? */
|
|
|
|
if (opp->supplies->u_volt == u_volt)
|
|
|
|
goto adjust_unlock;
|
|
|
|
|
|
|
|
opp->supplies->u_volt = u_volt;
|
|
|
|
opp->supplies->u_volt_min = u_volt_min;
|
|
|
|
opp->supplies->u_volt_max = u_volt_max;
|
|
|
|
|
|
|
|
dev_pm_opp_get(opp);
|
|
|
|
mutex_unlock(&opp_table->lock);
|
|
|
|
|
|
|
|
/* Notify the voltage change of the OPP */
|
|
|
|
blocking_notifier_call_chain(&opp_table->head, OPP_EVENT_ADJUST_VOLTAGE,
|
|
|
|
opp);
|
|
|
|
|
|
|
|
dev_pm_opp_put(opp);
|
2022-06-10 04:57:51 +00:00
|
|
|
goto put_table;
|
2019-10-16 14:57:53 +00:00
|
|
|
|
|
|
|
adjust_unlock:
|
|
|
|
mutex_unlock(&opp_table->lock);
|
2022-06-10 04:57:51 +00:00
|
|
|
put_table:
|
2019-10-16 14:57:53 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
|
|
|
return r;
|
|
|
|
}
|
2020-06-20 17:03:22 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_adjust_voltage);
|
2019-10-16 14:57:53 +00:00
|
|
|
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
/**
|
2013-09-19 21:03:50 +00:00
|
|
|
* dev_pm_opp_enable() - Enable a specific OPP
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @freq: OPP frequency to enable
|
|
|
|
*
|
|
|
|
* Enables a provided opp. If the operation is valid, this returns 0, else the
|
|
|
|
* corresponding error value. It is meant to be used for users an OPP available
|
2013-09-19 21:03:50 +00:00
|
|
|
* after being temporarily made unavailable with dev_pm_opp_disable.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
2014-12-24 17:22:57 +00:00
|
|
|
* Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
|
2015-09-24 19:28:44 +00:00
|
|
|
* copy operation, returns 0 if no modification was done OR modification was
|
2014-12-24 17:22:57 +00:00
|
|
|
* successful.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*/
|
2013-09-19 21:03:50 +00:00
|
|
|
int dev_pm_opp_enable(struct device *dev, unsigned long freq)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2014-12-24 17:22:56 +00:00
|
|
|
return _opp_set_availability(dev, freq, true);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
2013-09-19 21:03:50 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_enable);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
|
|
|
/**
|
2013-09-19 21:03:50 +00:00
|
|
|
* dev_pm_opp_disable() - Disable a specific OPP
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
* @dev: device for which we do this operation
|
|
|
|
* @freq: OPP frequency to disable
|
|
|
|
*
|
|
|
|
* Disables a provided opp. If the operation is valid, this returns
|
|
|
|
* 0, else the corresponding error value. It is meant to be a temporary
|
|
|
|
* control by users to make this OPP not available until the circumstances are
|
2013-09-19 21:03:50 +00:00
|
|
|
* right to make it available again (with a call to dev_pm_opp_enable).
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*
|
2014-12-24 17:22:57 +00:00
|
|
|
* Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
|
2015-09-24 19:28:44 +00:00
|
|
|
* copy operation, returns 0 if no modification was done OR modification was
|
2014-12-24 17:22:57 +00:00
|
|
|
* successful.
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
*/
|
2013-09-19 21:03:50 +00:00
|
|
|
int dev_pm_opp_disable(struct device *dev, unsigned long freq)
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
{
|
2014-12-24 17:22:56 +00:00
|
|
|
return _opp_set_availability(dev, freq, false);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
}
|
2013-09-19 21:03:50 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_disable);
|
PM: Introduce library for device-specific OPPs (v7)
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. The actual
definitions of OPP varies over silicon versions. For a specific domain,
we can have a set of {frequency, voltage} pairs. As the kernel boots
and more information is available, a default set of these are activated
based on the precise nature of device. Further on operation, based on
conditions prevailing in the system (such as temperature), some OPP
availability may be temporarily controlled by the SoC frameworks.
To implement an OPP, some sort of power management support is necessary
hence this library depends on CONFIG_PM.
Contributions include:
Sanjeev Premi for the initial concept:
http://patchwork.kernel.org/patch/50998/
Kevin Hilman for converting original design to device-based.
Kevin Hilman and Paul Walmsey for cleaning up many of the function
abstractions, improvements and data structure handling.
Romit Dasgupta for using enums instead of opp pointers.
Thara Gopinath, Eduardo Valentin and Vishwanath BS for fixes and
cleanups.
Linus Walleij for recommending this layer be made generic for usage
in other architectures beyond OMAP and ARM.
Mark Brown, Andrew Morton, Rafael J. Wysocki, Paul E. McKenney for
valuable improvements.
Discussions and comments from:
http://marc.info/?l=linux-omap&m=126033945313269&w=2
http://marc.info/?l=linux-omap&m=125482970102327&w=2
http://marc.info/?t=125809247500002&r=1&w=2
http://marc.info/?l=linux-omap&m=126025973426007&w=2
http://marc.info/?t=128152609200064&r=1&w=2
http://marc.info/?t=128468723000002&r=1&w=2
incorporated.
v1: http://marc.info/?t=128468723000002&r=1&w=2
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2010-10-12 22:13:10 +00:00
|
|
|
|
2011-09-30 20:35:12 +00:00
|
|
|
/**
|
2017-01-02 09:11:03 +00:00
|
|
|
* dev_pm_opp_register_notifier() - Register OPP notifier for the device
|
|
|
|
* @dev: Device for which notifier needs to be registered
|
|
|
|
* @nb: Notifier block to be registered
|
2014-12-24 17:22:57 +00:00
|
|
|
*
|
2017-01-02 09:11:03 +00:00
|
|
|
* Return: 0 on success or a negative error value.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_register_notifier(struct device *dev, struct notifier_block *nb)
|
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
opp_table = _find_opp_table(dev);
|
2017-01-23 04:41:48 +00:00
|
|
|
if (IS_ERR(opp_table))
|
|
|
|
return PTR_ERR(opp_table);
|
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
ret = blocking_notifier_chain_register(&opp_table->head, nb);
|
2017-01-02 09:11:03 +00:00
|
|
|
|
2017-01-23 04:41:48 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2017-01-02 09:11:03 +00:00
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(dev_pm_opp_register_notifier);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dev_pm_opp_unregister_notifier() - Unregister OPP notifier for the device
|
|
|
|
* @dev: Device for which notifier needs to be unregistered
|
|
|
|
* @nb: Notifier block to be unregistered
|
2014-12-24 17:22:57 +00:00
|
|
|
*
|
2017-01-02 09:11:03 +00:00
|
|
|
* Return: 0 on success or a negative error value.
|
2011-09-30 20:35:12 +00:00
|
|
|
*/
|
2017-01-02 09:11:03 +00:00
|
|
|
int dev_pm_opp_unregister_notifier(struct device *dev,
|
|
|
|
struct notifier_block *nb)
|
2011-09-30 20:35:12 +00:00
|
|
|
{
|
2017-01-02 09:11:03 +00:00
|
|
|
struct opp_table *opp_table;
|
|
|
|
int ret;
|
2011-09-30 20:35:12 +00:00
|
|
|
|
2017-01-02 09:11:03 +00:00
|
|
|
opp_table = _find_opp_table(dev);
|
2017-01-23 04:41:48 +00:00
|
|
|
if (IS_ERR(opp_table))
|
|
|
|
return PTR_ERR(opp_table);
|
2017-01-02 09:11:03 +00:00
|
|
|
|
2017-01-23 04:41:49 +00:00
|
|
|
ret = blocking_notifier_chain_unregister(&opp_table->head, nb);
|
2011-09-30 20:35:12 +00:00
|
|
|
|
2017-01-23 04:41:48 +00:00
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2017-01-02 09:11:03 +00:00
|
|
|
|
|
|
|
return ret;
|
2011-09-30 20:35:12 +00:00
|
|
|
}
|
2017-01-02 09:11:03 +00:00
|
|
|
EXPORT_SYMBOL(dev_pm_opp_unregister_notifier);
|
2012-09-04 23:09:12 +00:00
|
|
|
|
2020-08-20 07:48:23 +00:00
|
|
|
/**
|
|
|
|
* dev_pm_opp_remove_table() - Free all OPPs associated with the device
|
|
|
|
* @dev: device pointer used to lookup OPP table.
|
|
|
|
*
|
|
|
|
* Free both OPPs created using static entries present in DT and the
|
|
|
|
* dynamically added entries.
|
|
|
|
*/
|
|
|
|
void dev_pm_opp_remove_table(struct device *dev)
|
2017-01-02 09:11:00 +00:00
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
|
2016-02-16 08:47:53 +00:00
|
|
|
/* Check for existing table for 'dev' */
|
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table)) {
|
|
|
|
int error = PTR_ERR(opp_table);
|
2015-07-29 10:52:58 +00:00
|
|
|
|
|
|
|
if (error != -ENODEV)
|
2016-02-16 08:47:53 +00:00
|
|
|
WARN(1, "%s: opp_table: %d\n",
|
2015-07-29 10:52:58 +00:00
|
|
|
IS_ERR_OR_NULL(dev) ?
|
|
|
|
"Invalid device" : dev_name(dev),
|
|
|
|
error);
|
2017-01-23 04:41:48 +00:00
|
|
|
return;
|
2015-07-29 10:52:58 +00:00
|
|
|
}
|
|
|
|
|
2020-08-31 07:33:06 +00:00
|
|
|
/*
|
|
|
|
* Drop the extra reference only if the OPP table was successfully added
|
|
|
|
* with dev_pm_opp_of_add_table() earlier.
|
|
|
|
**/
|
|
|
|
if (_opp_remove_all_static(opp_table))
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2018-09-12 07:05:19 +00:00
|
|
|
|
|
|
|
/* Drop reference taken by _find_opp_table() */
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
2015-07-29 10:52:58 +00:00
|
|
|
}
|
2016-05-03 14:05:04 +00:00
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_remove_table);
|
2021-01-20 22:26:47 +00:00
|
|
|
|
|
|
|
/**
|
|
|
|
* dev_pm_opp_sync_regulators() - Sync state of voltage regulators
|
|
|
|
* @dev: device for which we do this operation
|
|
|
|
*
|
|
|
|
* Sync voltage state of the OPP table regulators.
|
|
|
|
*
|
|
|
|
* Return: 0 on success or a negative error value.
|
|
|
|
*/
|
|
|
|
int dev_pm_opp_sync_regulators(struct device *dev)
|
|
|
|
{
|
|
|
|
struct opp_table *opp_table;
|
|
|
|
struct regulator *reg;
|
|
|
|
int i, ret = 0;
|
|
|
|
|
|
|
|
/* Device may not have OPP table */
|
|
|
|
opp_table = _find_opp_table(dev);
|
|
|
|
if (IS_ERR(opp_table))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* Regulator may not be required for the device */
|
|
|
|
if (unlikely(!opp_table->regulators))
|
|
|
|
goto put_table;
|
|
|
|
|
|
|
|
/* Nothing to sync if voltage wasn't changed */
|
|
|
|
if (!opp_table->enabled)
|
|
|
|
goto put_table;
|
|
|
|
|
|
|
|
for (i = 0; i < opp_table->regulator_count; i++) {
|
|
|
|
reg = opp_table->regulators[i];
|
|
|
|
ret = regulator_sync_voltage(reg);
|
|
|
|
if (ret)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
put_table:
|
|
|
|
/* Drop reference taken by _find_opp_table() */
|
|
|
|
dev_pm_opp_put_opp_table(opp_table);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(dev_pm_opp_sync_regulators);
|