mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Gwendal Grignou <gwendal@chromium.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Tejun Heo <tj@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	alan.cox@intel.com,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	rajatja@chromium.org
Subject: Re: [PATCH 0/2] ata: libahci: devslp fixes
Date: Thu, 7 Mar 2019 21:37:30 +0100	[thread overview]
Message-ID: <54d2b8e6-332b-117a-b982-77a535152246@redhat.com> (raw)
In-Reply-To: <CAMHSBOVOK15nchZRFGTZUu8KSbBiK3SFzgW1amLjXb1iv_gJ5g@mail.gmail.com>

Hi,

On 07-03-19 21:27, Gwendal Grignou wrote:
> Srinivas,
> 
> I am looking at problem on a laptop machine that suspends to S01x, but
> link_management is set to max_performance, because the machine is
> connected to a charger.

What is setting it to max_performance when charging?  I assume chrome-os is
running something in userspace to do this (like TLP, but I guess you are not
using TLP) ?

Have you run benchmarks with max_performance vs the default?
I seriously doubt there will be a significant difference, esp.
with a chrome-os style workload.

> Given DVLSP must be set before the laptop suspends ["""One of the
> requirement for modern x86 system to enter lowest power mode  (SLP_S0)
> is SATA IP block to be off."""], the machine never reaches S01x.
> Does it make sense to change the target_lpm_policy at suspend
> (ata_port_suspend()) to min_power and bring it back to the original
> value on resume?

If userspace messes with the setting, then userspace should also
put it back before suspending...

The upstream kernel's default behavior is to have the target level set
to a fixed level independent of the charging state. Could it be this
fixed level is actually max-performance ? If that is the default the
kernel comes up with, that would indicate a kernel bug.

Regards,

Hans



> 
> Gwendal.
> 
> 
> On Mon, Jul 30, 2018 at 10:33 AM Tejun Heo <tj@kernel.org> wrote:
>>
>> On Mon, Jul 30, 2018 at 05:26:45PM +0200, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 30-07-18 17:22, Tejun Heo wrote:
>>>> On Mon, Jul 30, 2018 at 08:15:47AM -0700, Srinivas Pandruvada wrote:
>>>>> Hi Tejan,
>>>>>
>>>>> On Mon, 2018-07-02 at 12:01 -0700, Srinivas Pandruvada wrote:
>>>>>> Some minor fixes to be able to correctly set devslp register
>>>>>> to optimize power.
>>>>>>
>>>>>> Srinivas Pandruvada (2):
>>>>>>    ata: libahci: Correct setting of DEVSLP register
>>>>>>    ata: libahci: Allow reconfigure of DEVSLP register
>>>>>>
>>>>> Are you applying this series?
>>>>
>>>> I was waiting for Hans's reviews.  Hans, what do you think?
>>>
>>> Ah I missed that this was another series. With the caveat that
>>> I do not really know that much about devslp, both patches
>>> seem sensible to me, so both are:
>>>
>>> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
>>
>> Applied 1-2 to libata/for-4.19.
>>
>> Thanks.
>>
>> --
>> tejun
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2019-03-07 20:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 19:01 Srinivas Pandruvada
2018-07-02 19:01 ` [PATCH 1/2] ata: libahci: Correct setting of DEVSLP register Srinivas Pandruvada
     [not found]   ` <CAAtuYK9zXJHhJ8_aRqfqOPJJ9L29patDA9RuUs9r+GJVZMCy=Q@mail.gmail.com>
2018-07-17  3:43     ` Srinivas Pandruvada
2018-07-02 19:01 ` [PATCH 2/2] ata: libahci: Allow reconfigure " Srinivas Pandruvada
2018-07-30 15:15 ` [PATCH 0/2] ata: libahci: devslp fixes Srinivas Pandruvada
2018-07-30 15:22   ` Tejun Heo
2018-07-30 15:26     ` Hans de Goede
2018-07-30 17:33       ` Tejun Heo
2019-03-07 20:27         ` Gwendal Grignou
2019-03-07 20:37           ` Hans de Goede [this message]
2019-03-07 23:07             ` Rajat Jain
2019-03-08  0:04               ` Srinivas Pandruvada
2019-03-08  8:57                 ` Hans de Goede
2019-03-08 19:29                   ` Rajat Jain
2019-03-11  7:52                     ` Gwendal Grignou

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=54d2b8e6-332b-117a-b982-77a535152246@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alan.cox@intel.com \
    --cc=gwendal@chromium.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rajatja@chromium.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tj@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

all inboxes | Powered by JetHome®