summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJens Reidel <adrian@travitia.xyz>2026-04-05 12:54:56 +0200
committerBjorn Andersson <andersson@kernel.org>2026-04-27 14:43:31 -0500
commit68bfaa3fde985a227721b58b32283811d05d5c21 (patch)
tree9beef2d5accb685e57f16d9fa42d903700e570e5 /tools/perf/scripts/python
parentaa7066248f1b6b2d000d3cc2f64a3fd4930e1b44 (diff)
arm64: dts: qcom: sdm845-xiaomi-beryllium: Append compatible strings
Add the generic "xiaomi,beryllium" compatible string after the panel-specific one, so the compatible list follows the required ordering from most specific to most generic. This allows userspace to fall back to the generic Poco F1 compatible when no panel-specific match is present. In particular, hexagonrpcd relies on trying all compatible entries to derive the HexagonFS path, and currently fails when the generic device string is missing. This change modifies the DT ABI: systems describing the EBBG variant will now also match on "xiaomi,beryllium", whereas previously only the panel-specific compatible was exposed. In practice, no upstream userspace distinguishes between Tianma and EBBG panel variants. All known consumers rely only on the generic device identification, and no panel-specific handling exists. Therefore, enabling the generic fallback does not change effective runtime behavior, but fixes userspace that depends on generic matching. The previous state was incomplete, as it omitted the generic device-compatible string required for proper fallback matching. Signed-off-by: Jens Reidel <adrian@travitia.xyz> Signed-off-by: David Heidelberg <david@ixit.cz> Link: https://lore.kernel.org/r/20260405-beryllium-compat-string-v2-2-91149be07835@ixit.cz Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions