mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: David Del Sol <daviddelsol1998@gmail.com>, linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, rafael@kernel.org, lenb@kernel.org,
	Armin Wolf <W_Armin@gmx.de>
Subject: Re: [PATCH] ACPI: OSI: Enable _OSI("Windows 2022") on HP OmniBook X Flip 16-ar0xxx
Date: Tue, 11 Aug 2026 12:52:17 -0500	[thread overview]
Message-ID: <727bdb6c-8d49-4ec7-acbe-d73b6e63cfae@amd.com> (raw)
In-Reply-To: <CADaJo4UrmNbPPxnnt0tjpdTuxK5wQdhS-0W=rAdLAC_++Vp47w@mail.gmail.com>



On 8/11/26 12:48, David Del Sol wrote:
> Hi all,
> 
> This fixes slow battery charging on the 2025 HP OmniBook X Flip (AMD Ryzen
> AI 5 340, DMI board 8DA8): with a 65 W charger plugged in, the battery
> charges at only ~0.2 W on Linux instead of the ~30 W Windows gets.
> 
> The EC firmware only enables normal charging when the OS claims
> _OSI("Windows 2022"), and the DSDT/SSDT only check up to that string.
> Linux's default claimed OSI strings stop short of it, so the fast-charging
> branch never runs. Adding acpi_osi=! acpi_osi="Windows 2022" to the kernel
> cmdline restores 31-33 W - verified across multiple charge cycles on
> kernels 7.1.6 and 6.18.42-LTS.
> 
> I checked with HP first: they declined in writing (warranty case
> #5163282638, supervisor email 2026-08-10), saying the firmware is
> "specifically manufactured and optimized for the Windows operating system"
> and not supported for other OSes. A kernel-side quirk is therefore the
> only fix path.
> 
> The patch claims _OSI("Windows 2022") via acpi_osi_setup() with a DMI
> match scoped to board 8DA8 (same mechanism as dmi_enable_osi_linux), so
> no other platform is affected. Full evidence - DSDT/SSDT strings, EC RAM
> dumps, measurement logs - is on the bugzilla report below; happy to add
> sibling boards as owners confirm.
> 
> Thanks for looking,
> David
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=221866 <https:// 
> bugzilla.kernel.org/show_bug.cgi?id=221866>

Are you sure about your proposed root cause?  It has been enabled a very 
long time.

https://git.kernel.org/torvalds/c/dd067afe3f8cb

  reply	other threads:[~2026-08-11 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 17:48 David Del Sol
2026-08-11 17:52 ` Mario Limonciello [this message]
     [not found]   ` <CADaJo4WSKvSSOt6vG64NjPwLnRot3tC5Uz9RBvKWTp0sUuFC=A@mail.gmail.com>
2026-08-11 19:08     ` Mario Limonciello

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=727bdb6c-8d49-4ec7-acbe-d73b6e63cfae@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=W_Armin@gmx.de \
    --cc=daviddelsol1998@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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

all inboxes | Powered by JetHome®