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, URIBL_BLOCKED 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 66CE1C3A59F for ; Tue, 27 Aug 2019 02:50:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3A6CD20850 for ; Tue, 27 Aug 2019 02:50:12 +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="OgO/muqh" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728652AbfH0CuL (ORCPT ); Mon, 26 Aug 2019 22:50:11 -0400 Received: from mail-qk1-f193.google.com ([209.85.222.193]:40641 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727887AbfH0CuL (ORCPT ); Mon, 26 Aug 2019 22:50:11 -0400 Received: by mail-qk1-f193.google.com with SMTP id f10so1328366qkg.7 for ; Mon, 26 Aug 2019 19:50:11 -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=T2iPkJ7pf5gy03ZtFr13YyLMEqBiyBna8KsbdE4uLh4=; b=OgO/muqhVUTgi3797A1/YaOoRiSxfCK9qTOuvdSWVO5kgttxZF8bud0CU1Q+TemszI F4o710BbkBQiYhrPmrHcDtNOUH+xryGN5/3OjKQ5qLMZ5LZDeRnL+hif3HB1kLzLtwhI 9ed8gSxB4BgFPl432UuxuSCczBxpr9m5bO+SoILvSPaonHHooutjIR4fjNbRLmdXduIp ZqFB7LiPb4vVfZ3+79KXKqVuTdRgwrOKGi9eFejvI4xdoLgugjdZwYUsv2rg/gGfy4Y5 EccSsMFQ7WD0PlCK43idSM/yPkdr0QGnkn4AUgnHESF3RfdIrFIjUjO9S2f748Vq9IjJ iS5g== 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=T2iPkJ7pf5gy03ZtFr13YyLMEqBiyBna8KsbdE4uLh4=; b=DzvRTy5JXi4xYLIlVZyMqza3FoJZZ6xUgPev2Sb2o0NCJewouTCQqcJeeSx1ZPMBEg 5aCetot0schNZ6EMC7j/j3efc0RfjltOGAjWtc4KIemyR+h2JqWNIzD9iQiryAUiftt8 OOwuRwX/O58eAnA3xzNrfWS35e3Utk/bU5OWPZGWcnaYNMnamAK0PYtUURPAhD22JecB iMmWXlfdanwNkN+aRnSo3iAOZeCMdnpQmo/tJy8fefAT01ZUxVoH4+x/FiGcYmibuUkX jhfrzEmZRgS6ES7tonCWSdYjIUbRCiaiv0GUwCQXW1E/Oeet3bi+eCsDlhQdSuJ0skdg Th6g== X-Gm-Message-State: APjAAAUK31o0Z/dwtCkvBZUI+qGhJFq4fD984WY4tDZBmRrWLtJBnv8f hQfvXjKHIVqFL3tzo3ebwSWjVmWyQtLX19OWcX+Cxvau X-Google-Smtp-Source: APXvYqyorHsPxknELIV3kZZaAxlw5KcVXN96cPbvisDKUGVl/1XaqwDQWul4lUcEGTeWYKVYdyq/febIl7qMeZWHlzk= X-Received: by 2002:ae9:c206:: with SMTP id j6mr19308064qkg.14.1566874210753; Mon, 26 Aug 2019 19:50:10 -0700 (PDT) MIME-Version: 1.0 References: <01cf6be6-9175-87ca-f3ad-78c06b666893@linux.intel.com> In-Reply-To: <01cf6be6-9175-87ca-f3ad-78c06b666893@linux.intel.com> From: Daniel Drake Date: Tue, 27 Aug 2019 10:49:59 +0800 Message-ID: Subject: Re: Ryzen7 3700U xhci fails on resume from sleep To: Mathias Nyman Cc: "Rafael J. Wysocki" , Linux USB Mailing List , Linux PCI , Linux PM , Endless Linux Upstreaming Team Content-Type: text/plain; charset="UTF-8" Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Mon, Aug 26, 2019 at 9:32 PM Mathias Nyman wrote: > On 26.8.2019 12.29, Rafael J. Wysocki wrote: > > I wonder if you can reproduce this with the pm-s2idle-rework branch > > from linux-pm.git merged in. > > Root cause looks similar to: > https://bugzilla.kernel.org/show_bug.cgi?id=203885 > > Mika wrote a fix for that: > https://lore.kernel.org/linux-pci/20190821124519.71594-1-mika.westerberg@linux.intel.com/ Thanks for the suggestions. Mika's patch was already applied then reverted, I applied it again but there's no change. Also merging in pm-s2idle-rework doesn't make any difference. Any other ideas? Or comments on my findings so far? Given that I can't shift D0-D3-D0 reliably directly with setpci before loading the driver, is that indicative of a fundamental problem with the platform, or is my test invalid? Or in terms of other ways of testing the power transition outside of the suspend path, if a PCI dev is runtime suspended with no driver loaded, should Linux not be attempting to put it into D3? Thanks Daniel