Home
last modified time | relevance | path

Searched full:throttle (Results 1 – 25 of 393) sorted by relevance

12345678910>>...16

/Linux-v6.6/Documentation/devicetree/bindings/thermal/
Dnvidia,tegra124-soctherm.yaml62 throttle-cfgs:
65 hardware throttle events. These events can be set as cooling devices.
66 Throttle event sub-nodes must be named as "light" or "heavy".
76 description: Each throttles has its own throttle settings, so the
77 SW need to set priorities for various throttle, the HW arbiter
78 can select the final throttle settings. Bigger value indicates
94 of pulse skippers, which used to throttle clock frequencies. It
110 level of pulse skippers, which used to throttle clock
125 # Tegra210 specific and valid only for OCx throttle events
145 nvidia,throttle-period-us:
[all …]
/Linux-v6.6/drivers/thermal/
Dgov_step_wise.c31 enum thermal_trend trend, bool throttle) in get_target_state() argument
47 if (throttle) { in get_target_state()
56 if (throttle) { in get_target_state()
87 bool throttle = false; in thermal_zone_trip_update() local
95 throttle = true; in thermal_zone_trip_update()
99 dev_dbg(&tz->device, "Trip%d[type=%d,temp=%d]:trend=%d,throttle=%d\n", in thermal_zone_trip_update()
100 trip_id, trip.type, trip.temperature, trend, throttle); in thermal_zone_trip_update()
107 instance->target = get_target_state(instance, trend, throttle); in thermal_zone_trip_update()
135 * Throttling Logic: This uses the trend of the thermal zone to throttle.
157 .throttle = step_wise_throttle,
Dgov_fair_share.c55 * throttle state of the cooling devices associated with the given zone.
58 * P1. max_state: Maximum throttle state exposed by the cooling device.
63 * We do not want to throttle too much when we trip a lower temperature,
110 .throttle = fair_share_throttle,
DKconfig202 idle injection. This will throttle the CPU by injecting
214 This will throttle the device by limiting the maximum allowed DVFS
253 thermal framework. cpufreq is used as the cooling device to throttle
265 cpufreq is used as the cooling device to throttle CPUs when the
286 cpufreq is used as the cooling device to throttle CPUs when the passive
317 cpufreq is used as the cooling device to throttle CPUs when the
351 trip point. Cpufreq is used as the cooling device and will throttle
/Linux-v6.6/Documentation/admin-guide/cgroup-v1/
Dblkio-controller.rst38 echo "8:16 1048576" > /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device
50 Limits for writes can be put using blkio.throttle.write_bps_device file.
252 blkio.throttle.read_bps_device
257 echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.read_bps_device
259 blkio.throttle.write_bps_device
264 echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.write_bps_device
266 blkio.throttle.read_iops_device
271 echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.read_iops_device
273 blkio.throttle.write_iops_device
278 echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.write_iops_device
[all …]
/Linux-v6.6/include/linux/
Ddm-kcopyd.h27 unsigned int throttle; member
45 module_param_named(name, dm_kcopyd_throttle.throttle, uint, 0644); \
50 * throttle can be NULL if you don't want any throttling.
53 struct dm_kcopyd_client *dm_kcopyd_client_create(struct dm_kcopyd_throttle *throttle);
/Linux-v6.6/drivers/gpu/drm/amd/include/
Dkgd_pp_interface.h477 /* Throttle status */
529 /* Throttle status */
588 /* Throttle status (ASIC dependent) */
650 /* Throttle status */
677 /* Throttle status (ASIC independent) */
726 /* Throttle status */
776 /* Throttle status */
826 /* Throttle status (ASIC dependent) */
834 /* Throttle status (ASIC independent) */
879 /* Throttle status (ASIC dependent) */
[all …]
/Linux-v6.6/drivers/tty/serial/8250/
D8250_aspeed_vuart.c44 * If we fill the tty flip buffers, we throttle the data ready interrupt
274 bool throttle) in __aspeed_vuart_set_throttle() argument
282 if (!throttle) in __aspeed_vuart_set_throttle()
286 static void aspeed_vuart_set_throttle(struct uart_port *port, bool throttle) in aspeed_vuart_set_throttle() argument
292 __aspeed_vuart_set_throttle(up, throttle); in aspeed_vuart_set_throttle()
322 * have throttle/unthrottle callbacks, we've seen that the VUART device can
324 * against the throttle threshold. This results in dropped characters before
325 * the throttle.
328 * throttle now and schedule an unthrottle for later, once the ldisc has had
351 /* throttle and schedule an unthrottle later */ in aspeed_vuart_handle_irq()
[all …]
/Linux-v6.6/drivers/thermal/tegra/
Dsoctherm.c497 * throttrip_program() - Configures the hardware to throttle the
501 * @stc: pointer to the throttle need to be triggered
504 * Sets the thermal trip threshold and throttle event of the given sensor
506 * throttle.
717 * "THROTTLE" trip points , using "thermtrips", "critical" or "hot"
720 * After they have been configured, THERMTRIP or THROTTLE will take
730 * THROTTLE has been enabled successfully when a message similar to
732 * ""throttrip: will throttle when sensor group XXX reaches YYYYYY mC"
784 "throttrip: will throttle when %s reaches %d mC\n", in tegra_soctherm_set_hwtrips()
790 dev_info(dev, "throttrip: %s: missing throttle cdev\n", in tegra_soctherm_set_hwtrips()
[all …]
/Linux-v6.6/Documentation/ABI/testing/
Dsysfs-driver-intel-i915-hwmon15 The power controller will throttle the operating frequency
47 for client products. The power controller will throttle the
60 exposed for server products. The power controller will throttle
Dsysfs-devices-system-cpu430 Description: POWERNV CPUFreq driver's frequency throttle stats directory and
434 throttle stat attributes for the chip. The throttle stats of a cpu
436 throttle attributes exported in the 'throttle_stats' directory:
464 The sysfs attributes representing different throttle reasons like
480 Description: POWERNV CPUFreq driver's frequency throttle stats directory and
485 attributes which give the frequency throttle information of the chip.
/Linux-v6.6/drivers/md/
Ddm-kcopyd.c75 struct dm_kcopyd_throttle *throttle; member
125 unsigned int throttle, now, difference; in io_job_start() local
134 throttle = READ_ONCE(t->throttle); in io_job_start()
136 if (likely(throttle >= 100)) in io_job_start()
159 skew = t->io_period - throttle * t->total_period / 100; in io_job_start()
185 if (likely(READ_ONCE(t->throttle) >= 100)) in io_job_finish()
525 io_job_finish(kc->throttle); in complete_io()
578 io_job_start(job->kc->throttle); in run_io_job()
915 struct dm_kcopyd_client *dm_kcopyd_client_create(struct dm_kcopyd_throttle *throttle) in dm_kcopyd_client_create() argument
930 kc->throttle = throttle; in dm_kcopyd_client_create()
/Linux-v6.6/tools/perf/pmu-events/arch/x86/jaketown/
Duncore-memory.json232 "BriefDescription": "Critical Throttle Cycles",
248 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
257 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
266 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
275 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
284 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
293 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
302 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
311 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
/Linux-v6.6/block/
Dblk-iolatency.c9 * - We will throttle all IO that comes in here if we need to.
15 * throttle time do we pay attention to the actual queue depth.
32 * an average latency of 5ms. If it does then we will throttle the "slow"
34 * throttle "unloved", but nobody else.
41 * There are 2 ways we throttle IO.
43 * 1) Queue depth throttling. As we throttle down we will adjust the maximum
46 * only way we throttle.
57 * and then at throttle time will do
61 * This induced delay will throttle back the activity that is generating the
353 * dig out of it. Just enough that we don't throttle/unthrottle in scale_cookie_change()
[all …]
Dblk-rq-qos.c65 if (rqos->ops->throttle) in __rq_qos_throttle()
66 rqos->ops->throttle(rqos, bio); in __rq_qos_throttle()
228 * rq_qos_wait - throttle on a rqw if we need to
229 * @rqw: rqw to throttle on
Dblk-throttle.c16 #include "blk-throttle.h"
41 /* A workqueue to queue throttle related work */
583 * Since we are adjusting the throttle limit dynamically, the sleep in throtl_schedule_pending_timer()
844 /* Round up to the next throttle slice, wait time must be nonzero */ in tg_within_iops_limit()
865 /* no need to throttle if this bio's bytes have been accounted */ in tg_within_bps_limit()
929 * long since now. New slice is started only for empty throttle group. in tg_may_dispatch()
1328 * blk-throttle. in tg_conf_updated()
1444 .name = "throttle.read_bps_device",
1450 .name = "throttle.write_bps_device",
1456 .name = "throttle.read_iops_device",
[all …]
/Linux-v6.6/arch/arm/boot/dts/rockchip/
Drk3288-veyron-mickey.dts85 * After 1st level, throttle the CPU down to as low as 1.4 GHz
180 /* After 1st level throttle the GPU down to as low as 400 MHz */
187 * Slightly after we throttle the GPU, we'll also make sure that
189 * throttle the CPU lower than 1.4 GHz due to GPU heat--we'll
/Linux-v6.6/Documentation/devicetree/bindings/display/msm/
Dqcom,sc7180-dpu.yaml41 - description: Display core throttle clock
52 - const: throttle
/Linux-v6.6/drivers/cpufreq/
Dpowernv-cpufreq.c137 struct work_struct throttle; member
845 pr_info("Failed to create throttle stats directory for cpu %d\n", in powernv_cpufreq_cpu_init()
917 struct chip *chip = container_of(work, struct chip, throttle); in powernv_cpufreq_work_fn()
964 * target() callback which can detect the throttle state in powernv_cpufreq_occ_msg()
989 schedule_work(&chips[i].throttle); in powernv_cpufreq_occ_msg()
1008 schedule_work(&chips[i].throttle); in powernv_cpufreq_occ_msg()
1083 INIT_WORK(&chips[i].throttle, powernv_cpufreq_work_fn); in init_chip_info()
1102 cancel_work_sync(&chips[i].throttle); in clean_chip_info()
/Linux-v6.6/tools/perf/pmu-events/arch/x86/snowridgex/
Duncore-memory.json256 "BriefDescription": "Throttle Cycles for Rank 0",
260 …"PublicDescription": "Throttle Cycles for Rank 0 : Counts the number of cycles while the iMC is be…
265 "BriefDescription": "Throttle Cycles for Rank 0",
269 …"PublicDescription": "Throttle Cycles for Rank 0 : Counts the number of cycles while the iMC is be…
284 "BriefDescription": "Throttle Cycles for Rank 0",
288 …"PublicDescription": "Throttle Cycles for Rank 0 : Counts the number of cycles while the iMC is be…
293 "BriefDescription": "Throttle Cycles for Rank 0",
297 …"PublicDescription": "Throttle Cycles for Rank 0 : Counts the number of cycles while the iMC is be…
/Linux-v6.6/drivers/scsi/mpi3mr/
Dmpi3mr.h453 * struct mpi3mr_throttle_group_info - Throttle group info
460 * @id: Throttle Group ID.
637 * @tg_id: VDs throttle group ID
640 * @tg: Pointer to throttle group info
765 * @throttle_group: Pointer to throttle group info
1030 * @io_throttle_high: I/O size to start throttle in 512b blocks
1031 * @io_throttle_low: I/O size to stop throttle in 512b blocks
1032 * @num_io_throttle_group: Maximum number of throttle groups
1033 * @throttle_groups: Pointer to throttle group info structures
/Linux-v6.6/drivers/net/wireless/intel/iwlwifi/mvm/
Dtt.c25 tt->throttle = false; in iwl_mvm_enter_ctkill()
447 if (!tt->throttle && throttle_enable) { in iwl_mvm_tt_handler()
450 tt->throttle = true; in iwl_mvm_tt_handler()
451 } else if (tt->throttle && !tt->dynamic_smps && in iwl_mvm_tt_handler()
456 tt->throttle = false; in iwl_mvm_tt_handler()
836 tt->throttle = false; in iwl_mvm_thermal_initialize()
/Linux-v6.6/drivers/usb/serial/
Dbelkin_sa.h84 #define BELKIN_SA_FLOW_OCTS 0x0001 /* use CTS input to throttle output */
85 #define BELKIN_SA_FLOW_ODSR 0x0002 /* use DSR input to throttle output */
/Linux-v6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a53/
Dcache.json10 "BriefDescription": "Instruction Cache Throttle occurred"
/Linux-v6.6/Documentation/block/
Dkyber-iosched.rst6 reads and synchronous writes. Kyber will throttle requests in order to meet

12345678910>>...16