From: Guilhem Lettron <guilhem@barpilot.io>
To: dedekind1@gmail.com
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Len Brown <lenb@kernel.org>, Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] intel_idle: Add ICL support
Date: Wed, 26 Aug 2020 15:19:15 +0200 [thread overview]
Message-ID: <CAGX5Wg2rzm74RprNYVzbkGBUx8WJZ5etKE_UOg8S3Eoyd=h2pg@mail.gmail.com> (raw)
In-Reply-To: <a7c8ee4b54b5f205548c055b7b8d599c1bd7ddeb.camel@gmail.com>
On Wed, 26 Aug 2020 at 15:09, Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
> On Wed, 2020-08-26 at 15:03 +0200, Guilhem Lettron wrote:
> > On my laptop, a Dell XPS 13 7390 2-in-1 with i7-1065G7, ACPI only
> > report "C1_ACPI", "C2_ACPI" and "C3_ACPI".
>
> Did you try to dig into the BIOS menus and check if you can enable
> more/deeper C-states?
Yes everything is enabled relative to C-states.
I find, at least, 1 people with same problem:
https://community.clearlinux.org/t/intel-idle-on-10th-ice-lake/3939/9
>
> Artem.
>
Guilhem Lettron
next prev parent reply other threads:[~2020-08-26 13:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 12:04 [PATCH] intel_idle: Add ICL support Guilhem Lettron
2020-08-26 12:43 ` Rafael J. Wysocki
2020-08-26 13:03 ` Guilhem Lettron
2020-08-26 13:09 ` Artem Bityutskiy
2020-08-26 13:19 ` Guilhem Lettron [this message]
2020-08-26 13:20 ` Rafael J. Wysocki
2020-08-26 13:16 ` Artem Bityutskiy
2020-08-26 13:18 ` Artem Bityutskiy
2020-08-26 13:21 ` Rafael J. Wysocki
2020-08-26 13:32 ` Guilhem Lettron
2020-08-26 13:41 ` Zhang Rui
2020-08-26 14:04 ` Guilhem Lettron
2020-08-26 16:02 ` Rafael J. Wysocki
2020-08-26 16:21 ` Rafael J. Wysocki
2020-08-26 16:39 ` Artem Bityutskiy
2020-08-26 16:43 ` Rafael J. Wysocki
2020-08-26 16:46 ` Guilhem Lettron
2020-08-26 17:00 ` Rafael J. Wysocki
2020-08-26 17:47 ` Zhang Rui
2020-08-26 16:52 ` Artem Bityutskiy
2020-08-26 16:19 ` Artem Bityutskiy
2020-08-26 16:25 ` Artem Bityutskiy
2020-08-26 16:28 ` Artem Bityutskiy
2020-08-26 16:41 ` Rafael J. Wysocki
[not found] ` <CAGX5Wg0655U71nFcaAJXmj1XMA3MjnCVn=q1Pf=7LLyryHhroQ@mail.gmail.com>
2020-08-26 13:17 ` Rafael J. Wysocki
2020-08-26 13:34 ` Guilhem Lettron
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='CAGX5Wg2rzm74RprNYVzbkGBUx8WJZ5etKE_UOg8S3Eoyd=h2pg@mail.gmail.com' \
--to=guilhem@barpilot.io \
--cc=dedekind1@gmail.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.