/openbmc/linux/drivers/usb/host/ |
H A 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()
|
/openbmc/linux/Documentation/hwmon/ |
H A 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
|
H A D | pm6764tr.rst | 31 response. The device assures fast and independent protection against load overcurrent,
|
H A D | ltc4215.rst | 55 curr1_max_alarm overcurrent alarm
|
H A D | ltc2992.rst | 48 currX_max_alarm An overcurrent occurred. Cleared on read.
|
H A D | ltc4260.rst | 63 curr1_alarm SENSE overcurrent alarm
|
H A D | ltc4261.rst | 70 curr1_alarm SENSE overcurrent alarm
|
H A D | lineage-pem.rst | 70 curr1_alarm Input overcurrent alarm
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | exynos5250-snow.dts | 149 ti,overcurrent-wait = <3>; 154 ti,overcurrent-wait = <3>; 159 ti,overcurrent-wait = <3>; 163 ti,overcurrent-wait = <3>; 168 ti,overcurrent-wait = <3>; 172 ti,overcurrent-wait = <3>; 177 ti,overcurrent-wait = <3>;
|
H A D | exynos5250-spring.dts | 531 ti,overcurrent-wait = <3>; 536 ti,overcurrent-wait = <3>; 541 ti,overcurrent-wait = <3>; 545 ti,overcurrent-wait = <3>; 550 ti,overcurrent-wait = <3>; 554 ti,overcurrent-wait = <3>; 559 ti,overcurrent-wait = <3>;
|
H A D | armada-388-helios4.dts | 152 * 5-USB3 overcurrent 191 "usb-overcurrent-status";
|
/openbmc/linux/Documentation/devicetree/bindings/regulator/ |
H A 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.
|
/openbmc/linux/arch/arm/boot/dts/samsung/ |
H A 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>;
|
/openbmc/linux/arch/arm64/boot/dts/broadcom/stingray/ |
H A D | stingray-pinctrl.dtsi | 322 drdu2_pins: drdu2-overcurrent-pins { 331 drdu3_pins: drdu3-overcurrent-pins { 340 usb3h_pins: usb3h-overcurrent-pins {
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | st,sta350.txt | 63 - st,overcurrent-warning-adjustment: 64 If present, overcurrent warning adjustment is enabled.
|
/openbmc/linux/arch/arm/boot/dts/marvell/ |
H A D | armada-388-helios4.dts | 157 * 5-USB3 overcurrent 195 line-name = "usb-overcurrent-status";
|
H A D | armada-388-clearfog.dts | 66 * 5-USB3 overcurrent
|
H A D | armada-388-clearfog.dtsi | 121 * 5-USB3 overcurrent
|
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
H A D | configuration.md | 10 overcurrent settings.
|
/openbmc/phosphor-power/phosphor-regulators/ |
H A D | README.md | 19 overcurrent settings.
|
/openbmc/linux/Documentation/devicetree/bindings/usb/ |
H A D | atmel-usb.txt | 19 activated for the overcurrent detection.
|
/openbmc/linux/arch/arm/boot/dts/renesas/ |
H A D | r7s9210-rza2mevb.dts | 18 * - USB Channel 1 loses the overcurrent input signal.
|
/openbmc/linux/Documentation/ABI/testing/ |
H A 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
|
/openbmc/linux/arch/arm64/boot/dts/ti/ |
H A D | k3-am642-tqma64xxl-mbax4xxl.dts | 434 * The CDNS USB driver currently doesn't support overcurrent GPIOs, 435 * so there is no overcurrent detection. The OC pin is configured
|
/openbmc/linux/Documentation/power/regulator/ |
H A D | overview.rst | 166 overvoltage or overcurrent caused by buggy client drivers. It also
|