mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marco Scardovi <scardracs@disroot.org>
To: "Luke D . Jones" <luke@ljones.dev>,
	"Denis Benato" <denis.benato@linux.dev>,
	"Corentin Chary" <corentin.chary@gmail.com>,
	"Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: asus-armoury: add support for G614PR
Date: Thu, 11 Jun 2026 17:53:11 +0200	[thread overview]
Message-ID: <OhHrh4KYR76ict9IRSPksQ@disroot.org> (raw)
In-Reply-To: <178119015973.12014.6231948241278781864.b4-ty@b4>

In data giovedì 11 giugno 2026 17:02:39 Ora legale dell’Europa centrale, Ilpo 
Järvinen ha scritto:
> On Wed, 10 Jun 2026 17:21:30 +0200, Marco Scardovi wrote:
> > Add TDP power limits and fan curve requirements for the ASUS ROG Strix
> > G16 G614PR laptop model.
> > 
> > The ASUS ROG Strix G16 G614PR requires specific AC/DC power limits
> > (PPT PL1/PL2/PL3, dynamic boost, and NV TGP targets) to function
> > correctly under various power profiles. Without these limits, the Asus
> > Armoury driver cannot configure the correct power envelopes or enable
> > custom fan curves, leading to suboptimal performance or noise management.
> > 
> > [...]
> 
> Thank you for your contribution, it has been applied to my local
> review-ilpo-next branch. Note it will show up in the public
> platform-drivers-x86/review-ilpo-next branch only once I've pushed my
> local branch there, which might take a while.
> 
> The list of commits applied:
> [1/1] platform/x86: asus-armoury: add support for G614PR
>       commit: 6b3bbe770f4ca0439710b7c42f88b9f6eeebabd0
> 
> --
>  i.

Hi! Thank you for picking it up :) I'm not in a rush and tbf I was expecting 
it would take some time.



  reply	other threads:[~2026-06-11 15:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 15:21 Marco Scardovi
2026-06-10 17:54 ` Denis Benato
2026-06-11 15:02 ` Ilpo Järvinen
2026-06-11 15:53   ` Marco Scardovi [this message]
2026-06-14  8:44   ` [PATCH v2 0/1] " Marco Scardovi
2026-06-14  8:44     ` [PATCH v2] " Marco Scardovi
2026-06-14 12:33       ` Denis Benato
2026-06-15 15:07         ` Marco Scardovi
2026-06-27  6:18           ` Marco Scardovi
2026-06-29 11:04             ` Ilpo Järvinen
2026-06-29 11:27               ` Marco Scardovi
2026-06-30 14:18                 ` Ilpo Järvinen

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=OhHrh4KYR76ict9IRSPksQ@disroot.org \
    --to=scardracs@disroot.org \
    --cc=corentin.chary@gmail.com \
    --cc=denis.benato@linux.dev \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --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