diff options
| author | Krzysztof Kozlowski <[email protected]> | 2022-05-09 16:47:14 +0200 |
|---|---|---|
| committer | Bjorn Andersson <[email protected]> | 2022-06-27 16:46:32 -0500 |
| commit | cb0b68537713208824af74f2b1dbae22e8e52f82 (patch) | |
| tree | be1a0d79a4e2aa892db8e5adbbfb2dd17f7f93d2 /tools/perf/scripts/python/flamegraph.py | |
| parent | 7908dcc8be2db90c9d9bbcbd5fb021f935b76b26 (diff) | |
arm64: dts: qcom: sdm630: order interrupts according to bindings
The CAMSS DTSI device node, which came after the bindings were merged,
got the interrupts ordered differently then specified in the bindings:
sdm630-sony-xperia-nile-pioneer.dtb: camss@ca00000: interrupt-names:0: 'csid0' was expected
Reordering them to match bindings should not cause ABI issues, because
the driver relies on names, not ordering.
Signed-off-by: Krzysztof Kozlowski <[email protected]>
Signed-off-by: Bjorn Andersson <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions