Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
f75d2acc
Commit
f75d2acc
authored
Sep 03, 2019
by
Viresh Kumar
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'cpufreq/qcom-updates' into cpufreq/arm/linux-next
parents
9176b425
248b5f29
Changes
9
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
9 changed files
with
566 additions
and
23 deletions
+566
-23
Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt
Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt
+121
-6
Documentation/devicetree/bindings/opp/qcom-opp.txt
Documentation/devicetree/bindings/opp/qcom-opp.txt
+19
-0
MAINTAINERS
MAINTAINERS
+2
-2
drivers/cpufreq/Kconfig.arm
drivers/cpufreq/Kconfig.arm
+2
-2
drivers/cpufreq/Makefile
drivers/cpufreq/Makefile
+1
-1
drivers/cpufreq/cpufreq-dt-platdev.c
drivers/cpufreq/cpufreq-dt-platdev.c
+1
-0
drivers/cpufreq/qcom-cpufreq-nvmem.c
drivers/cpufreq/qcom-cpufreq-nvmem.c
+352
-0
drivers/opp/core.c
drivers/opp/core.c
+58
-10
include/linux/pm_opp.h
include/linux/pm_opp.h
+10
-2
No files found.
Documentation/devicetree/bindings/opp/
kryo
-cpufreq.txt
→
Documentation/devicetree/bindings/opp/
qcom-nvmem
-cpufreq.txt
View file @
f75d2acc
Qualcomm Technologies, Inc.
KRYO
CPUFreq and OPP bindings
Qualcomm Technologies, Inc.
NVMEM
CPUFreq and OPP bindings
===================================
In Certain Qualcomm Technologies, Inc. SoCs like apq8096 and msm8996
th
at have KRYO processors, the CPU ferequencies subset and voltage value
of each OPP varies based on
the silicon variant in use.
In Certain Qualcomm Technologies, Inc. SoCs like apq8096 and msm8996
,
th
e CPU frequencies subset and voltage value of each OPP varies based on
the silicon variant in use.
Qualcomm Technologies, Inc. Process Voltage Scaling Tables
defines the voltage and frequency value based on the msm-id in SMEM
and speedbin blown in the efuse combination.
The qcom-cpufreq-
kryo
driver reads the msm-id and efuse value from the SoC
The qcom-cpufreq-
nvmem
driver reads the msm-id and efuse value from the SoC
to provide the OPP framework with required information (existing HW bitmap).
This is used to determine the voltage and frequency value for each OPP of
operating-points-v2 table when it is parsed by the OPP framework.
Required properties:
--------------------
In 'cpu
s
' nodes:
In 'cpu' nodes:
- operating-points-v2: Phandle to the operating-points-v2 table to use.
In 'operating-points-v2' table:
- compatible: Should be
- 'operating-points-v2-kryo-cpu' for apq8096 and msm8996.
Optional properties:
--------------------
In 'cpu' nodes:
- power-domains: A phandle pointing to the PM domain specifier which provides
the performance states available for active state management.
Please refer to the power-domains bindings
Documentation/devicetree/bindings/power/power_domain.txt
and also examples below.
- power-domain-names: Should be
- 'cpr' for qcs404.
In 'operating-points-v2' table:
- nvmem-cells: A phandle pointing to a nvmem-cells node representing the
efuse registers that has information about the
speedbin that is used to select the right frequency/voltage
...
...
@@ -678,3 +691,105 @@ soc {
};
};
};
Example 2:
---------
cpus {
#address-cells = <1>;
#size-cells = <0>;
CPU0: cpu@100 {
device_type = "cpu";
compatible = "arm,cortex-a53";
reg = <0x100>;
....
clocks = <&apcs_glb>;
operating-points-v2 = <&cpu_opp_table>;
power-domains = <&cpr>;
power-domain-names = "cpr";
};
CPU1: cpu@101 {
device_type = "cpu";
compatible = "arm,cortex-a53";
reg = <0x101>;
....
clocks = <&apcs_glb>;
operating-points-v2 = <&cpu_opp_table>;
power-domains = <&cpr>;
power-domain-names = "cpr";
};
CPU2: cpu@102 {
device_type = "cpu";
compatible = "arm,cortex-a53";
reg = <0x102>;
....
clocks = <&apcs_glb>;
operating-points-v2 = <&cpu_opp_table>;
power-domains = <&cpr>;
power-domain-names = "cpr";
};
CPU3: cpu@103 {
device_type = "cpu";
compatible = "arm,cortex-a53";
reg = <0x103>;
....
clocks = <&apcs_glb>;
operating-points-v2 = <&cpu_opp_table>;
power-domains = <&cpr>;
power-domain-names = "cpr";
};
};
cpu_opp_table: cpu-opp-table {
compatible = "operating-points-v2-kryo-cpu";
opp-shared;
opp-1094400000 {
opp-hz = /bits/ 64 <1094400000>;
required-opps = <&cpr_opp1>;
};
opp-1248000000 {
opp-hz = /bits/ 64 <1248000000>;
required-opps = <&cpr_opp2>;
};
opp-1401600000 {
opp-hz = /bits/ 64 <1401600000>;
required-opps = <&cpr_opp3>;
};
};
cpr_opp_table: cpr-opp-table {
compatible = "operating-points-v2-qcom-level";
cpr_opp1: opp1 {
opp-level = <1>;
qcom,opp-fuse-level = <1>;
};
cpr_opp2: opp2 {
opp-level = <2>;
qcom,opp-fuse-level = <2>;
};
cpr_opp3: opp3 {
opp-level = <3>;
qcom,opp-fuse-level = <3>;
};
};
....
soc {
....
cpr: power-controller@b018000 {
compatible = "qcom,qcs404-cpr", "qcom,cpr";
reg = <0x0b018000 0x1000>;
....
vdd-apc-supply = <&pms405_s3>;
#power-domain-cells = <0>;
operating-points-v2 = <&cpr_opp_table>;
....
};
};
Documentation/devicetree/bindings/opp/qcom-opp.txt
0 → 100644
View file @
f75d2acc
Qualcomm OPP bindings to describe OPP nodes
The bindings are based on top of the operating-points-v2 bindings
described in Documentation/devicetree/bindings/opp/opp.txt
Additional properties are described below.
* OPP Table Node
Required properties:
- compatible: Allow OPPs to express their compatibility. It should be:
"operating-points-v2-qcom-level"
* OPP Node
Required properties:
- qcom,opp-fuse-level: A positive value representing the fuse corner/level
associated with this OPP node. Sometimes several corners/levels shares
a certain fuse corner/level. A fuse corner/level contains e.g. ref uV,
min uV, and max uV.
MAINTAINERS
View file @
f75d2acc
...
...
@@ -13292,8 +13292,8 @@ QUALCOMM CPUFREQ DRIVER MSM8996/APQ8096
M: Ilia Lin <ilia.lin@kernel.org>
L: linux-pm@vger.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/opp/
kryo
-cpufreq.txt
F: drivers/cpufreq/qcom-cpufreq-
kryo
.c
F: Documentation/devicetree/bindings/opp/
qcom-nvmem
-cpufreq.txt
F: drivers/cpufreq/qcom-cpufreq-
nvmem
.c
QUALCOMM EMAC GIGABIT ETHERNET DRIVER
M: Timur Tabi <timur@kernel.org>
...
...
drivers/cpufreq/Kconfig.arm
View file @
f75d2acc
...
...
@@ -132,8 +132,8 @@ config ARM_OMAP2PLUS_CPUFREQ
depends on ARCH_OMAP2PLUS
default ARCH_OMAP2PLUS
config ARM_QCOM_CPUFREQ_
KRYO
tristate "Qualcomm
Kryo
based CPUFreq"
config ARM_QCOM_CPUFREQ_
NVMEM
tristate "Qualcomm
nvmem
based CPUFreq"
depends on ARM64
depends on QCOM_QFPROM
depends on QCOM_SMEM
...
...
drivers/cpufreq/Makefile
View file @
f75d2acc
...
...
@@ -64,7 +64,7 @@ obj-$(CONFIG_ARM_OMAP2PLUS_CPUFREQ) += omap-cpufreq.o
obj-$(CONFIG_ARM_PXA2xx_CPUFREQ)
+=
pxa2xx-cpufreq.o
obj-$(CONFIG_PXA3xx)
+=
pxa3xx-cpufreq.o
obj-$(CONFIG_ARM_QCOM_CPUFREQ_HW)
+=
qcom-cpufreq-hw.o
obj-$(CONFIG_ARM_QCOM_CPUFREQ_
KRYO)
+=
qcom-cpufreq-kryo
.o
obj-$(CONFIG_ARM_QCOM_CPUFREQ_
NVMEM)
+=
qcom-cpufreq-nvmem
.o
obj-$(CONFIG_ARM_RASPBERRYPI_CPUFREQ)
+=
raspberrypi-cpufreq.o
obj-$(CONFIG_ARM_S3C2410_CPUFREQ)
+=
s3c2410-cpufreq.o
obj-$(CONFIG_ARM_S3C2412_CPUFREQ)
+=
s3c2412-cpufreq.o
...
...
drivers/cpufreq/cpufreq-dt-platdev.c
View file @
f75d2acc
...
...
@@ -127,6 +127,7 @@ static const struct of_device_id blacklist[] __initconst = {
{
.
compatible
=
"qcom,apq8096"
,
},
{
.
compatible
=
"qcom,msm8996"
,
},
{
.
compatible
=
"qcom,qcs404"
,
},
{
.
compatible
=
"st,stih407"
,
},
{
.
compatible
=
"st,stih410"
,
},
...
...
drivers/cpufreq/qcom-cpufreq-
kryo
.c
→
drivers/cpufreq/qcom-cpufreq-
nvmem
.c
View file @
f75d2acc
This diff is collapsed.
Click to expand it.
drivers/opp/core.c
View file @
f75d2acc
...
...
@@ -401,6 +401,54 @@ struct dev_pm_opp *dev_pm_opp_find_freq_exact(struct device *dev,
}
EXPORT_SYMBOL_GPL
(
dev_pm_opp_find_freq_exact
);
/**
* 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
)
{
struct
opp_table
*
opp_table
;
struct
dev_pm_opp
*
temp_opp
,
*
opp
=
ERR_PTR
(
-
ERANGE
);
opp_table
=
_find_opp_table
(
dev
);
if
(
IS_ERR
(
opp_table
))
{
int
r
=
PTR_ERR
(
opp_table
);
dev_err
(
dev
,
"%s: OPP table not found (%d)
\n
"
,
__func__
,
r
);
return
ERR_PTR
(
r
);
}
mutex_lock
(
&
opp_table
->
lock
);
list_for_each_entry
(
temp_opp
,
&
opp_table
->
opp_list
,
node
)
{
if
(
temp_opp
->
level
==
level
)
{
opp
=
temp_opp
;
/* Increment the reference count of OPP */
dev_pm_opp_get
(
opp
);
break
;
}
}
mutex_unlock
(
&
opp_table
->
lock
);
dev_pm_opp_put_opp_table
(
opp_table
);
return
opp
;
}
EXPORT_SYMBOL_GPL
(
dev_pm_opp_find_level_exact
);
static
noinline
struct
dev_pm_opp
*
_find_freq_ceil
(
struct
opp_table
*
opp_table
,
unsigned
long
*
freq
)
{
...
...
@@ -1771,6 +1819,7 @@ static void _opp_detach_genpd(struct opp_table *opp_table)
* dev_pm_opp_attach_genpd - Attach genpd(s) for the device and save virtual device pointer
* @dev: Consumer device for which the genpd is getting attached.
* @names: Null terminated array of pointers containing names of genpd to attach.
* @virt_devs: Pointer to return the array of virtual devices.
*
* Multiple generic power domains for a device are supported with the help of
* virtual genpd devices, which are created for each consumer device - genpd
...
...
@@ -1784,12 +1833,16 @@ static void _opp_detach_genpd(struct opp_table *opp_table)
*
* 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.
*
* The order of entries in the names array must match the order in which
* "required-opps" are added in DT.
*/
struct
opp_table
*
dev_pm_opp_attach_genpd
(
struct
device
*
dev
,
const
char
**
names
)
struct
opp_table
*
dev_pm_opp_attach_genpd
(
struct
device
*
dev
,
const
char
**
names
,
struct
device
***
virt_devs
)
{
struct
opp_table
*
opp_table
;
struct
device
*
virt_dev
;
int
index
,
ret
=
-
EINVAL
;
int
index
=
0
,
ret
=
-
EINVAL
;
const
char
**
name
=
names
;
opp_table
=
dev_pm_opp_get_opp_table
(
dev
);
...
...
@@ -1815,14 +1868,6 @@ struct opp_table *dev_pm_opp_attach_genpd(struct device *dev, const char **names
goto
unlock
;
while
(
*
name
)
{
index
=
of_property_match_string
(
dev
->
of_node
,
"power-domain-names"
,
*
name
);
if
(
index
<
0
)
{
dev_err
(
dev
,
"Failed to find power domain: %s (%d)
\n
"
,
*
name
,
index
);
goto
err
;
}
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
);
...
...
@@ -1843,9 +1888,12 @@ struct opp_table *dev_pm_opp_attach_genpd(struct device *dev, const char **names
}
opp_table
->
genpd_virt_devs
[
index
]
=
virt_dev
;
index
++
;
name
++
;
}
if
(
virt_devs
)
*
virt_devs
=
opp_table
->
genpd_virt_devs
;
mutex_unlock
(
&
opp_table
->
genpd_virt_dev_lock
);
return
opp_table
;
...
...
include/linux/pm_opp.h
View file @
f75d2acc
...
...
@@ -96,6 +96,8 @@ unsigned long dev_pm_opp_get_suspend_opp_freq(struct device *dev);
struct
dev_pm_opp
*
dev_pm_opp_find_freq_exact
(
struct
device
*
dev
,
unsigned
long
freq
,
bool
available
);
struct
dev_pm_opp
*
dev_pm_opp_find_level_exact
(
struct
device
*
dev
,
unsigned
int
level
);
struct
dev_pm_opp
*
dev_pm_opp_find_freq_floor
(
struct
device
*
dev
,
unsigned
long
*
freq
);
...
...
@@ -128,7 +130,7 @@ struct opp_table *dev_pm_opp_set_clkname(struct device *dev, const char * name);
void
dev_pm_opp_put_clkname
(
struct
opp_table
*
opp_table
);
struct
opp_table
*
dev_pm_opp_register_set_opp_helper
(
struct
device
*
dev
,
int
(
*
set_opp
)(
struct
dev_pm_set_opp_data
*
data
));
void
dev_pm_opp_unregister_set_opp_helper
(
struct
opp_table
*
opp_table
);
struct
opp_table
*
dev_pm_opp_attach_genpd
(
struct
device
*
dev
,
const
char
**
names
);
struct
opp_table
*
dev_pm_opp_attach_genpd
(
struct
device
*
dev
,
const
char
**
names
,
struct
device
***
virt_devs
);
void
dev_pm_opp_detach_genpd
(
struct
opp_table
*
opp_table
);
int
dev_pm_opp_xlate_performance_state
(
struct
opp_table
*
src_table
,
struct
opp_table
*
dst_table
,
unsigned
int
pstate
);
int
dev_pm_opp_set_rate
(
struct
device
*
dev
,
unsigned
long
target_freq
);
...
...
@@ -200,6 +202,12 @@ static inline struct dev_pm_opp *dev_pm_opp_find_freq_exact(struct device *dev,
return
ERR_PTR
(
-
ENOTSUPP
);
}
static
inline
struct
dev_pm_opp
*
dev_pm_opp_find_level_exact
(
struct
device
*
dev
,
unsigned
int
level
)
{
return
ERR_PTR
(
-
ENOTSUPP
);
}
static
inline
struct
dev_pm_opp
*
dev_pm_opp_find_freq_floor
(
struct
device
*
dev
,
unsigned
long
*
freq
)
{
...
...
@@ -292,7 +300,7 @@ static inline struct opp_table *dev_pm_opp_set_clkname(struct device *dev, const
static
inline
void
dev_pm_opp_put_clkname
(
struct
opp_table
*
opp_table
)
{}
static
inline
struct
opp_table
*
dev_pm_opp_attach_genpd
(
struct
device
*
dev
,
const
char
**
names
)
static
inline
struct
opp_table
*
dev_pm_opp_attach_genpd
(
struct
device
*
dev
,
const
char
**
names
,
struct
device
***
virt_devs
)
{
return
ERR_PTR
(
-
ENOTSUPP
);
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment