Searched refs:overcurrent (Results 1 – 25 of 25) sorted by relevance
| /Linux-v6.6/drivers/usb/host/ |
| D | ohci-omap.c | 48 struct gpio_desc *overcurrent; member
237 priv->overcurrent = devm_gpiod_get_optional(&pdev->dev, "overcurrent", in ohci_hcd_omap_probe()
239 if (IS_ERR(priv->overcurrent)) { in ohci_hcd_omap_probe()
240 retval = PTR_ERR(priv->overcurrent); in ohci_hcd_omap_probe()
243 if (priv->overcurrent) in ohci_hcd_omap_probe()
244 gpiod_set_consumer_name(priv->overcurrent, "OHCI overcurrent"); in ohci_hcd_omap_probe()
|
| /Linux-v6.6/Documentation/hwmon/ |
| D | ltc4245.rst | 67 curr1_max_alarm 12v overcurrent alarm
68 curr2_max_alarm 5v overcurrent alarm
69 curr3_max_alarm 3v overcurrent alarm
70 curr4_max_alarm Vee (-12v) overcurrent alarm
|
| D | pm6764tr.rst | 31 response. The device assures fast and independent protection against load overcurrent,
|
| D | ltc4215.rst | 55 curr1_max_alarm overcurrent alarm
|
| D | ltc2992.rst | 48 currX_max_alarm An overcurrent occurred. Cleared on read.
|
| D | ltc4260.rst | 63 curr1_alarm SENSE overcurrent alarm
|
| D | ltc4261.rst | 70 curr1_alarm SENSE overcurrent alarm
|
| D | lineage-pem.rst | 70 curr1_alarm Input overcurrent alarm
|
| /Linux-v6.6/Documentation/devicetree/bindings/regulator/ |
| D | tps65090.txt | 24 - ti,overcurrent-wait: This is applicable to FET registers, which have a
25 poorly defined "overcurrent wait" field. If this property is present it
27 "overcurrent wait" field and we'll leave it to the BIOS/EC to deal with.
|
| /Linux-v6.6/arch/arm/boot/dts/samsung/ |
| D | exynos5250-snow-common.dtsi | 131 ti,overcurrent-wait = <3>;
136 ti,overcurrent-wait = <3>;
141 ti,overcurrent-wait = <3>;
145 ti,overcurrent-wait = <3>;
150 ti,overcurrent-wait = <3>;
154 ti,overcurrent-wait = <3>;
159 ti,overcurrent-wait = <3>;
|
| D | exynos4212-tab3.dtsi | 160 maxim,battery-overcurrent-microamp = <3500000>;
|
| D | exynos4412-midas.dtsi | 243 maxim,battery-overcurrent-microamp = <3500000>;
|
| /Linux-v6.6/arch/arm64/boot/dts/broadcom/stingray/ |
| D | stingray-pinctrl.dtsi | 322 drdu2_pins: drdu2-overcurrent-pins {
331 drdu3_pins: drdu3-overcurrent-pins {
340 usb3h_pins: usb3h-overcurrent-pins {
|
| /Linux-v6.6/Documentation/devicetree/bindings/sound/ |
| D | st,sta350.txt | 63 - st,overcurrent-warning-adjustment:
64 If present, overcurrent warning adjustment is enabled.
|
| /Linux-v6.6/arch/arm/boot/dts/marvell/ |
| D | armada-388-helios4.dts | 157 * 5-USB3 overcurrent
195 line-name = "usb-overcurrent-status";
|
| D | armada-388-clearfog.dts | 66 * 5-USB3 overcurrent
|
| D | armada-388-clearfog.dtsi | 121 * 5-USB3 overcurrent
|
| /Linux-v6.6/Documentation/devicetree/bindings/usb/ |
| D | atmel-usb.txt | 19 activated for the overcurrent detection.
|
| /Linux-v6.6/arch/arm/boot/dts/renesas/ |
| D | r7s9210-rza2mevb.dts | 18 * - USB Channel 1 loses the overcurrent input signal.
|
| /Linux-v6.6/arch/arm64/boot/dts/ti/ |
| D | k3-am642-tqma64xxl-mbax4xxl.dts | 435 * The CDNS USB driver currently doesn't support overcurrent GPIOs,
436 * so there is no overcurrent detection. The OC pin is configured
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 425 /sys/devices/system/cpu/cpuX/cpufreq/throttle_stats/overcurrent
458 - overcurrent : This file gives the total number of times the
465 powercap, overtemp, supply_fault, overcurrent and occ_reset map to
475 /sys/devices/system/cpu/cpufreq/policyX/throttle_stats/overcurrent
|
| /Linux-v6.6/Documentation/power/regulator/ |
| D | overview.rst | 166 overvoltage or overcurrent caused by buggy client drivers. It also
|
| /Linux-v6.6/arch/arm/boot/dts/nxp/imx/ |
| D | imx6sx-softing-vining-2000.dts | 336 /* overcurrent detection */
|
| /Linux-v6.6/drivers/cpufreq/ |
| D | powernv-cpufreq.c | 411 throttle_attr(overcurrent, reason[OVERCURRENT]);
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | kernel-parameters.txt | 6704 [USB] Ignore overcurrent events (default N).
6708 Note that genuine overcurrent events won't be
|
