linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: linux-pm@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>
Subject: Lack of Kaby Lake support in intel_pch_thermal
Date: Mon, 22 Dec 2025 15:44:44 +0100	[thread overview]
Message-ID: <20251222154444.496284d9@endymion> (raw)

Hi all,

We have this report in bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=219197

which suggests that adding Kaby Lake (aka 200 Series) chipset support
to the intel_pch_thermal driver would be trivial. I asked the reporter
to send his patch to the driver maintainers last year but it does not
look like he ever did. I can clean up his patch and send it, but before
I do, I want to ask: is there a reason why Kaby Lake support was
omitted in the first place?

Thanks,
-- 
Jean Delvare
SUSE L3 Support

                 reply	other threads:[~2025-12-22 14:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251222154444.496284d9@endymion \
    --to=jdelvare@suse.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).