From: Neftin, Sasha <sasha.neftin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] platform/x86: intel_pmc: Ignore GBE LTR on Tiger Lake platforms
Date: Sun, 7 Mar 2021 10:39:16 +0200 [thread overview]
Message-ID: <113b08b2-ead1-7f4c-1b09-4f3572d6134f@intel.com> (raw)
In-Reply-To: <20210305190608.1834164-1-david.e.box@linux.intel.com>
On 3/5/2021 21:06, David E. Box wrote:
> Due to a HW limitation, the Latency Tolerance Reporting (LTR) value
> programmed in the Tiger Lake GBE controller is not large enough to allow
> the platform to enter Package C10, which in turn prevents the platform from
> achieving its low power target during suspend-to-idle. Ignore the GBE LTR
> value on Tiger Lake. LTR ignore functionality is currently performed solely
> by a debugfs write call. Split out the LTR code into its own function that
> can be called by both the debugfs writer and by this work around.
>
> Signed-off-by: David E. Box <david.e.box@linux.intel.com>
> Reviewed-by: Sasha Neftin <sasha.neftin@intel.com>
> Cc: intel-wired-lan at lists.osuosl.org
> ---
> drivers/platform/x86/intel_pmc_core.c | 55 ++++++++++++++++++++-------
> 1 file changed, 42 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/platform/x86/intel_pmc_core.c b/drivers/platform/x86/intel_pmc_core.c
> index ee2f757515b0..ab31eb646a1a 100644
> --- a/drivers/platform/x86/intel_pmc_core.c
> +++ b/drivers/platform/x86/intel_pmc_core.c
> @@ -863,34 +863,45 @@ static int pmc_core_pll_show(struct seq_file *s, void *unused)
> }
> DEFINE_SHOW_ATTRIBUTE(pmc_core_pll);
>
> -static ssize_t pmc_core_ltr_ignore_write(struct file *file,
> - const char __user *userbuf,
> - size_t count, loff_t *ppos)
> +static int pmc_core_write_ltr_ignore(u32 value)
> {
> struct pmc_dev *pmcdev = &pmc;
> const struct pmc_reg_map *map = pmcdev->map;
> - u32 val, buf_size, fd;
> - int err;
> -
> - buf_size = count < 64 ? count : 64;
> -
> - err = kstrtou32_from_user(userbuf, buf_size, 10, &val);
> - if (err)
> - return err;
> + u32 fd;
> + int err = 0;
>
> mutex_lock(&pmcdev->lock);
>
> - if (val > map->ltr_ignore_max) {
> + if (fls(value) > map->ltr_ignore_max) {
> err = -EINVAL;
> goto out_unlock;
> }
>
> fd = pmc_core_reg_read(pmcdev, map->ltr_ignore_offset);
> - fd |= (1U << val);
> + fd |= value;
> pmc_core_reg_write(pmcdev, map->ltr_ignore_offset, fd);
>
> out_unlock:
> mutex_unlock(&pmcdev->lock);
> +
> + return err;
> +}
> +
> +static ssize_t pmc_core_ltr_ignore_write(struct file *file,
> + const char __user *userbuf,
> + size_t count, loff_t *ppos)
> +{
> + u32 buf_size, val;
> + int err;
> +
> + buf_size = count < 64 ? count : 64;
> +
> + err = kstrtou32_from_user(userbuf, buf_size, 10, &val);
> + if (err)
> + return err;
> +
> + err = pmc_core_write_ltr_ignore(1U << val);
> +
> return err == 0 ? count : err;
> }
>
> @@ -1189,6 +1200,15 @@ static int quirk_xtal_ignore(const struct dmi_system_id *id)
> return 0;
> }
>
> +static int quirk_ltr_ignore(u32 val)
> +{
> + int err;
> +
> + err = pmc_core_write_ltr_ignore(val);
> +
> + return err;
> +}
> +
> static const struct dmi_system_id pmc_core_dmi_table[] = {
> {
> .callback = quirk_xtal_ignore,
> @@ -1244,6 +1264,15 @@ static int pmc_core_probe(struct platform_device *pdev)
> pmcdev->pmc_xram_read_bit = pmc_core_check_read_lock_bit();
> dmi_check_system(pmc_core_dmi_table);
>
> + /*
> + * On TGL, due to a hardware limitation, the GBE LTR blocks PC10 when
> + * a cable is attached. Tell the PMC to ignore it.
> + */
> + if (pmcdev->map == &tgl_reg_map) {
I would suggest: if (pmcdev->map >= &tgl_reg_map)
> + dev_dbg(&pdev->dev, "ignoring GBE LTR\n");
> + quirk_ltr_ignore(1U << 3);
> + }
> +
> pmc_core_dbgfs_register(pmcdev);
>
> device_initialized = true;
>
next prev parent reply other threads:[~2021-03-07 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 19:06 [Intel-wired-lan] [PATCH] platform/x86: intel_pmc: Ignore GBE LTR on Tiger Lake platforms David E. Box
2021-03-07 8:39 ` Neftin, Sasha [this message]
2021-03-07 19:09 ` David E. Box
2021-03-07 19:13 ` Hans de Goede
2021-03-08 14:04 ` Rajneesh Bhardwaj
2021-03-08 14:10 ` Rajneesh Bhardwaj
2021-03-08 16:54 ` David E. Box
2021-03-08 16:57 ` Rajneesh Bhardwaj
2021-03-08 17:20 ` Limonciello, Mario
2021-03-08 17:31 ` Rajneesh Bhardwaj
2021-03-08 18:02 ` Limonciello, Mario
2021-03-08 18:12 ` David E. Box
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=113b08b2-ead1-7f4c-1b09-4f3572d6134f@intel.com \
--to=sasha.neftin@intel.com \
--cc=intel-wired-lan@osuosl.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