linux/Documentation/devicetree
Krzysztof Kozlowski 8163fbd971 mfd: max14577: Do not enforce (incorrect) interrupt trigger type
Interrupt line can be configured on different hardware in different way,
even inverted.  Therefore driver should not enforce specific trigger
type - edge falling - but instead rely on Devicetree to configure it.

The Maxim 14577/77836 datasheets describe the interrupt line as active
low with a requirement of acknowledge from the CPU therefore the edge
falling is not correct.

The interrupt line is shared between PMIC and charger driver, so using
level sensitive interrupt is here especially important to avoid races.
With an edge configuration in case if first PMIC signals interrupt
followed shortly after by the RTC, the interrupt might not be yet
cleared/acked thus the second one would not be noticed.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
Link: https://lore.kernel.org/r/20210602110445.33536-4-krzysztof.kozlowski@canonical.com
2021-11-05 14:40:06 +00:00
..
bindings mfd: max14577: Do not enforce (incorrect) interrupt trigger type 2021-11-05 14:40:06 +00:00
changesets.rst docs: dt: Make 'Devicetree' wording more consistent 2021-03-27 12:58:04 -06:00
dynamic-resolution-notes.rst docs: dt: Make 'Devicetree' wording more consistent 2021-03-27 12:58:04 -06:00
index.rst docs: dt: Add DT API documentation 2021-03-27 12:59:03 -06:00
kernel-api.rst docs: dt: Add DT API documentation 2021-03-27 12:59:03 -06:00
of_unittest.rst docs: dt: Make 'Devicetree' wording more consistent 2021-03-27 12:58:04 -06:00
overlay-notes.rst docs: dt: Make 'Devicetree' wording more consistent 2021-03-27 12:58:04 -06:00
usage-model.rst docs: dt: Make 'Devicetree' wording more consistent 2021-03-27 12:58:04 -06:00