Home
last modified time | relevance | path

Searched refs:overcurrent (Results 1 – 25 of 31) sorted by relevance

12

/linux/drivers/usb/host/
H A Dohci-omap.c48 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/Documentation/hwmon/
H A Dltc4245.rst67 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 Dlt3074.rst67 curr1_crit Output overcurrent fault limit
68 curr1_crit_alarm Output overcurrent fault status
H A Dpm6764tr.rst31 response. The device assures fast and independent protection against load overcurrent,
H A Dltc4215.rst55 curr1_max_alarm overcurrent alarm
H A Dltc4282.rst89 Also clears overcurrent fault logs.
132 curr1_crit_fault_log Set to 1 by an overcurrent fault occurring.
H A Dltc2992.rst48 currX_max_alarm An overcurrent occurred. Cleared on read.
H A Dltc4260.rst63 curr1_alarm SENSE overcurrent alarm
H A Dlineage-pem.rst70 curr1_alarm Input overcurrent alarm
H A Dltc4261.rst70 curr1_alarm SENSE overcurrent alarm
/linux/Documentation/devicetree/bindings/regulator/
H A Dtps65090.txt24 - 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/arch/arm/boot/dts/samsung/
H A Dexynos5250-snow-common.dtsi131 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>;
/linux/arch/arm64/boot/dts/broadcom/stingray/
H A Dstingray-pinctrl.dtsi322 drdu2_pins: drdu2-overcurrent-pins {
331 drdu3_pins: drdu3-overcurrent-pins {
340 usb3h_pins: usb3h-overcurrent-pins {
/linux/Documentation/devicetree/bindings/sound/
H A Dst,sta350.txt63 - st,overcurrent-warning-adjustment:
64 If present, overcurrent warning adjustment is enabled.
/linux/arch/arm/boot/dts/marvell/
H A Darmada-388-helios4.dts157 * 5-USB3 overcurrent
195 line-name = "usb-overcurrent-status";
H A Darmada-388-clearfog.dts67 * 5-USB3 overcurrent
H A Darmada-388-clearfog.dtsi121 * 5-USB3 overcurrent
/linux/Documentation/wmi/devices/
H A Ddell-wmi-ddv.rst163 - overcurrent failure (``0xb``)
183 The following failure codes are valid for a overcurrent failure:
185 - overcurrent during charging (``0x6``)
186 - overcurrent during discharging (``0xb``)
/linux/drivers/platform/cznic/
H A DKconfig44 overcurrent,
/linux/Documentation/devicetree/bindings/usb/
H A Datmel-usb.txt19 activated for the overcurrent detection.
/linux/arch/arm/boot/dts/renesas/
H A Dr7s9210-rza2mevb.dts18 * - USB Channel 1 loses the overcurrent input signal.
/linux/Documentation/power/regulator/
H A Doverview.rst166 overvoltage or overcurrent caused by buggy client drivers. It also
/linux/Documentation/ABI/testing/
H A Dsysfs-devices-system-cpu481 /sys/devices/system/cpu/cpuX/cpufreq/throttle_stats/overcurrent
514 - overcurrent : This file gives the total number of times the
521 powercap, overtemp, supply_fault, overcurrent and occ_reset map to
531 /sys/devices/system/cpu/cpufreq/policyX/throttle_stats/overcurrent
/linux/arch/arm/boot/dts/nxp/imx/
H A Dimx6sx-softing-vining-2000.dts336 /* overcurrent detection */
/linux/arch/arm64/boot/dts/ti/
H A Dk3-am642-tqma64xxl-mbax4xxl.dts539 * The CDNS USB driver currently doesn't support overcurrent GPIOs,
540 * so there is no overcurrent detection. The OC pin is configured

12