Searched +full:peak +full:- +full:to +full:- +full:peak (Results 1 – 25 of 485) sorted by relevance
12345678910>>...20
| /kernel/linux/linux-5.10/drivers/net/can/sja1000/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 10 tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card" 13 This driver is for the one, two or four channel CPC-PCI, 14 CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche 15 (http://www.ems-wuensche.de). 18 tristate "EMS CPC-CARD Card" 21 This driver is for the one or two channel CPC-CARD cards from 22 EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de). 25 tristate "Fintek F81601 PCIE to 2 CAN Controller" 28 This driver adds support for Fintek F81601 PCIE to 2 CAN [all …]
|
| /kernel/linux/linux-6.6/drivers/net/can/sja1000/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 10 tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card" 13 This driver is for the one, two or four channel CPC-PCI, 14 CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche 15 (http://www.ems-wuensche.de). 18 tristate "EMS CPC-CARD Card" 21 This driver is for the one or two channel CPC-CARD cards from 22 EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de). 25 tristate "Fintek F81601 PCIE to 2 CAN Controller" 28 This driver adds support for Fintek F81601 PCIE to 2 CAN [all …]
|
| /kernel/linux/linux-5.10/net/sched/ |
| D | sch_tbf.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later 6 * Dmitry Torokhov <dtor@mail.ru> - allow attaching inner qdiscs - 26 ------- 31 ------------ 35 does not exceed B + R*(t_f-t_i). 41 s_i+....+s_k <= B + R*(t_k - t_i) 44 ---------- 54 N(t_* + 0) = N(t_* - 0) - S/R. 58 Actually, QoS requires two TBF to be applied to a data stream. 60 one with rate P (peak rate) and depth M (equal to link MTU) [all …]
|
| /kernel/linux/linux-6.6/net/sched/ |
| D | sch_tbf.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later 6 * Dmitry Torokhov <dtor@mail.ru> - allow attaching inner qdiscs - 27 ------- 32 ------------ 36 does not exceed B + R*(t_f-t_i). 42 s_i+....+s_k <= B + R*(t_k - t_i) 45 ---------- 55 N(t_* + 0) = N(t_* - 0) - S/R. 59 Actually, QoS requires two TBF to be applied to a data stream. 61 one with rate P (peak rate) and depth M (equal to link MTU) [all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/ |
| D | cirrus,cs35l41.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - david.rhodes@cirrus.com 19 - cirrus,cs35l40 20 - cirrus,cs35l41 28 '#sound-dai-cells': 33 reset-gpios: 36 VA-supply: 39 VP-supply: [all …]
|
| D | cs35l34.txt | 5 - compatible : "cirrus,cs35l34" 7 - reg : the I2C address of the device for I2C. 9 - VA-supply, VP-supply : power supplies for the device, 13 - cirrus,boost-vtge-millivolt : Boost Voltage Value. Configures the boost 14 converter's output voltage in mV. The range is from VP to 8V with 17 - cirrus,boost-nanohenry: Inductor value for boost converter. The value is 22 - reset-gpios: GPIO used to reset the amplifier. 24 - interrupts : IRQ line info CS35L34. 25 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt 26 for further information relating to interrupt properties) [all …]
|
| D | cs35l36.txt | 5 - compatible : "cirrus,cs35l36" 7 - reg : the I2C address of the device for I2C 9 - VA-supply, VP-supply : power supplies for the device, 13 - cirrus,boost-ctl-millivolt : Boost Voltage Value. Configures the boost 14 converter's output voltage in mV. The range is from 2550mV to 12000mV with 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. 20 Range starts at 1600mA and goes to a maximum of 4500mA with increments of 24 - cirrus,boost-ind-nanohenry : Inductor estimation LBST reference value. 26 inductance value to reference. [all …]
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/qcom/ |
| D | sdm660.dtsi | 1 // SPDX-License-Identifier: GPL-2.0-only 13 compatible = "qcom,adreno-512.0", "qcom,adreno"; 14 operating-points-v2 = <&gpu_sdm660_opp_table>; 16 gpu_sdm660_opp_table: opp-table { 17 compatible = "operating-points-v2"; 21 * Though it cannot be used for now due to interconnect 23 * at the same opp-level 25 opp-750000000 { 26 opp-hz = /bits/ 64 <750000000>; 27 opp-level = <RPM_SMD_LEVEL_TURBO>; [all …]
|
| D | sm6350.dtsi | 1 // SPDX-License-Identifier: BSD-3-Clause 7 #include <dt-bindings/clock/qcom,dispcc-sm6350.h> 8 #include <dt-bindings/clock/qcom,gcc-sm6350.h> 9 #include <dt-bindings/clock/qcom,gpucc-sm6350.h> 10 #include <dt-bindings/clock/qcom,rpmh.h> 11 #include <dt-bindings/clock/qcom,sm6350-camcc.h> 12 #include <dt-bindings/dma/qcom-gpi.h> 13 #include <dt-bindings/gpio/gpio.h> 14 #include <dt-bindings/interconnect/qcom,icc.h> 15 #include <dt-bindings/interconnect/qcom,osm-l3.h> [all …]
|
| /kernel/linux/linux-5.10/drivers/net/can/usb/peak_usb/ |
| D | pcan_usb_core.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 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> 9 * Many thanks to Klaus Hitschler <klaus.hitschler@gmx.de> 14 /* PEAK-System vendor id. */ 34 /* maximum length of the usb commands sent to/received from the devices */ 39 /* PEAK-System USB adapter descriptor */ 108 /* PEAK-System USB device */
|
| /kernel/linux/linux-6.6/drivers/net/can/usb/peak_usb/ |
| D | pcan_usb_core.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 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> 9 * Many thanks to Klaus Hitschler <klaus.hitschler@gmx.de> 14 /* PEAK-System vendor id. */ 34 /* maximum length of the usb commands sent to/received from the devices */ 39 /* PEAK-System USB adapter descriptor */ 109 /* PEAK-System USB device */ 126 /* equivalent to the device ID in the Windows API */ [all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/ |
| D | transmit-amplitude.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/phy/transmit-amplitude.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 Binding describing the peak-to-peak transmit amplitude for common PHYs 14 - Marek Behún <kabel@kernel.org> 17 tx-p2p-microvolt: 19 Transmit amplitude voltages in microvolts, peak-to-peak. If this property 21 'tx-p2p-microvolt-names' property must be provided and contain 24 tx-p2p-microvolt-names: [all …]
|
| /kernel/liteos_a/kernel/extended/plimit/ |
| D | los_memlimit.c | 2 * Copyright (c) 2022-2022 Huawei Device Co., Ltd. All rights reserved. 15 * to endorse or promote products derived from this software without specific prior written 19 * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, 23 * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, 44 procMemLimiter->limit = OS_NULL_INT; in OsMemLimiterInit() 50 g_procMemLimiter->limit = limit; in OsMemLimitSetLimit() 77 plimiteDest->limit = plimiteSrc->limit; in OsMemLimiterCopy() 85 if ((currMemLimit->usage + parentMemLimit->usage) >= parentMemLimit->limit) { in MemLimiteMigrateCheck() 98 parentMemLimit->usage += currMemLimit->usage; in OsMemLimiterMigrate() 99 parentMemLimit->failcnt += currMemLimit->failcnt; in OsMemLimiterMigrate() [all …]
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/nvidia/ |
| D | tegra234.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 3 #include <dt-bindings/clock/tegra234-clock.h> 4 #include <dt-bindings/gpio/tegra234-gpio.h> 5 #include <dt-bindings/interrupt-controller/arm-gic.h> 6 #include <dt-bindings/mailbox/tegra186-hsp.h> 7 #include <dt-bindings/memory/tegra234-mc.h> 8 #include <dt-bindings/pinctrl/pinctrl-tegra-io-pad.h> 9 #include <dt-bindings/power/tegra234-powergate.h> 10 #include <dt-bindings/reset/tegra234-reset.h> 11 #include <dt-bindings/thermal/tegra234-bpmp-thermal.h> [all …]
|
| /kernel/linux/linux-6.6/drivers/net/can/peak_canfd/ |
| D | peak_canfd_user.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 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> 12 #define PCANFD_ECHO_SKB_DEF -1 14 /* data structure private to each uCAN interface */ 16 struct can_priv can; /* socket-can private data */
|
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 4 tristate "PEAK-System PCAN-PCIe FD cards" 6 This driver adds support for the PEAK-System PCI Express FD 7 CAN-FD cards family. 8 These 1x or 2x CAN-FD channels cards offer CAN 2.0 a/b as well as 9 CAN-FD access to the CAN bus. Besides the nominal bitrate of up to 10 1 Mbit/s, the data bytes of CAN-FD frames can be transmitted with 11 up to 12 Mbit/s. A galvanic isolation of the CAN ports protects the 13 disturbances of up to 500 Volts. The PCAN-PCI Express FD can be 14 operated with ambient temperatures in a range of -40 to +85 °C.
|
| /kernel/linux/linux-5.10/drivers/net/can/peak_canfd/ |
| D | peak_canfd_user.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 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> 12 #define PCANFD_ECHO_SKB_DEF -1 14 /* data structure private to each uCAN interface */ 16 struct can_priv can; /* socket-can private data */
|
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 4 tristate "PEAK-System PCAN-PCIe FD cards" 6 This driver adds support for the PEAK-System PCI Express FD 7 CAN-FD cards family. 8 These 1x or 2x CAN-FD channels cards offer CAN 2.0 a/b as well as 9 CAN-FD access to the CAN bus. Besides the nominal bitrate of up to 10 1 Mbit/s, the data bytes of CAN-FD frames can be transmitted with 11 up to 12 Mbit/s. A galvanic isolation of the CAN ports protects the 13 disturbances of up to 500 Volts. The PCAN-PCI Express FD can be 14 operated with ambient temperatures in a range of -40 to +85 °C.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | cs35l34.txt | 5 - compatible : "cirrus,cs35l34" 7 - reg : the I2C address of the device for I2C. 9 - VA-supply, VP-supply : power supplies for the device, 13 - cirrus,boost-vtge-millivolt : Boost Voltage Value. Configures the boost 14 converter's output voltage in mV. The range is from VP to 8V with 17 - cirrus,boost-nanohenry: Inductor value for boost converter. The value is 22 - reset-gpios: GPIO used to reset the amplifier. 24 - interrupts : IRQ line info CS35L34. 25 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt 26 for further information relating to interrupt properties) [all …]
|
| D | cs35l36.txt | 5 - compatible : "cirrus,cs35l36" 7 - reg : the I2C address of the device for I2C 9 - VA-supply, VP-supply : power supplies for the device, 13 - cirrus,boost-ctl-millivolt : Boost Voltage Value. Configures the boost 14 converter's output voltage in mV. The range is from 2550mV to 12000mV with 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. 20 Range starts at 1600mA and goes to a maximum of 4500mA with increments of 24 - cirrus,boost-ind-nanohenry : Inductor estimation LBST reference value. 26 inductance value to reference. [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/msm/ |
| D | gpu.txt | 4 - compatible: "qcom,adreno-XYZ.W", "qcom,adreno" or 5 "amd,imageon-XYZ.W", "amd,imageon" 6 for example: "qcom,adreno-306.0", "qcom,adreno" 7 Note that you need to list the less specific "qcom,adreno" (since this 8 is what the device is matched on), in addition to the more specific 9 with the chip-id. 11 - reg: Physical base address and length of the controller's registers. 12 - interrupts: The interrupt signal from the gpu. 13 - clocks: device clocks (if applicable) 14 See ../clocks/clock-bindings.txt for details. [all …]
|
| /kernel/linux/linux-5.10/drivers/nfc/fdp/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 8 Intel Fields Peak NFC controller core driver. 11 To compile this driver as a module, choose m here. The module will 19 This module adds support for the Intel Fields Peak NFC controller 23 If you choose to build a module, it'll be called fdp_i2c.
|
| /kernel/linux/linux-6.6/drivers/nfc/fdp/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 8 Intel Fields Peak NFC controller core driver. 11 To compile this driver as a module, choose m here. The module will 19 This module adds support for the Intel Fields Peak NFC controller 23 If you choose to build a module, it'll be called fdp_i2c.
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| 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 8 identifiers. Contrary to a USB serial number, these identifiers 12 This attribute provides read-only access to the currently 18 set to zero.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Viresh Kumar <viresh.kumar@linaro.org> 13 Devices work at voltage-current-frequency combinations and some implementations 19 This describes the OPPs belonging to a device. 25 pattern: '^opp-table(-[a-z0-9]+)?$' 27 opp-shared: 36 '^opp(-?[0-9]+)*$': [all …]
|
12345678910>>...20