ASoC: dt-bindings: Correct interrupt flags in examples
authorKrzysztof Kozlowski <krzk@kernel.org>
Tue, 8 Sep 2020 14:59:54 +0000 (16:59 +0200)
committerMark Brown <broonie@kernel.org>
Thu, 17 Sep 2020 16:40:06 +0000 (17:40 +0100)
commitabe42b09118914f01246f880dd9029150fdc727c
tree8aacd269d7b7ae7219d9caa4cabdea1b2e31043a
parentcac17861c950832a60d405f597c2acc2f40a0136
ASoC: dt-bindings: 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 some
logical behavior behind the name "ACTIVE_xxx", this is:
  ACTIVE_HIGH => IRQ_TYPE_LEVEL_HIGH

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Acked-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20200908145954.4629-1-krzk@kernel.org
Signed-off-by: Mark Brown <broonie@kernel.org>
Documentation/devicetree/bindings/sound/max98090.txt
Documentation/devicetree/bindings/sound/rt5640.txt
Documentation/devicetree/bindings/sound/rt5659.txt
Documentation/devicetree/bindings/sound/rt5665.txt
Documentation/devicetree/bindings/sound/rt5668.txt
Documentation/devicetree/bindings/sound/rt5677.txt
Documentation/devicetree/bindings/sound/rt5682.txt