Linux USB
 help / color / mirror / Atom feed
From: BurningHoryd <sjunhyuk1@gmail.com>
To: linux-usb@vger.kernel.org
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [BUG] HP OMEN Transcend 14 (board 8E41): GPU power ceiling on 65W USB-C charger is non-deterministic
Date: Fri, 25 Sep 2026 09:41:48 -0400	[thread overview]
Message-ID: <20260925134148.435774-1-sjunhyuk1@gmail.com> (raw)
In-Reply-To: <arVGfB1PV7kt2Llq@archlinux>

Krishna,

Thanks for taking a look. The acpidump is already up -- BIOS is still
F.05 (same as when I captured it on 8E41), so a fresh dump would be
byte-identical to what I already have; no need to redo it.

Full acpidump + decompiled SSDT23 (the table with the NPCF device) is
attached to my earlier comment on the NVIDIA issue:

  https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1162#issuecomment-5779711336

Same topology as board 8D40 from that issue: NPCF sits under \_SB as a
peer of the GPU rather than as its PCIe child, which is why the open
kernel module's NPCF binding misses it and Power Management Object
stays N/A. That explains why >50W Dynamic Boost never works here, but
it's a separate mechanism from the 25W/65W split on the 65W charger --
PMO is N/A in both states, so it can't be what's flipping that.

Happy to attach the raw acpidump/ssdt23-acpi.zip directly to this
thread instead of linking out, if that's easier for you to work with
-- just say the word.

Thanks for flagging the missing Signed-off-by on the other 8E41 patch
too.

  reply	other threads:[~2026-09-25 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 19:23 [BUG] HP OMEN Transcend 14 (board 8E41): GPU power ceiling on 65W USB-C charger is non-deterministic across sessions (25W vs ~65W) sjunhyuk1
2026-09-22 21:32 ` sjunhyuk1
2026-09-24 15:58 ` Krishna Chomal
2026-09-25 13:41   ` BurningHoryd [this message]
2026-09-26  5:35     ` [BUG] HP OMEN Transcend 14 (board 8E41): GPU power ceiling on 65W USB-C charger is non-deterministic Krishna Chomal

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=20260925134148.435774-1-sjunhyuk1@gmail.com \
    --to=sjunhyuk1@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.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