| /kernel/linux/linux-5.10/drivers/cpuidle/ |
| D | coupled.c | 3 * coupled.c - helper functions to enter the same idle state on multiple cpus
21 * DOC: Coupled cpuidle states
30 * WFI), and one or more "coupled" power states that affect blocks
32 * sometimes the whole SoC). Entering a coupled power state must
36 * WFI state until all cpus are ready to enter a coupled state, at
37 * which point the coupled state function will be called on all
46 * ready counter matches the number of online coupled cpus. If any
50 * requested_state stores the deepest coupled idle state each cpu
56 * and only read after all the cpus are ready for the coupled idle
60 * of cpus in the coupled set that are currently or soon will be
[all …]
|
| /kernel/linux/linux-6.6/drivers/cpuidle/ |
| D | coupled.c | 3 * coupled.c - helper functions to enter the same idle state on multiple cpus
21 * DOC: Coupled cpuidle states
30 * WFI), and one or more "coupled" power states that affect blocks
32 * sometimes the whole SoC). Entering a coupled power state must
36 * WFI state until all cpus are ready to enter a coupled state, at
37 * which point the coupled state function will be called on all
46 * ready counter matches the number of online coupled cpus. If any
50 * requested_state stores the deepest coupled idle state each cpu
56 * and only read after all the cpus are ready for the coupled idle
60 * of cpus in the coupled set that are currently or soon will be
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | nvidia,tegra-regulators-coupling.txt | 5 Thus on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30
11 On Tegra20 SoC's there are 3 coupled regulators: CORE, RTC and CPU.
18 On Tegra30 SoC's there are 2 coupled regulators: CORE and CPU. The CORE
39 regulator-coupled-with = <&rtc_vdd_reg &cpu_vdd_reg>;
40 regulator-coupled-max-spread = <170000 550000>;
49 regulator-coupled-with = <&core_vdd_reg &cpu_vdd_reg>;
50 regulator-coupled-max-spread = <170000 550000>;
59 regulator-coupled-with = <&core_vdd_reg &rtc_vdd_reg>;
60 regulator-coupled-max-spread = <550000 550000>;
|
| D | regulator.yaml | 129 regulator-coupled-with:
130 description: Regulators with which the regulator is coupled. The linkage
131 is 2-way - all coupled regulators should be linked with each other.
132 A regulator should not be coupled with its supplier.
135 regulator-coupled-max-spread:
136 description: Array of maximum spread between voltages of coupled regulators
138 couple specified by the regulator-coupled-with property.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/ |
| D | nvidia,tegra-regulators-coupling.txt | 5 Thus on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30
11 On Tegra20 SoC's there are 3 coupled regulators: CORE, RTC and CPU.
18 On Tegra30 SoC's there are 2 coupled regulators: CORE and CPU. The CORE
39 regulator-coupled-with = <&rtc_vdd_reg &cpu_vdd_reg>;
40 regulator-coupled-max-spread = <170000 550000>;
49 regulator-coupled-with = <&core_vdd_reg &cpu_vdd_reg>;
50 regulator-coupled-max-spread = <170000 550000>;
59 regulator-coupled-with = <&core_vdd_reg &rtc_vdd_reg>;
60 regulator-coupled-max-spread = <550000 550000>;
|
| D | regulator.yaml | 212 regulator-coupled-with:
213 description: Regulators with which the regulator is coupled. The linkage
214 is 2-way - all coupled regulators should be linked with each other.
215 A regulator should not be coupled with its supplier.
220 regulator-coupled-max-spread:
221 description: Array of maximum spread between voltages of coupled regulators
223 couple specified by the regulator-coupled-with property.
|
| /kernel/linux/linux-5.10/drivers/regulator/ |
| D | of_regulator.c | 37 n_phandles = of_count_phandle_with_args(np, "regulator-coupled-with", in of_get_regulation_constraints()
180 of_property_read_u32_array(np, "regulator-coupled-max-spread", in of_get_regulation_constraints()
488 * Returns number of regulators coupled with rdev.
496 "regulator-coupled-with", in of_get_n_coupled()
502 /* Looks for "to_find" device_node in src's "regulator-coupled-with" property */
511 "regulator-coupled-with", in of_coupling_find_node()
516 "regulator-coupled-with", i); in of_coupling_find_node()
543 * - all coupled regulators have the same max_spread
544 * - all coupled regulators have the same number of regulator_dev phandles
569 "regulator-coupled-with", i); in of_check_coupling_data()
[all …]
|
| /kernel/linux/linux-6.6/include/linux/regulator/ |
| D | coupler.h | 23 * @attach_regulator: Callback invoked on creation of a coupled regulator,
29 * @detach_regulator: Callback invoked on destruction of a coupled regulator.
31 * @balance_voltage: Callback invoked when voltage of a coupled regulator is
32 * changing. Called with all of the coupled rdev's being held
34 * balancing, changing voltage of the coupled regulators as
|
| /kernel/linux/linux-6.6/drivers/regulator/ |
| D | of_regulator.c | 93 n_phandles = of_count_phandle_with_args(np, "regulator-coupled-with", in of_get_regulation_constraints()
236 of_property_read_u32_array(np, "regulator-coupled-max-spread", in of_get_regulation_constraints()
554 * Returns number of regulators coupled with rdev.
562 "regulator-coupled-with", in of_get_n_coupled()
568 /* Looks for "to_find" device_node in src's "regulator-coupled-with" property */
577 "regulator-coupled-with", in of_coupling_find_node()
582 "regulator-coupled-with", i); in of_coupling_find_node()
609 * - all coupled regulators have the same max_spread
610 * - all coupled regulators have the same number of regulator_dev phandles
635 "regulator-coupled-with", i); in of_check_coupling_data()
[all …]
|
| /kernel/linux/linux-5.10/include/linux/regulator/ |
| D | coupler.h | 23 * @attach_regulator: Callback invoked on creation of a coupled regulator,
29 * @detach_regulator: Callback invoked on destruction of a coupled regulator.
31 * @balance_voltage: Callback invoked when voltage of a coupled regulator is
32 * changing. Called with all of the coupled rdev's being held
34 * balancing, changing voltage of the coupled regulators as
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/ |
| D | qcom,q6dsp-lpass-clocks.yaml | 25 1 = for no coupled clock
26 2 = for dividend of the coupled clock
27 3 = for divisor of the coupled clock
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | tegra30-asus-nexus7-grouper-ti-pmic.dtsi | 55 regulator-coupled-with = <&vdd_core>;
56 regulator-coupled-max-spread = <300000>;
132 regulator-coupled-with = <&vdd_cpu>;
133 regulator-coupled-max-spread = <300000>;
|
| D | tegra30-cardhu-a04.dts | 102 regulator-coupled-with = <&vddcore_reg>;
103 regulator-coupled-max-spread = <300000>;
112 regulator-coupled-with = <&vddctrl_reg>;
113 regulator-coupled-max-spread = <300000>;
|
| D | tegra30-asus-nexus7-grouper-maxim-pmic.dtsi | 69 regulator-coupled-with = <&vdd_core>;
70 regulator-coupled-max-spread = <300000>;
82 regulator-coupled-with = <&vdd_cpu>;
83 regulator-coupled-max-spread = <300000>;
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/nvidia/ |
| D | tegra30-asus-nexus7-grouper-ti-pmic.dtsi | 56 regulator-coupled-with = <&vdd_core>;
57 regulator-coupled-max-spread = <300000>;
133 regulator-coupled-with = <&vdd_cpu>;
134 regulator-coupled-max-spread = <300000>;
|
| D | tegra30-asus-nexus7-grouper-maxim-pmic.dtsi | 69 regulator-coupled-with = <&vdd_core>;
70 regulator-coupled-max-spread = <300000>;
82 regulator-coupled-with = <&vdd_cpu>;
83 regulator-coupled-max-spread = <300000>;
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | samsung,s2mps11.yaml | 191 regulator-coupled-with = <&buck3_reg>;
192 regulator-coupled-max-spread = <300000>;
205 regulator-coupled-with = <&buck2_reg>;
206 regulator-coupled-max-spread = <300000>;
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | pm-cps.h | 12 * thus in an MT system the VP(E)s within each core are coupled and can only
45 * each coupled CPU. Returns 0 on successful entry & exit, otherwise -errno.
|
| /kernel/linux/linux-6.6/arch/mips/include/asm/ |
| D | pm-cps.h | 12 * thus in an MT system the VP(E)s within each core are coupled and can only
45 * each coupled CPU. Returns 0 on successful entry & exit, otherwise -errno.
|
| /kernel/linux/linux-5.10/include/linux/input/ |
| D | adxl34x.h | 93 * AC/DC: A '0' = DC coupled operation and a '1' = AC coupled
94 * operation. In DC coupled operation, the current acceleration is
97 * coupled operation for activity detection, the acceleration value
102 * AC coupled operation for inactivity detection, a reference value
|
| /kernel/linux/linux-6.6/include/linux/input/ |
| D | adxl34x.h | 93 * AC/DC: A '0' = DC coupled operation and a '1' = AC coupled
94 * operation. In DC coupled operation, the current acceleration is
97 * coupled operation for activity detection, the acceleration value
102 * AC coupled operation for inactivity detection, a reference value
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | qcom,q6afe.txt | 114 1 - for no coupled clock
115 2 - for dividend of the coupled clock
116 3 - for divisor of the coupled clock
|
| /kernel/linux/linux-6.6/arch/mips/kernel/ |
| D | pm-cps.c | 26 * @online: the count of online coupled VPEs
51 * Indicates the number of coupled VPEs ready to operate in a non-coherent
56 /* Indicates online CPUs coupled with the current CPU */
127 /* Calculate which coupled CPUs (VPEs) are online */ in cps_pm_enter_state()
180 * it needs to wake up any coupled VPEs still running their wait in cps_pm_enter_state()
182 * coordination between the coupled VPEs & provide the governor with in cps_pm_enter_state()
394 * but in the coupled case the enable step will only run on one VPE. in cps_gen_entry_code()
563 * Re-enable coherence. Note that for CPS_PM_NC_WAIT all coupled VPEs in cps_gen_entry_code()
|
| /kernel/linux/linux-5.10/arch/mips/kernel/ |
| D | pm-cps.c | 26 * @online: the count of online coupled VPEs
51 * Indicates the number of coupled VPEs ready to operate in a non-coherent
56 /* Indicates online CPUs coupled with the current CPU */
127 /* Calculate which coupled CPUs (VPEs) are online */ in cps_pm_enter_state()
180 * it needs to wake up any coupled VPEs still running their wait in cps_pm_enter_state()
182 * coordination between the coupled VPEs & provide the governor with in cps_pm_enter_state()
394 * but in the coupled case the enable step will only run on one VPE. in cps_gen_entry_code()
563 * Re-enable coherence. Note that for CPS_PM_NC_WAIT all coupled VPEs in cps_gen_entry_code()
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/mediatek/ |
| D | mt8183-pumpkin.dts | 182 regulator-coupled-with = <&mt6358_vsram_gpu_reg>;
183 regulator-coupled-max-spread = <100000>;
190 regulator-coupled-with = <&mt6358_vgpu_reg>;
191 regulator-coupled-max-spread = <100000>;
|