| /Linux-v5.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 …]
|
| D | cpuidle.c | 147 * The state used here cannot be a "coupled" one, because the "coupled" in enter_s2idle_proper()
702 * @coupled_cpus: a cpumask for the coupled states
724 * On multiplatform for ARM, the coupled idle states could be in cpuidle_register()
|
| /Linux-v5.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.
|
| /Linux-v5.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()
484 * Returns number of regulators coupled with rdev.
492 "regulator-coupled-with", in of_get_n_coupled()
498 /* Looks for "to_find" device_node in src's "regulator-coupled-with" property */
507 "regulator-coupled-with", in of_coupling_find_node()
512 "regulator-coupled-with", i); in of_coupling_find_node()
539 * - all coupled regulators have the same max_spread
540 * - all coupled regulators have the same number of regulator_dev phandles
565 "regulator-coupled-with", i); in of_check_coupling_data()
[all …]
|
| /Linux-v5.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
|
| D | machine.h | 103 * @max_spread: Max possible spread between coupled regulators
156 /* used for coupled regulators */
|
| /Linux-v5.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>;
|
| D | tegra20-paz00.dts | 392 regulator-coupled-with = <&rtc_vdd_reg &cpu_vdd_reg>;
393 regulator-coupled-max-spread = <170000 450000>;
403 regulator-coupled-with = <&core_vdd_reg &rtc_vdd_reg>;
404 regulator-coupled-max-spread = <450000 450000>;
430 regulator-coupled-with = <&core_vdd_reg &cpu_vdd_reg>;
431 regulator-coupled-max-spread = <170000 450000>;
|
| /Linux-v5.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.
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.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()
|
| /Linux-v5.10/net/sched/ |
| D | act_gact.c | 28 smp_rmb(); /* coupled with smp_wmb() in tcf_gact_init() */ in gact_net_rand()
38 smp_rmb(); /* coupled with smp_wmb() in tcf_gact_init() */ in gact_determ()
132 * coupled with smp_rmb() in gact_net_rand() & gact_determ() in tcf_gact_init()
|
| /Linux-v5.10/arch/csky/ |
| D | Kconfig | 226 bool "Tightly-Coupled/Sram Memory"
229 The implementation are not only used by TCM (Tightly-Coupled Meory)
|
| /Linux-v5.10/Documentation/devicetree/bindings/media/i2c/ |
| D | imi,rdacm2x-gmsl.yaml | 21 coupled with an OV10635 image sensor and an embedded MCU. Both the MCU and
25 The RDACM21 camera module encloses the same serializer, coupled with an
|
| /Linux-v5.10/drivers/soc/samsung/ |
| D | exynos-regulator-coupler.c | 72 * If not, set it to minimum voltage, allowed by other coupled in regulator_get_optimal_voltage()
155 * the coupled voltages. in exynos_coupler_balance_voltage()
|
| /Linux-v5.10/sound/hda/ext/ |
| D | hdac_ext_stream.c | 324 * @type: type of stream (coupled, host or link stream)
326 * This assigns the stream based on the type (coupled/host/link), for the
329 * coupled: Looks for an unused stream
367 * @type: type of stream (coupled, host or link stream)
|
| /Linux-v5.10/Documentation/arm/ |
| D | tcm.rst | 2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
|
| /Linux-v5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,nvic.txt | 3 The NVIC provides an interrupt controller that is tightly coupled to
|
| /Linux-v5.10/Documentation/driver-api/pm/ |
| D | cpuidle.rst | 226 entries in the :c:member:`states` array represent "coupled" idle states (that
229 to be the index of an idle state that is not "coupled" (that is, one that can be
238 are no "coupled" idle state entries in the driver's :c:member:`states` array,
|
| /Linux-v5.10/Documentation/ |
| D | asm-annotations.rst | 113 All of these **shall** be coupled with ``SYM_FUNC_END``. First, it marks
151 Again, every ``SYM_CODE_START*`` **shall** be coupled by ``SYM_CODE_END``.
|
| /Linux-v5.10/arch/arm64/boot/dts/allwinner/ |
| D | sun50i-h6-orangepi-lite2.dts | 44 * enable of coupled regulators, keep them
|
