All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221110] New: amdgpu DM skips backlight registration on ASUS TUF A14 (DCN 3.5) due to ATPX detection regardless of active GPU mode
Date: Fri, 20 Feb 2026 21:37:24 +0000	[thread overview]
Message-ID: <bug-221110-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221110

            Bug ID: 221110
           Summary: amdgpu DM skips backlight registration on ASUS TUF A14
                    (DCN 3.5) due to ATPX detection regardless of active
                    GPU mode
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: maurotibanez@gmail.com
        Regression: No

Hardware:

Laptop: ASUS TUF A14
Panel: BOE NE140QDM-NX7
iGPU: AMD (DCN 3.5)
dGPU: NVIDIA (disabled via vga_switcheroo / supergfxctl, Integrated mode
active)
Kernel: 6.17.9-76061709-generic

Problem:
No backlight device is registered in /sys/class/backlight/ when booting in
Integrated GPU mode. Brightness control is completely non-functional.
Kernel log showing root cause:

[3.831962] amdgpu: vga_switcheroo: detected switching method
\_SB_.PCI0.GPPA.VGA_.ATPX handle
[3.832035] amdgpu: ATPX version 1, functions 0x00000801
[3.832077] amdgpu: ATPX Hybrid Graphics
[4.320982] amdgpu 0000:65:00.0: amdgpu: [drm] Skipping amdgpu DM backlight
registration

The amdgpu driver detects ATPX at 3.83s and skips backlight registration at
4.32s. The skip occurs unconditionally based on ATPX presence, without checking
whether vga_switcheroo has actually handed display control to the iGPU. When in
Integrated mode, amdgpu owns the display pipeline (DCN 3.5 active, eDP-1
connected to card0) but does not register a backlight device.
Confirmed not caused by:

asus_wmi / asus-nb-wmi (loads at 6.08s, after the skip at 4.32s)
Missing ACPI backlight method (DSDT contains no backlight method)
Panel quirk (BOE NE140QDM-NX7 has no known quirk entry)

Kernel parameters tested with no effect:

amdgpu.backlight=0 / amdgpu.backlight=1
acpi_backlight=native
acpi_backlight=video
acpi_backlight=vendor

ATPX functions value: 0x00000801
Expected behavior:
When vga_switcheroo/supergfxctl has placed the system in Integrated mode and
the AMD iGPU owns the display pipeline, amdgpu DM should register a backlight
device normally regardless of ATPX presence.
Additional info:

/proc/acpi/video/ does not exist
card0-eDP-1 is the active internal panel path
NVIDIA modules are fully unloaded in Integrated mode
supergfxctl -g confirms Integrated

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2026-02-20 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 21:37 bugzilla-daemon [this message]
2026-02-26 14:34 ` [Bug 221110] amdgpu DM skips backlight registration on ASUS TUF A14 (DCN 3.5) due to ATPX detection regardless of active GPU mode bugzilla-daemon

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=bug-221110-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.