Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp5311910imb; Thu, 7 Mar 2019 12:38:41 -0800 (PST) X-Google-Smtp-Source: APXvYqzAvk0ffGJlVVUnObzYtmlcTQ4EsjtoTPmgIMhNxg49NNOC0hynRD7aUVkTjuGgo+s2kIt7 X-Received: by 2002:a62:b248:: with SMTP id x69mr14547250pfe.256.1551991121016; Thu, 07 Mar 2019 12:38:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551991121; cv=none; d=google.com; s=arc-20160816; b=sx2qtjqLZsWKDfiLjWs6gSJBGvVAt6G3RzP2fwM0ngzHhcb1eD5qXoxKxv8ve8P9e6 jyNNU7ZWBPONd9vAYaHppCvUNIp2kmJYOpd3216K/DVV8GuWeEj22c7TN9prY82EbJCf M/vIOBZ4/dcZIkbyFGuLRu8MA8PSMgLxLFMxQUZJgcI2kJ2ccVgBMvrrNYahglmogMxd P6AekZwHh6Kpk2O8491RheHPI4XBCrEthbZPF218I8uA4HROtnk69I9LV/GSHLvbknSz fwzGlNJ/GJxkdHwspoSWzBprQ0McuUQiIKAb9mDuhrIafYtYJHeaC6FNDvr478CNUcGt 9Mog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=ciakIFypHhbfberMmeiRPKsknDYsjGvDxtVRFiP5ZW4=; b=z6jW7hqXlw59hNye6Zo1w94Lw9C8OzNMY1+n9Dz+FyqyBauC/5GuwK1qWvFb6DLQIf FKA/PPcl5558/TnYAsy3muVnUlsaI0fSPBPEFf5ogSF/JyEXE4PpBTys6e29/QEGzarZ Jt/JRdQfBloNMrD/X1DOPkVc23rMiGBAt778KFFHPrXld/rEr4UgBxjkoxT6qikckUc6 Ti+MbzVap8Ct/Ho3O/GPOgsW7WvP0W+8/jKCHaR/7sZNhMU/SxmcXhR1wByGOF1MnS10 O8pAhNvluvHvvU6BJ0FRJOVX3ZulwfTEZbwEqWNDmbwFOseD1I9QmQVHSER51abunI8/ QRag== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f1si4879779plb.396.2019.03.07.12.38.24; Thu, 07 Mar 2019 12:38:41 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726319AbfCGUhe (ORCPT + 99 others); Thu, 7 Mar 2019 15:37:34 -0500 Received: from mail-wm1-f65.google.com ([209.85.128.65]:40856 "EHLO mail-wm1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726249AbfCGUhe (ORCPT ); Thu, 7 Mar 2019 15:37:34 -0500 Received: by mail-wm1-f65.google.com with SMTP id g20so10471130wmh.5 for ; Thu, 07 Mar 2019 12:37:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ciakIFypHhbfberMmeiRPKsknDYsjGvDxtVRFiP5ZW4=; b=GXCi+J4rHxqgGRFm7TX8CgXMy7w+FFayNTlJbtYxvzGntZliHEOBvU2mnUGuJRw//o QCmqYNS74KAENIWYLm818QD6LLb5ht7klqtb3er9YnTccFb4moNrL0pUiPHccSQmVudf 4f1k4IRj70rbVYaW9EsR+ZJOzveHb7dK8Zv+RwYWS4wnjTbN2xMpxwWd6m0zOch6+m9E MUVWCbVLVr+8glZ5PpBFCf5WtH+tAH25Jmmkm94kUp94ANgtqjfWjci2Sb/ICLGAEHYl wQSjTsI4OHM2tNMMPdUWeid66Iz7r81hC7VMs8trEGNjcKp1NQ/TexS8+cpl91i6vapz 1gdw== X-Gm-Message-State: APjAAAVUOJttge143mtE0gqKZqByv2uhUbpOlRuxhv/mMgOsRLHd/Vmr 6nccNof78/8ZKb9YNTqz7JbxYg== X-Received: by 2002:a7b:cb8e:: with SMTP id m14mr6370274wmi.64.1551991052620; Thu, 07 Mar 2019 12:37:32 -0800 (PST) Received: from shalem.localdomain (546A5441.cm-12-3b.dynamic.ziggo.nl. [84.106.84.65]) by smtp.gmail.com with ESMTPSA id a131sm7469946wmh.34.2019.03.07.12.37.31 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Thu, 07 Mar 2019 12:37:31 -0800 (PST) Subject: Re: [PATCH 0/2] ata: libahci: devslp fixes To: Gwendal Grignou , Srinivas Pandruvada , Tejun Heo Cc: "Rafael J. Wysocki" , alan.cox@intel.com, IDE/ATA development list , Linux Kernel , rajatja@chromium.org References: <20180702190154.6864-1-srinivas.pandruvada@linux.intel.com> <9712316ab62bef25953c523bce02e260a9ea40fe.camel@linux.intel.com> <20180730152256.GF1206094@devbig004.ftw2.facebook.com> <20180730173345.GI1206094@devbig004.ftw2.facebook.com> From: Hans de Goede Message-ID: <54d2b8e6-332b-117a-b982-77a535152246@redhat.com> Date: Thu, 7 Mar 2019 21:37:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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 >> >> 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