Home
last modified time | relevance | path

Searched full:coupled (Results 1 – 25 of 136) sorted by relevance

123456

/linux/drivers/cpuidle/
H A Dcoupled.c3 * 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 …]
/linux/Documentation/devicetree/bindings/regulator/
H A Dnvidia,tegra-regulators-coupling.txt5 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>;
/linux/include/linux/regulator/
H A Dcoupler.h24 * @attach_regulator: Callback invoked on creation of a coupled regulator,
30 * @detach_regulator: Callback invoked on destruction of a coupled regulator.
32 * @balance_voltage: Callback invoked when voltage of a coupled regulator is
33 * changing. Called with all of the coupled rdev's being held
35 * balancing, changing voltage of the coupled regulators as
/linux/arch/arm64/boot/dts/rockchip/
H A Drk3588-evb2-v10.dts311 regulator-coupled-with = <&vdd_gpu_mem_s0>;
312 regulator-coupled-max-spread = <10000>;
365 regulator-coupled-with = <&vdd_gpu_s0>;
366 regulator-coupled-max-spread = <10000>;
615 regulator-coupled-with = <&vdd_cpu_big1_mem_s0>;
616 regulator-coupled-max-spread = <10000>;
629 regulator-coupled-with = <&vdd_cpu_big0_mem_s0>;
630 regulator-coupled-max-spread = <10000>;
643 regulator-coupled-with = <&vdd_cpu_lit_mem_s0>;
644 regulator-coupled-max-spread = <10000>;
[all …]
H A Drk3588s-evb1-v10.dts846 regulator-coupled-with = <&vdd_cpu_big1_mem_s0>;
847 regulator-coupled-max-spread = <10000>;
861 regulator-coupled-with = <&vdd_cpu_big0_mem_s0>;
862 regulator-coupled-max-spread = <10000>;
876 regulator-coupled-with = <&vdd_cpu_lit_mem_s0>;
877 regulator-coupled-max-spread = <10000>;
905 regulator-coupled-with = <&vdd_cpu_big1_s0>;
906 regulator-coupled-max-spread = <10000>;
921 regulator-coupled-with = <&vdd_cpu_big0_s0>;
922 regulator-coupled-max-spread = <10000>;
[all …]
/linux/drivers/regulator/
H A Dof_regulator.c93 n_phandles = of_count_phandle_with_args(np, "regulator-coupled-with", in of_get_regulation_constraints()
248 of_property_read_u32_array(np, "regulator-coupled-max-spread", in of_get_regulation_constraints()
744 * Returns number of regulators coupled with rdev.
752 "regulator-coupled-with", in of_get_n_coupled()
758 /* Looks for "to_find" device_node in src's "regulator-coupled-with" property */
767 "regulator-coupled-with", in of_coupling_find_node()
772 "regulator-coupled-with", i); in of_coupling_find_node()
799 * - all coupled regulators have the same max_spread
800 * - all coupled regulators have the same number of regulator_dev phandles
825 "regulator-coupled-with", i); in of_check_coupling_data()
[all …]
/linux/Documentation/devicetree/bindings/sound/
H A Dqcom,q6dsp-lpass-clocks.yaml25 1 = for no coupled clock
26 2 = for dividend of the coupled clock
27 3 = for divisor of the coupled clock
/linux/Documentation/iio/
H A Dadxl345.rst86 Note that activity and inactivity detection are DC-coupled by default;
87 therefore, only the AC-coupled activity and inactivity events are explicitly
107 | in_accel_mag_adaptive_rising_en | Enable AC coupled activity on X axis |
109 | in_accel_mag_adaptive_falling_period | AC coupled inactivity time in seconds |
111 | in_accel_mag_adaptive_falling_value | AC coupled inactivity threshold in 62.5/LSB |
113 | in_accel_mag_adaptive_rising_value | AC coupled activity threshold in 62.5/LSB |
123 | in_accel_x&y&z_mag_adaptive_falling_en | Enable AC coupled inactivity on all axis |
163 activity detection, use auto-sleep, and be either AC- or DC-coupled.
178 In DC-coupled mode, the current acceleration magnitude is directly compared to
180 inactivity. In contrast, AC-coupled activity detection uses the acceleration
[all …]
H A Dadxl313.rst63 | in_accel_mag_adaptive_falling_period | AC coupled inactivity time. …
65 | in_accel_mag_adaptive_falling_value | AC coupled inactivity threshold. …
67 | in_accel_mag_adaptive_rising_value | AC coupled activity threshold. …
75 | in_accel_x\&y\&z_mag_adaptive_falling_en | Enable or disable AC coupled inactivity event…
77 | in_accel_x\|y\|z_mag_adaptive_rising_en | Enable or disable AC coupled activity events.…
84 The default coupling is DC coupled events. In this case the threshold will
85 be in place as such, where for the AC coupled case an adaptive threshold
267 Now, enabling activity, e.g. the AC coupled counter-part ``ACTIVITY_AC``
287 AC- or DC-coupled (the default) events are used similarly.
/linux/arch/arm/boot/dts/nvidia/
H A Dtegra30-asus-nexus7-grouper-ti-pmic.dtsi56 regulator-coupled-with = <&vdd_core>;
57 regulator-coupled-max-spread = <300000>;
133 regulator-coupled-with = <&vdd_cpu>;
134 regulator-coupled-max-spread = <300000>;
H A Dtegra30-asus-nexus7-grouper-maxim-pmic.dtsi69 regulator-coupled-with = <&vdd_core>;
70 regulator-coupled-max-spread = <300000>;
82 regulator-coupled-with = <&vdd_cpu>;
83 regulator-coupled-max-spread = <300000>;
H A Dtegra20-paz00.dts361 regulator-coupled-with = <&rtc_vdd_reg &cpu_vdd_reg>;
362 regulator-coupled-max-spread = <170000 550000>;
372 regulator-coupled-with = <&core_vdd_reg &rtc_vdd_reg>;
373 regulator-coupled-max-spread = <550000 550000>;
399 regulator-coupled-with = <&core_vdd_reg &cpu_vdd_reg>;
400 regulator-coupled-max-spread = <170000 550000>;
H A Dtegra20-ventana.dts406 regulator-coupled-with = <&rtc_vdd &vdd_cpu>;
407 regulator-coupled-max-spread = <170000 550000>;
418 regulator-coupled-with = <&vdd_core &rtc_vdd>;
419 regulator-coupled-max-spread = <550000 550000>;
446 regulator-coupled-with = <&vdd_core &vdd_cpu>;
447 regulator-coupled-max-spread = <170000 550000>;
/linux/arch/arm64/boot/dts/mediatek/
H A Dmt8390-grinn-genio-som.dtsi86 regulator-coupled-with = <&mt6359_vsram_others_ldo_reg>;
87 regulator-coupled-max-spread = <6250>;
110 regulator-coupled-with = <&mt6359_vproc2_buck_reg>;
111 regulator-coupled-max-spread = <6250>;
/linux/include/linux/input/
H A Dadxl34x.h93 * 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/arch/mips/include/asm/
H A Dpm-cps.h12 * 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/sound/hda/core/ext/
H A Dstream.c328 * @type: type of stream (coupled, host or link stream)
330 * This assigns the stream based on the type (coupled/host/link), for the
333 * coupled: Looks for an unused stream
372 * @type: type of stream (coupled, host or link stream)
/linux/net/sched/
H A Dact_gact.c28 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/Documentation/devicetree/bindings/media/i2c/
H A Dimi,rdacm2x-gmsl.yaml21 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/drivers/soc/samsung/
H A Dexynos-regulator-coupler.c72 * 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/Documentation/devicetree/bindings/mfd/
H A Dmaxim,max77802.yaml153 regulator-coupled-with = <&buck3_reg>;
154 regulator-coupled-max-spread = <300000>;
/linux/arch/csky/
H A DKconfig264 bool "Tightly-Coupled/Sram Memory"
267 The implementation are not only used by TCM (Tightly-Coupled Memory)
/linux/Documentation/arch/arm/
H A Dtcm.rst2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
/linux/include/linux/
H A Dexecmem.h141 * Allocates memory that will contain data coupled with executable code,
159 * Allocates memory that will contain data coupled with executable code,
/linux/drivers/iio/accel/
H A Dadxl313_core.c564 * for example, if an AC-coupled activity is active and the in adxl313_set_act_inact_en()
565 * current call attempts to turn off a DC-coupled activity, this in adxl313_set_act_inact_en()
1043 /* AC coupled */ in adxl313_push_events()
1053 /* DC coupled, relying on THRESH */ in adxl313_push_events()
1071 /* AC coupled */ in adxl313_push_events()
1081 /* DC coupled, relying on THRESH */ in adxl313_push_events()

123456