From: Martin Schiller <ms@dev.tdt.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@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>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Florian Eckert <fe@dev.tdt.de>
Subject: Re: [PATCH 0/2] x86/cpu: P-state support for Lightning Mountain
Date: Mon, 09 Mar 2026 07:53:40 +0100 [thread overview]
Message-ID: <3e828b47bacf84ca8d19a024ac71778c@dev.tdt.de> (raw)
In-Reply-To: <CAJZ5v0jR0eVu2oCD+c0x9MERfYvdPfNi2T9YZrO9RLQf-+iH3A@mail.gmail.com>
On 2026-03-06 18:59, Rafael J. Wysocki wrote:
> On Fri, Mar 6, 2026 at 9:27 AM Martin Schiller <ms@dev.tdt.de> wrote:
>>
>> 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.
>
> Can you please combine the patches?
>
> Or does the first one work just fine without the second one?
Well, the first patch can basically be applied without the second one,
but then frequency stepping will only work on the first cpu core.
I split the two changes because they apply to different parts of the
kernel sources.
But you're probably right, and it makes sense to combine the two
patches.
BTW: The original code from the MaxLinear SDK enables EIST in the
intel_pstate driver, but I don't think that's the right place for it.
next prev parent reply other threads:[~2026-03-09 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 8:27 [PATCH 0/2] x86/cpu: P-state support for Lightning Mountain Martin Schiller
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 [this message]
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=3e828b47bacf84ca8d19a024ac71778c@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