| /linux/drivers/cpuidle/ |
| H A 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 …]
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A 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>;
|
| H A D | regulator.yaml | 228 regulator-coupled-with: 229 description: Regulators with which the regulator is coupled. The linkage 230 is 2-way - all coupled regulators should be linked with each other. 231 A regulator should not be coupled with its supplier. 236 regulator-coupled-max-spread: 237 description: Array of maximum spread between voltages of coupled regulators 239 couple specified by the regulator-coupled-with property.
|
| /linux/include/linux/regulator/ |
| H A D | coupler.h | 24 * @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/Documentation/devicetree/bindings/sound/ |
| H A 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
|
| /linux/drivers/regulator/ |
| H A D | of_regulator.c | 93 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/arch/mips/include/asm/ |
| H A 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/include/linux/input/ |
| H A 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/arch/arm/boot/dts/nvidia/ |
| H A D | tegra20-ventana.dts | 406 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>;
|
| H A D | tegra30-cardhu.dtsi | 285 regulator-coupled-with = <&vdd_core>; 286 regulator-coupled-max-spread = <300000>; 366 regulator-coupled-with = <&vddctrl_reg>; 367 regulator-coupled-max-spread = <300000>;
|
| /linux/sound/hda/core/ext/ |
| H A D | stream.c | 328 * @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/drivers/iio/accel/ |
| H A D | adxl345_core.c | 514 * Note: Activity and inactivity can be either AC coupled or DC coupled not 531 * A setting of false selects dc-coupled operation, and a setting of in adxl345_set_act_inact_ac() 532 * true enables ac-coupled operation. In dc-coupled operation, the in adxl345_set_act_inact_ac() 537 * In ac-coupled operation for activity detection, the acceleration in adxl345_set_act_inact_ac() 544 * Similarly, in ac-coupled operation for inactivity detection, a in adxl345_set_act_inact_ac() 691 * for example, if an AC-coupled activity is active and the in adxl345_set_act_inact_en() 692 * current call attempts to turn off a DC-coupled activity, this in adxl345_set_act_inact_en() 1711 /* AC coupled */ in adxl345_push_event() 1719 /* DC coupled, relying on THRESH */ in adxl345_push_event() 1736 /* AC coupled */ in adxl345_push_event() [all …]
|
| /linux/net/sched/ |
| H A 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/Documentation/devicetree/bindings/media/i2c/ |
| H A 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/drivers/soc/samsung/ |
| H A 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/Documentation/devicetree/bindings/mfd/ |
| H A D | maxim,max77802.yaml | 153 regulator-coupled-with = <&buck3_reg>; 154 regulator-coupled-max-spread = <300000>;
|
| /linux/arch/csky/ |
| H A D | Kconfig | 264 bool "Tightly-Coupled/Sram Memory" 267 The implementation are not only used by TCM (Tightly-Coupled Memory)
|
| /linux/Documentation/devicetree/bindings/serial/ |
| H A D | arm,dcc.yaml | 14 via JTAG can be also used as one of serial line tightly coupled with every
|
| /linux/tools/testing/selftests/riscv/hwprobe/ |
| H A D | hwprobe.h | 19 * ourselves. This way we don't need to be coupled to a new-enough libc to
|
| /linux/Documentation/arch/arm/ |
| H A 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/include/linux/ |
| H A D | execmem.h | 141 * Allocates memory that will contain data coupled with executable code, 159 * Allocates memory that will contain data coupled with executable code,
|
| H A D | clockchips.h | 76 * @set_next_coupled: set next event function for clocksource coupled mode 84 * @cs_id: Clocksource ID to denote the clocksource for coupled mode
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | arm,nvic.yaml | 13 The NVIC provides an interrupt controller that is tightly coupled to Cortex-M
|
| /linux/Documentation/driver-api/pm/ |
| H A 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/arch/arm64/boot/dts/allwinner/ |
| H A D | sun50i-h6-orangepi-lite2.dts | 44 * enable of coupled regulators, keep them
|