From: <vitaly.prosyak@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>
Subject: [PATCH v1 0/1] lib/amdgpu: fix platform range matching with chip_external_rev
Date: Wed, 2 Sep 2026 15:34:44 -0400 [thread overview]
Message-ID: <cover.1788377261.git.vitaly.prosyak@amd.com> (raw)
From: Vitaly Prosyak <vitaly.prosyak@amd.com>
This single-patch series fixes AMD platform range matching for navi32.
navi32 skip rules can fail because the matcher used chip_rev. On some
systems chip_rev is 0 while chip_external_rev contains the ASIC mapping
value (for example, 0x20). Prefer chip_external_rev when it is available,
with a fallback to chip_rev for older kernels or devices. This restores
the expected platform_skip.conf behavior.
--
2.54.0
next reply other threads:[~2026-09-02 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:34 vitaly.prosyak [this message]
2026-09-02 19:34 ` [PATCH v1 1/1] lib/amdgpu: prefer chip_external_rev for platform range match vitaly.prosyak
2026-09-02 23:44 ` ✓ Xe.CI.BAT: success for lib/amdgpu: fix platform range matching with chip_external_rev Patchwork
2026-09-02 23:46 ` ✓ i915.CI.BAT: " Patchwork
2026-09-03 16:52 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-03 20:06 ` ✗ i915.CI.Full: " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1788377261.git.vitaly.prosyak@amd.com \
--to=vitaly.prosyak@amd.com \
--cc=igt-dev@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox