diff options
| author | Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> | 2026-04-29 18:56:27 +0200 |
|---|---|---|
| committer | Thierry Reding <treding@nvidia.com> | 2026-07-31 17:55:31 +0200 |
| commit | 93fd84cee4546ea6475b1c4e1250a7ddbd3d5e7f (patch) | |
| tree | 59de6587a882360a107bf6bdbd2c8100e909a319 | |
| parent | 3f856cf050cb45e5921ebabf32ecde4f135c04e9 (diff) | |
| download | linux-next-93fd84cee4546ea6475b1c4e1250a7ddbd3d5e7f.tar.gz linux-next-93fd84cee4546ea6475b1c4e1250a7ddbd3d5e7f.zip | |
arm64: tegra: Correct Tegra194 p2972 interrupt flags
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
Realtek RT5658 codec driver requests interrupt on both edges, so correct
the interrupt flags, assuming the author of the code wanted the similar
logical behavior behind the name "ACTIVE_xxx", this is:
ACTIVE_HIGH => IRQ_TYPE_EDGE_RISING
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
| -rw-r--r-- | arch/arm64/boot/dts/nvidia/tegra194-p2972-0000.dts | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm64/boot/dts/nvidia/tegra194-p2972-0000.dts b/arch/arm64/boot/dts/nvidia/tegra194-p2972-0000.dts index ea6f397a2792..5462200f1176 100644 --- a/arch/arm64/boot/dts/nvidia/tegra194-p2972-0000.dts +++ b/arch/arm64/boot/dts/nvidia/tegra194-p2972-0000.dts @@ -2170,7 +2170,7 @@ compatible = "realtek,rt5658"; reg = <0x1a>; interrupt-parent = <&gpio>; - interrupts = <TEGRA194_MAIN_GPIO(S, 5) GPIO_ACTIVE_HIGH>; + interrupts = <TEGRA194_MAIN_GPIO(S, 5) IRQ_TYPE_EDGE_RISING>; clocks = <&bpmp TEGRA194_CLK_AUD_MCLK>; clock-names = "mclk"; realtek,jd-src = <2>; |