diff options
| author | Krzysztof Kozlowski <[email protected]> | 2020-10-26 16:36:20 +0100 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2020-11-28 14:47:56 -0800 |
| commit | 4d521943f76bd0d1e68ea5e02df7aadd30b2838a (patch) | |
| tree | 9e94e3029ff241c02ff664062c153cd9332934f9 /tools/testing/selftests/bpf/prog_tests/ringbuf.c | |
| parent | 6548755c55254a3e96294a3385774641d178e011 (diff) | |
dt-bindings: net: correct interrupt flags in examples
GPIO_ACTIVE_x flags are not correct in the context of interrupt flags.
These are simple defines so they could be used in DTS but they will not
have the same meaning:
1. GPIO_ACTIVE_HIGH = 0 = IRQ_TYPE_NONE
2. GPIO_ACTIVE_LOW = 1 = IRQ_TYPE_EDGE_RISING
Correct the interrupt flags, assuming the author of the code wanted same
logical behavior behind the name "ACTIVE_xxx", this is:
ACTIVE_LOW => IRQ_TYPE_LEVEL_LOW
ACTIVE_HIGH => IRQ_TYPE_LEVEL_HIGH
Fixes: a1a8b4594f8d ("NFC: pn544: i2c: Add DTS Documentation")
Fixes: 6be88670fc59 ("NFC: nxp-nci_i2c: Add I2C support to NXP NCI driver")
Fixes: e3b329221567 ("dt-bindings: can: tcan4x5x: Update binding to use interrupt property")
Signed-off-by: Krzysztof Kozlowski <[email protected]>
Acked-by: Rob Herring <[email protected]>
Acked-by: Marc Kleine-Budde <[email protected]> # for tcan4x5x.txt
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/ringbuf.c')
0 files changed, 0 insertions, 0 deletions