Fix incorrect dimensions for 'debonce' and 'scan-delay' times.
Now they represent what driver really expect. Add possible
time quants for 'debonce', 'scan-delay' and 'row-hold' times.
Update bindings example.
Signed-off-by: Ivan T. Ivanov <iiva...@mm-sol.com>
---
Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt
b/Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt
index 2b60f8a..df5e2a1 100644
--- a/Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt
+++ b/Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt
@@ -54,20 +54,23 @@ PROPERTIES
- debounce:
Usage: optional
Value type: <u32>
- Definition: time in microseconds that key must be pressed or release
+ Definition: time in miliseconds that key must be pressed or release
for key sense interrupt to trigger.
+ Possible values: 5, 10, 15, 20.
- scan-delay:
Usage: optional
Value type: <u32>
- Definition: time in microseconds to pause between successive scans
+ Definition: time in miliseconds to pause between successive scans
of the matrix array.
+ Possible values: 1, 2, 4, 8, 16, 32, 64, 128.
- row-hold:
Usage: optional
Value type: <u32>
Definition: time in nanoseconds to pause between scans of each row in
the matrix array.
+ Possible values: 30500, 61000, 122000.
EXAMPLE
@@ -86,5 +89,5 @@ EXAMPLE
keypad,num-columns = <5>;
debounce = <15>;
scan-delay = <32>;
- row-hold = <91500>;
+ row-hold = <61000>;
};
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
