[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250202035100.31235-1-badhri@google.com>
Date: Sun, 2 Feb 2025 03:50:59 +0000
From: Badhri Jagan Sridharan <badhri@...gle.com>
To: Thinh.Nguyen@...opsys.com, gregkh@...uxfoundation.org,
felipe.balbi@...ux.intel.com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, johnyoun@...opsys.com
Cc: linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, jameswei@...gle.com,
Badhri Jagan Sridharan <badhri@...gle.com>, stable@...nel.org
Subject: [PATCH v1 1/2] dt-bindings: usb: snps,dwc3: Add property for imod
This change adds `snps,device-mode-intrpt-mod-interval`
which allows enabling interrupt moderation through
snps,dwc3 node.
`snps,device-mode-intrpt-mod-interval`specifies the
minimum inter-interrupt interval in 250ns increments
during device mode operation. A value of 0 disables
the interrupt throttling logic and interrupts are
generated immediately if event count becomes non-zero.
Otherwise, the interrupt is signaled when all of the
following conditons are met which are, EVNT_HANDLER_BUSY
is 0, event count is non-zero and at least 250ns increments
of this value has elapsed since the last time interrupt
was de-asserted.
Cc: stable@...nel.org
Fixes: cf40b86b6ef6 ("usb: dwc3: Implement interrupt moderation")
Signed-off-by: Badhri Jagan Sridharan <badhri@...gle.com>
---
.../devicetree/bindings/usb/snps,dwc3-common.yaml | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/snps,dwc3-common.yaml b/Documentation/devicetree/bindings/usb/snps,dwc3-common.yaml
index c956053fd036..3957f1dac3c4 100644
--- a/Documentation/devicetree/bindings/usb/snps,dwc3-common.yaml
+++ b/Documentation/devicetree/bindings/usb/snps,dwc3-common.yaml
@@ -375,6 +375,19 @@ properties:
items:
enum: [1, 4, 8, 16, 32, 64, 128, 256]
+ snps,device-mode-intrpt-mod-interval:
+ description:
+ Specifies the minimum inter-interrupt interval in 250ns increments
+ during device mode operation. A value of 0 disables the interrupt
+ throttling logic and interrupts are generated immediately if event
+ count becomes non-zero. Otherwise, the interrupt is signaled when
+ all of the following conditons are met which are, EVNT_HANDLER_BUSY
+ is 0, event count is non-zero and at least 250ns increments of this
+ value has elapsed since the last time interrupt was de-asserted.
+ $ref: /schemas/types.yaml#/definitions/uint16
+ minimum: 0
+ maximum: 255
+
num-hc-interrupters:
maximum: 8
default: 1
base-commit: 72deda0abee6e705ae71a93f69f55e33be5bca5c
--
2.48.1.362.g079036d154-goog
Powered by blists - more mailing lists