Home
last modified time | relevance | path

Searched full:overcurrent (Results 1 – 25 of 114) sorted by relevance

12345

/linux-6.14.4/drivers/usb/host/
Dohci-omap.c48 struct gpio_desc *overcurrent; member
142 /* board-specific power switching and overcurrent support */ in ohci_omap_reset()
155 /* gpio9 for overcurrent detection */ in ohci_omap_reset()
233 * This "overcurrent" GPIO line isn't really used in the code, in ohci_hcd_omap_probe()
235 * TODO: implement proper overcurrent handling. in ohci_hcd_omap_probe()
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()
Duhci-hub.c63 * overcurrent indications, causing massive log spam unless in get_hub_status_data()
66 * the motherboard; if the overcurrent input is left to float in get_hub_status_data()
270 /* Intel controllers report the OverCurrent bit active on. in uhci_hub_control()
Dohci-at91.c501 dev_err(& pdev->dev, "overcurrent interrupt from unknown GPIO\n"); in ohci_hcd_at91_overcurrent_irq()
516 dev_dbg(& pdev->dev, "overcurrent situation %s\n", in ohci_hcd_at91_overcurrent_irq()
582 dev_err(&pdev->dev, "unable to claim gpio \"overcurrent\": %d\n", err); in ohci_hcd_at91_drv_probe()
592 dev_info(&pdev->dev, "failed to request gpio \"overcurrent\" IRQ\n"); in ohci_hcd_at91_drv_probe()
/linux-6.14.4/drivers/regulator/
Dtps65219-regulator.c35 { "LDO3_OC", "LDO3", "overcurrent", REGULATOR_EVENT_OVER_CURRENT },
38 { "LDO4_OC", "LDO4", "overcurrent", REGULATOR_EVENT_OVER_CURRENT },
41 { "LDO1_OC", "LDO1", "overcurrent", REGULATOR_EVENT_OVER_CURRENT },
44 { "LDO2_OC", "LDO2", "overcurrent", REGULATOR_EVENT_OVER_CURRENT },
47 { "BUCK3_OC", "BUCK3", "overcurrent", REGULATOR_EVENT_OVER_CURRENT },
48 { "BUCK3_NEG_OC", "BUCK3", "negative overcurrent", REGULATOR_EVENT_OVER_CURRENT },
51 { "BUCK1_OC", "BUCK1", "overcurrent", REGULATOR_EVENT_OVER_CURRENT },
52 { "BUCK1_NEG_OC", "BUCK1", "negative overcurrent", REGULATOR_EVENT_OVER_CURRENT },
55 { "BUCK2_OC", "BUCK2", "overcurrent", REGULATOR_EVENT_OVER_CURRENT },
56 { "BUCK2_NEG_OC", "BUCK2", "negative overcurrent", REGULATOR_EVENT_OVER_CURRENT },
Dtps6594-regulator.c269 { TPS6594_IRQ_NAME_BUCK1_ILIM, "BUCK1", "reach ilim, overcurrent",
277 { TPS6594_IRQ_NAME_BUCK2_ILIM, "BUCK2", "reach ilim, overcurrent",
285 { TPS6594_IRQ_NAME_BUCK3_ILIM, "BUCK3", "reach ilim, overcurrent",
293 { TPS6594_IRQ_NAME_BUCK4_ILIM, "BUCK4", "reach ilim, overcurrent",
301 { TPS6594_IRQ_NAME_BUCK5_ILIM, "BUCK5", "reach ilim, overcurrent",
309 { TPS6594_IRQ_NAME_LDO1_ILIM, "LDO1", "reach ilim, overcurrent",
317 { TPS6594_IRQ_NAME_LDO2_ILIM, "LDO2", "reach ilim, overcurrent",
325 { TPS6594_IRQ_NAME_LDO3_ILIM, "LDO3", "reach ilim, overcurrent",
333 { TPS6594_IRQ_NAME_LDO4_ILIM, "LDO4", "reach ilim, overcurrent",
Dtps65090-regulator.c30 #define MAX_OVERCURRENT_WAIT 3 /* Overcurrent wait must be <= this */
54 * tps65090_reg_set_overcurrent_wait - Setup overcurrent wait
56 * This will set the overcurrent wait time based on what's in the regulator
73 dev_err(&rdev->dev, "Error updating overcurrent wait %#x\n", in tps65090_reg_set_overcurrent_wait()
125 * - We'll make sure that we bump the "overcurrent wait" to the maximum, which
387 if (of_property_read_u32(np, "ti,overcurrent-wait", in tps65090_parse_dt_reg_data()
Dqcom-labibb-regulator.c238 * qcom_labibb_ocp_isr - Interrupt routine for OverCurrent Protection
271 * damage at all costs, we assume that the overcurrent event was in qcom_labibb_ocp_isr()
288 /* Warn the user for overcurrent */ in qcom_labibb_ocp_isr()
296 /* Signal overcurrent event to drivers */ in qcom_labibb_ocp_isr()
830 /* OverCurrent Protection IRQ is optional */ in qcom_labibb_regulator_probe()
/linux-6.14.4/Documentation/hwmon/
Dltc4282.rst85 curr1_max Overcurrent threshold
89 Also clears overcurrent fault logs.
91 curr1_max_alarm Overcurrent alarm
92 curr1_crit_alarm Critical Overcurrent alarm
132 curr1_crit_fault_log Set to 1 by an overcurrent fault occurring.
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
Dltc2945.rst76 curr1_max Overcurrent threshold
81 curr1_max_alarm Overcurrent alarm
Dltc2947.rst63 curr1_max Overcurrent threshold
68 curr1_max_alarm Overcurrent alarm
Dpm6764tr.rst31 response. The device assures fast and independent protection against load overcurrent,
Dadm1177.rst36 curr1_max_alarm Overcurrent alarm in microamperes.
Dltc2992.rst48 currX_max_alarm An overcurrent occurred. Cleared on read.
/linux-6.14.4/Documentation/devicetree/bindings/iio/adc/
Dmaxim,max34408.yaml7 title: Maxim MAX34408/MAX34409 current monitors with overcurrent control
19 user-programmable digital thresholds to indicate overcurrent conditions.
20 Overcurrent conditions trigger a hardware output to provide an immediate
/linux-6.14.4/Documentation/devicetree/bindings/regulator/
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-6.14.4/Documentation/devicetree/bindings/power/supply/
Dmaxim,max77693.yaml50 maxim,battery-overcurrent-microamp:
52 Overcurrent protection threshold in uA (current from battery to
/linux-6.14.4/Documentation/devicetree/bindings/hwmon/
Dadi,adm1177.yaml31 the current reading and overcurrent alert is disabled.
36 If not provided, the overcurrent alert is configured to max ADC range
Dadi,ltc4282.yaml83 adi,overcurrent-retry:
86 Overcurrent fault.
/linux-6.14.4/arch/arm/boot/dts/samsung/
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-6.14.4/drivers/input/misc/
Dtwl6040-vibra.c61 dev_warn(info->dev, "Left Vibrator overcurrent detected\n"); in twl6040_vib_irq_handler()
66 dev_warn(info->dev, "Right Vibrator overcurrent detected\n"); in twl6040_vib_irq_handler()
88 * ERRATA: Disable overcurrent protection for at least in twl6040_vibra_enable()
90 * overcurrent detection in twl6040_vibra_enable()
/linux-6.14.4/drivers/usb/dwc3/
Ddwc3-octeon.c138 /* Overcurrent protection enable: 0x0 = unavailable, 0x1 = available */
140 /* Overcurrent sene selection:
141 * 0x0 = Overcurrent indication from off-chip is active-low
142 * 0x1 = Overcurrent indication from off-chip is active-high
278 /* Step 2: Select GPIO for overcurrent indication, if desired. SKIP */ in dwc3_octeon_setup()
/linux-6.14.4/Documentation/devicetree/bindings/sound/
Dst,sta350.txt63 - st,overcurrent-warning-adjustment:
64 If present, overcurrent warning adjustment is enabled.
/linux-6.14.4/arch/arm64/boot/dts/broadcom/stingray/
Dstingray-pinctrl.dtsi322 drdu2_pins: drdu2-overcurrent-pins {
331 drdu3_pins: drdu3-overcurrent-pins {
340 usb3h_pins: usb3h-overcurrent-pins {
/linux-6.14.4/include/linux/usb/
Disp116x.h13 /* On-chip overcurrent detection */

12345