From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2B20C47404 for ; Mon, 14 Oct 2019 06:18:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 91D2920882 for ; Mon, 14 Oct 2019 06:18:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=endlessm-com.20150623.gappssmtp.com header.i=@endlessm-com.20150623.gappssmtp.com header.b="Dexi5+e+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729903AbfJNGSU (ORCPT ); Mon, 14 Oct 2019 02:18:20 -0400 Received: from mail-qk1-f194.google.com ([209.85.222.194]:40275 "EHLO mail-qk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725936AbfJNGSU (ORCPT ); Mon, 14 Oct 2019 02:18:20 -0400 Received: by mail-qk1-f194.google.com with SMTP id y144so14894324qkb.7 for ; Sun, 13 Oct 2019 23:18:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=endlessm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FqKcVf6BlzXJcN3Dn+3SB+F5+GJnbOOd5dOqKoYVFbQ=; b=Dexi5+e+0aNyT+H4oup4xfEmK8vXVLM1adv2RBkDnZW7A8lrje9aaLZBu7g8WFEIOq e+zCaPWI7RwJrdB8+psBjEJ6QAkansjm22bMh9HNtuxY090wnm0uV1r/x1by2f0aHL4P XSrp1m+CPyQLvv3c5UMSnRJXfvAcSpj7jHKe5CoGlY3SDJgU7zkBvcAMokXz5yODEI2K Ek4v3tHipCXet9gCTCd1Vfpf5ciXpjmr5/GfOjNl0uAnsJbfxeUkkMkNk5/NEb4RKdA0 shWzZzLsdFIV0powDfrCmSEurELoLFxD/hOzL+Y90EvhanJ0n33qlgmLozemlc4cJld8 VBmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FqKcVf6BlzXJcN3Dn+3SB+F5+GJnbOOd5dOqKoYVFbQ=; b=F+0xULp1hDCSgH1apXuFkoFwYRGJ2icYPDC+PFl3wzTCJCMkxX9kusplrGfptdaSFS JZRChunAyt8YLevRt8nD0UItFtU0YQP/HRH6kY+bN/coewvigq2XoVV078yEGqneSJd8 aeBaU/2lQaCU5i0U9LNgL/FdskbdP1DyCtGEJrG4RBxYQSc2v4fksaiPYkVOX2BOjrvQ FS/lkl2Pk/AsY3NeFbueuD7ungtuDl0CVEAw2BH8TBx93ONOFT5N7mWdoRC1VLFJG8hG yWm8gYmvO8C8vOtH43bWrF8Hy7hM+Z+xfzRYyPzzGV7/N+xJRw/iluQPXzddW0FVWpsx 0DVg== X-Gm-Message-State: APjAAAXWcFqB0IwnK6YnXD3Uob3U7eTBGag9CH87SKtlWCmJ/BvnRlIP BI2JExMpU5H0xfzddUJJ7vhzT9DmW4QTC24vAy/QwA== X-Google-Smtp-Source: APXvYqwhDLUMrnCKYP6emCXVillOtZV/837gKLxFSJ6O1Ob9HCMOn9BiV/w7/6uclzMAHaN2b/EdItMMb0VXDQvp/Zs= X-Received: by 2002:a05:620a:1322:: with SMTP id p2mr27866532qkj.14.1571033897385; Sun, 13 Oct 2019 23:18:17 -0700 (PDT) MIME-Version: 1.0 References: <20190927090202.1468-1-drake@endlessm.com> <261805141.5tZyQaKU0z@kreacher> In-Reply-To: <261805141.5tZyQaKU0z@kreacher> From: Daniel Drake Date: Mon, 14 Oct 2019 14:18:06 +0800 Message-ID: Subject: Re: [PATCH] PCI: also apply D3 delay when leaving D3cold To: "Rafael J. Wysocki" Cc: "Rafael J. Wysocki" , Bjorn Helgaas , Mathias Nyman , Linux Upstreaming Team , Linux PM , Linux PCI Content-Type: text/plain; charset="UTF-8" Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Fri, Oct 11, 2019 at 6:14 PM Rafael J. Wysocki wrote: > So I think that we can use pci_restore_standard_config() in the system resume > patch too, which should address the issue as well. > > Basically, there is no reason for the PM-runtime and system-wide resume code > paths to be different in that respect. Your patch works without modification when combined with https://patchwork.kernel.org/patch/11187815/ Can you push this directly or would it be helpful if I update the commit message and submit it by email? Thanks! Daniel