mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, Rui Feng <rui_feng@realsil.com.cn>
Subject: Re: [PATCH] mfd: Fix RTS5227 (and others) powermanagement
Date: Wed, 6 Dec 2017 16:44:03 +0100	[thread overview]
Message-ID: <906755d5-45b4-c4d0-e4b7-e501e5e7b450@redhat.com> (raw)
In-Reply-To: <20171206154216.p34bksrk4bnx2krq@dell>

Hi,

On 06-12-17 16:42, Lee Jones wrote:
> On Wed, 06 Dec 2017, Hans de Goede wrote:
> 
>> Hi,
>>
>> On 06-12-17 12:21, Hans de Goede wrote:
>>> Commit 8275b77a1513 ("mfd: rts5249: Add support for RTS5250S power
>>> saving") adds powersaving support for device-ids 5249 524a and 525a.
>>>
>>> But as a side effect it breaks ASPM support for all the other device-ids,
>>> causing e.g. the Haswell CPU on a Lenovo T440s to not go into a higher
>>> c-state then PC3, while previously it would go to PC7, causing the
>>> machine to idle at 7.4W instead of 6.6W!
>>>
>>> The problem here is the new option.dev_aspm_mode field, which only gets
>>> explicitly initialized in the new code for the device-ids 5249 524a and
>>> 525a. Leaving the dev_aspm_mode 0 for the other device-ids.
>>>
>>> The default dev_aspm_mode 0 is mapped to DEV_ASPM_DISABLE, but the
>>> old behavior of calling rtsx_pci_enable_aspm() when idle and
>>> rtsx_pci_disable_aspm() when busy happens when dev_aspm_mode ==
>>> DEV_ASPM_DYNAMIC.
>>>
>>> This commit changes the enum so that 0 = DEV_ASPM_DYNAMIC matching the
>>> old default behavior, fixing the pm regression with the other device-ids.
>>>
>>> Cc: Rui Feng <rui_feng@realsil.com.cn>
>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>
>> p.s.
>>
>> 2 remarks:
>>
>> 1. As this is a regression in 4.15, please queue this up as a fix for 4.15
>>     (I prioritized bisecting this, which took me a whole day to get a fix
>>      ready in time for 4.15).
> 
> If this is aimed at -the rcs, you should apply a Fixes: tag.

Right, I should have thought of that myself.

> Happy to do it for you this time.

Thanks you.

Regards,

Hans

  reply	other threads:[~2017-12-06 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 11:21 Hans de Goede
2017-12-06 11:31 ` Hans de Goede
2017-12-06 15:42   ` Lee Jones
2017-12-06 15:44     ` Hans de Goede [this message]
2017-12-07  2:38   ` 答复: " 冯锐
2017-12-07  9:28     ` Lee Jones
2017-12-07  9:36       ` 答复: " 冯锐
2017-12-07  9:48 ` Lee Jones

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=906755d5-45b4-c4d0-e4b7-e501e5e7b450@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui_feng@realsil.com.cn \
    /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

Powered by JetHome