From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: platform-driver-x86@vger.kernel.org,
Antheas Kapenekakis <lkml@antheas.dev>
Cc: linux-kernel@vger.kernel.org,
"Derek John Clark" <derekjohn.clark@gmail.com>,
"Joaquín Ignacio Aramendía" <samsagax@gmail.com>,
Eileen <eileen@one-netbook.com>,
"Hans de Goede" <hansg@kernel.org>
Subject: Re: [PATCH v1 1/2] platform/x86: oxpec: Fix turbo register for G1 AMD
Date: Tue, 22 Jul 2025 18:38:57 +0300 [thread overview]
Message-ID: <175319873747.17914.9743576512932520356.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250718163305.159232-1-lkml@antheas.dev>
On Fri, 18 Jul 2025 18:33:04 +0200, Antheas Kapenekakis wrote:
> Turns out that the AMD variant of the G1 uses different turbo registers
> than the Intel variant. Differentiate them and apply the correct ones
> to the AMD variant.
>
>
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/2] platform/x86: oxpec: Fix turbo register for G1 AMD
commit: 232b41d3c2ce8cf4641a174416676458bf0de5b2
[2/2] platform/x86: oxpec: Add support for OneXPlayer X1 Mini Pro (Strix Point)
commit: 1798561befd8be1e52feb54f850efcab5a595f43
--
i.
prev parent reply other threads:[~2025-07-22 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 16:33 [PATCH v1 1/2] platform/x86: oxpec: Fix turbo register for G1 AMD Antheas Kapenekakis
2025-07-18 16:33 ` [PATCH v1 2/2] platform/x86: oxpec: Add support for OneXPlayer X1 Mini Pro (Strix Point) Antheas Kapenekakis
2025-07-22 13:22 ` [PATCH v1 1/2] platform/x86: oxpec: Fix turbo register for G1 AMD Ilpo Järvinen
2025-07-22 13:27 ` Antheas Kapenekakis
2025-07-22 13:31 ` Ilpo Järvinen
2025-07-22 15:38 ` Ilpo Järvinen [this message]
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=175319873747.17914.9743576512932520356.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=derekjohn.clark@gmail.com \
--cc=eileen@one-netbook.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=samsagax@gmail.com \
/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