Searched +full:opp +full:- +full:1593600000 (Results 1 – 4 of 4) sorted by relevance
1 // SPDX-License-Identifier: BSD-3-Clause9 /delete-node/ opp-table-cluster0;10 /delete-node/ opp-table-cluster1;18 cluster0_opp: opp-table-cluster0 {19 compatible = "operating-points-v2-kryo-cpu";20 nvmem-cells = <&speedbin_efuse>;21 opp-shared;23 opp-307200000 {24 opp-hz = /bits/ 64 <307200000>;25 opp-supported-hw = <0x70>;[all …]
1 // SPDX-License-Identifier: GPL-2.0-only3 * Copyright (c) 2014-2015, The Linux Foundation. All rights reserved.6 #include <dt-bindings/interrupt-controller/arm-gic.h>7 #include <dt-bindings/clock/qcom,gcc-msm899[all...]
1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)3 ---4 $id: http://devicetree.org/schemas/opp/op[all...]
1 Qualcomm Technologies, Inc. NVMEM CPUFreq and OPP bindings5 the CPU frequencies subset and voltage value of each OPP varies based on8 defines the voltage and frequency value based on the msm-id in SMEM10 The qcom-cpufreq-nvmem driver reads the msm-id and efuse value from the SoC11 to provide the OPP framework with required information (existing HW bitmap).12 This is used to determine the voltage and frequency value for each OPP of13 operating-points-v2 table when it is parsed by the OPP framework.16 --------------------18 - operating-points-v2: Phandle to the operating-points-v2 table to use.20 In 'operating-points-v2' table:[all …]