From: Martin Schiller <ms@dev.tdt.de>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Florian Eckert <fe@dev.tdt.de>, Martin Schiller <ms@dev.tdt.de>
Subject: [PATCH 0/2] x86/cpu: P-state support for Lightning Mountain
Date: Fri, 06 Mar 2026 09:27:23 +0100 [thread overview]
Message-ID: <20260306-cpufreq_lgm-v1-0-47f104aed7c2@dev.tdt.de> (raw)
This patch set contains 2 commits to get P-state support for Intel /
MaxLinear Lightning Mountain. The first adds the needed code to the
intel_pstate driver. The second adds a workaround to the x86/cpu
subsystem to enable EIST on all cpus.
Signed-off-by: Martin Schiller <ms@dev.tdt.de>
---
Martin Schiller (2):
cpufreq: intel_pstate: Add Lightning Mountain support
x86/cpu/intel: Add EIST workaround for Lightning Mountain.
arch/x86/kernel/cpu/intel.c | 23 ++++++++++++++++
drivers/cpufreq/intel_pstate.c | 62 ++++++++++++++++++++++++++++++++++++++++++
2 files changed, 85 insertions(+)
---
base-commit: 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b
change-id: 20260306-cpufreq_lgm-c0280ef989c3
Best regards,
--
Martin Schiller <ms@dev.tdt.de>
next reply other threads:[~2026-03-06 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 8:27 Martin Schiller [this message]
2026-03-06 8:27 ` [PATCH 1/2] cpufreq: intel_pstate: Add Lightning Mountain support Martin Schiller
2026-03-06 8:27 ` [PATCH 2/2] x86/cpu/intel: Add EIST workaround for Lightning Mountain Martin Schiller
2026-03-06 16:54 ` Dave Hansen
2026-03-09 9:30 ` Martin Schiller
2026-03-06 17:59 ` [PATCH 0/2] x86/cpu: P-state support " Rafael J. Wysocki
2026-03-09 6:53 ` Martin Schiller
2026-03-09 15:57 ` srinivas pandruvada
2026-03-17 6:53 ` Martin Schiller
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=20260306-cpufreq_lgm-v1-0-47f104aed7c2@dev.tdt.de \
--to=ms@dev.tdt.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fe@dev.tdt.de \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=x86@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®