/linux/arch/arm64/boot/dts/qcom/ |
H A D | sa8540p.dtsi | 19 opp-peak-kBps = <(300000 * 32)>; 23 opp-peak-kBps = <(384000 * 32)>; 27 opp-peak-kBps = <(480000 * 32)>; 31 opp-peak-kBps = <(576000 * 32)>; 35 opp-peak-kBps = <(672000 * 32)>; 39 opp-peak-kBps = <(768000 * 32)>; 43 opp-peak-kBps = <(864000 * 32)>; 47 opp-peak-kBps = <(960000 * 32)>; 51 opp-peak-kBps = <(1075200 * 32)>; 55 opp-peak-kBps = <(1171200 * 32)>; [all …]
|
H A D | msm8996pro.dtsi | 27 opp-peak-kBps = <192000>; 33 opp-peak-kBps = <192000>; 39 opp-peak-kBps = <192000>; 45 opp-peak-kBps = <192000>; 51 opp-peak-kBps = <192000>; 57 opp-peak-kBps = <307200>; 63 opp-peak-kBps = <307200>; 69 opp-peak-kBps = <384000>; 75 opp-peak-kBps = <441600>; 81 opp-peak-kBps = <537600>; [all …]
|
H A D | sc7180-lite.dtsi | 9 opp-peak-kBps = <7216000 22425600>; 13 opp-peak-kBps = <7216000 22425600>; 17 opp-peak-kBps = <8532000 23347200>; 21 opp-peak-kBps = <8532000 23347200>; 25 opp-peak-kBps = <8532000 23347200>;
|
H A D | sdm850.dtsi | 13 opp-peak-kBps = <7216000 25497600>; 18 opp-peak-kBps = <7216000 25497600>;
|
H A D | qcm2290.dtsi | 782 opp-peak-kBps = <(200 * 4 * 1000)>; 786 opp-peak-kBps = <(300 * 4 * 1000)>; 790 opp-peak-kBps = <(451 * 4 * 1000)>; 794 opp-peak-kBps = <(547 * 4 * 1000)>; 798 opp-peak-kBps = <(681 * 4 * 1000)>; 802 opp-peak-kBps = <(768 * 4 * 1000)>; 806 opp-peak-kBps = <(1017 * 4 * 1000)>; 810 opp-peak-kBps = <(1353 * 4 * 1000)>; 814 opp-peak-kBps = <(1555 * 4 * 1000)>; 818 opp-peak-kBps = <(1804 * 4 * 1000)>; [all …]
|
/linux/tools/testing/selftests/cgroup/ |
H A D | test_memcontrol.c | 164 * and checks memory.current, memory.peak, and some memory.stat values. 169 long current, peak, peak_reset; in test_memcg_current_peak() local 186 peak = cg_read_long(memcg, "memory.peak"); in test_memcg_current_peak() 187 if (peak != 0) in test_memcg_current_peak() 193 peak = cg_read_long(memcg, "memory.peak"); in test_memcg_current_peak() 194 if (peak < MB(50)) in test_memcg_current_peak() 198 * We'll open a few FDs for the same memory.peak file to exercise the free-path in test_memcg_current_peak() 202 peak_fd = cg_open(memcg, "memory.peak", O_RDWR | O_APPEND | O_CLOEXEC); in test_memcg_current_peak() 211 * Before we try to use memory.peak's fd, try to figure out whether in test_memcg_current_peak() 223 peak_fd2 = cg_open(memcg, "memory.peak", O_RDWR | O_APPEND | O_CLOEXEC); in test_memcg_current_peak() [all …]
|
/linux/drivers/net/can/sja1000/ |
H A D | Kconfig | 42 tristate "PEAK PCAN-PCI/PCIe/miniPCI Cards" 46 (1, 2, 3 or 4 channels) from PEAK-System Technik 47 (http://www.peak-system.com). 50 bool "PEAK PCAN-ExpressCard Cards" 56 Say Y here if you want to use a PCAN-ExpressCard from PEAK-System 61 tristate "PEAK PCAN-PC Card" 66 from PEAK-System (http://www.peak-system.com). To compile this
|
H A D | peak_pcmcia.c | 3 * Copyright (C) 2010-2012 Stephane Grosjean <s.grosjean@peak-system.com> 5 * CAN driver for PEAK-System PCAN-PC Card 7 * Copyright (C) 2006-2010 PEAK System-Technik GmbH 22 MODULE_AUTHOR("Stephane Grosjean <s.grosjean@peak-system.com>"); 23 MODULE_DESCRIPTION("CAN driver for PEAK-System PCAN-PC Cards"); 26 /* PEAK-System PCMCIA driver name */ 625 * setup PCMCIA socket and probe for PEAK-System PC-CARD 674 dev_info(&pdev->dev, "PEAK-System pcmcia card %s fw %d.%d\n", in pcan_probe()
|
/linux/arch/arm/boot/dts/nvidia/ |
H A D | tegra124-peripherals-opp.dtsi | 336 opp-peak-kBps = <204000>; 342 opp-peak-kBps = <326400>; 348 opp-peak-kBps = <652800>; 354 opp-peak-kBps = <1088000>; 360 opp-peak-kBps = <1632000>; 366 opp-peak-kBps = <3264000>; 373 opp-peak-kBps = <4224000>; 379 opp-peak-kBps = <4800000>; 385 opp-peak-kBps = <5568000>; 391 opp-peak-kBps = <6336000>; [all …]
|
H A D | tegra30-peripherals-opp.dtsi | 395 opp-peak-kBps = <102000>; 401 opp-peak-kBps = <204000>; 407 opp-peak-kBps = <216000>; 413 opp-peak-kBps = <408000>; 419 opp-peak-kBps = <432000>; 425 opp-peak-kBps = <816000>; 431 opp-peak-kBps = <864000>; 437 opp-peak-kBps = <1632000>; 444 opp-peak-kBps = <2132000>; 450 opp-peak-kBps = <2668000>; [all …]
|
/linux/net/sched/ |
H A D | sch_tbf.c | 61 one with rate P (peak rate) and depth M (equal to link MTU) 89 Note that the peak rate TBF is much more tough: with MTU 1500 90 P_crit = 150Kbytes/sec. So, if you need greater peak 105 struct psched_ratecfg peak; member 272 return q->peak.rate_bytes_ps; in tbf_peak_present() 295 ptoks -= (s64) psched_l2t_ns(&q->peak, len); in tbf_dequeue() 366 struct psched_ratecfg peak; in tbf_change() local 408 psched_ratecfg_precompute(&peak, &qopt->peakrate, prate64); in tbf_change() 409 if (peak.rate_bytes_ps <= rate.rate_bytes_ps) { in tbf_change() 411 peak.rate_bytes_ps, rate.rate_bytes_ps); in tbf_change() [all …]
|
/linux/arch/arm64/boot/dts/nvidia/ |
H A D | tegra132-peripherals-opp.dtsi | 338 opp-peak-kBps = <204000>; 344 opp-peak-kBps = <326400>; 350 opp-peak-kBps = <652800>; 356 opp-peak-kBps = <1088000>; 362 opp-peak-kBps = <1632000>; 368 opp-peak-kBps = <3264000>; 375 opp-peak-kBps = <4224000>; 381 opp-peak-kBps = <4800000>; 387 opp-peak-kBps = <5568000>; 393 opp-peak-kBps = <6336000>; [all …]
|
/linux/Documentation/devicetree/bindings/sound/ |
H A D | cirrus,cs35l41.yaml | 42 cirrus,boost-peak-milliamp: 44 Boost-converter peak current limit in mA. 45 Configures the peak current by monitoring the current through the boost FET. 84 Internal boost requires boost-peak-milliamp, boost-ind-nanohenry and 93 boost-peak-milliamp, boost-ind-nanohenry and boost-cap-microfarad. 167 - cirrus,boost-peak-milliamp 180 cirrus,boost-peak-milliamp: false 205 cirrus,boost-peak-milliamp = <4500>;
|
H A D | cs35l34.txt | 28 - cirrus,boost-peak-milliamp : Boost converter peak current limit in mA. The 61 cirrus,boost-peak-milliamp = <3000>; /* 3A */
|
H A D | cs35l36.txt | 18 - cirrus,boost-peak-milliamp : Boost-converter peak current limit in mA. 19 Configures the peak current by monitoring the current through the boost FET. 149 cirrus,boost-peak-milliamp = <4500>;
|
/linux/drivers/net/can/usb/peak_usb/ |
H A D | pcan_usb_core.h | 3 * CAN driver for PEAK System USB adapters 6 * Copyright (C) 2003-2010 PEAK System-Technik GmbH 7 * Copyright (C) 2010-2012 Stephane Grosjean <s.grosjean@peak-system.com> 14 /* PEAK-System vendor id. */ 39 /* PEAK-System USB adapter descriptor */ 109 /* PEAK-System USB device */
|
H A D | pcan_usb_pro.h | 3 * CAN driver for PEAK System PCAN-USB Pro adapter 6 * Copyright (C) 2003-2011 PEAK System-Technik GmbH 7 * Copyright (C) 2011-2012 Stephane Grosjean <s.grosjean@peak-system.com>
|
/linux/Documentation/devicetree/bindings/phy/ |
H A D | transmit-amplitude.yaml | 10 Binding describing the peak-to-peak transmit amplitude for common PHYs 19 Transmit amplitude voltages in microvolts, peak-to-peak. If this property
|
/linux/drivers/net/can/peak_canfd/ |
H A D | peak_canfd_user.h | 2 /* CAN driver for PEAK System micro-CAN based adapters 4 * Copyright (C) 2003-2011 PEAK System-Technik GmbH 5 * Copyright (C) 2011-2013 Stephane Grosjean <s.grosjean@peak-system.com>
|
H A D | Kconfig | 4 tristate "PEAK-System PCAN-PCIe FD cards" 6 This driver adds support for the PEAK-System PCI Express FD
|
/linux/include/media/i2c/ |
H A D | lm3560.h | 71 * @peak : peak current 77 enum lm3560_peak_current peak; member
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-iio-accel-adxl372 | 1 What: /sys/bus/iio/devices/triggerX/name = "adxl372-devX-peak" 6 which sets the device in a mode in which it will record only the peak acceleration
|
H A D | sysfs-class-net-peak_usb | 5 Contact: Stephane Grosjean <s.grosjean@peak-system.com> 7 PEAK PCAN-USB devices support user-configurable CAN channel
|
/linux/Documentation/devicetree/bindings/opp/ |
H A D | opp-v2-base.yaml | 124 opp-peak-kBps: 126 Peak bandwidth in kilobytes per second, expressed as an array of 128 peak bandwidth value of each interconnect path. The number of elements 139 meaningful in OPP tables where opp-peak-kBps is present. 240 opp-avg-kBps: [ opp-peak-kBps ]
|
/linux/drivers/nfc/fdp/ |
H A D | Kconfig | 8 Intel Fields Peak NFC controller core driver. 19 This module adds support for the Intel Fields Peak NFC controller
|