Received: by 10.213.65.68 with SMTP id h4csp1605130imn; Thu, 15 Mar 2018 04:44:34 -0700 (PDT) X-Google-Smtp-Source: AG47ELuwvTP1h8Qr70AG27vu8b/kfkQBxI9GMIhr+rsN3bQYSZCxo+LkHcZlj717e6CD2iN1YwbG X-Received: by 10.99.110.133 with SMTP id j127mr6596909pgc.79.1521114274639; Thu, 15 Mar 2018 04:44:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521114274; cv=none; d=google.com; s=arc-20160816; b=pCTZ3+T1brm8Jj6SzPIA55u+VkjGuIdzGV7vfWExlzj4rEk8LYDcoQ/9K+dReOFybU hU0Awlp4GNkB5i202ycnMmk5PQmjyL4BAb2Mrfw0DUvsN7oB68iZBI77I3W5QB56rBLd tDlnkZOay8fHpvasyVwWaDHng1gZkFubPI/V8CWuxsImP6c2W6DOkTL9JgsJcJUOIMfr tOml8GLUhRPfRYw+v1cM9IuKsfGz+WCCpjcWKSJvRTB2gXeUDjThGDL9zm8e5j2mVCTq tpSophkmPl1WlmDNTnxeKz8n4pYBAQhilMleWLyf7nRG8YB3O9ADQSdU++6J1RRLoq/3 ziZA== 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:to:subject:arc-authentication-results; bh=10Z6gPNL0saPBMF3YpRUZNbSAnVd9Ga1qF4dMGHiBXs=; b=XLJ7ixtjE/7oYuEfq4Kx134ObEQr0uSTha8uBTPwhykdmeg5EGGM19ojqL/jJX8Y1K MEiWqXiJzfXq4VySgzdl/Gd5aUXr376UGv36pnkqZFy674NKDPKIkQetcVGpinV91mPs +n5o5ly6m3xQglppCOoE5Bz4Ks7MFU/MtRKgV2FRX1DfnwATzTQ8+0YYFg8qMs0cpnUA ET92BNThUnmN1YmpERfJoRl+rrpHIAUtYPYUOZU6hrKb/O+5UAvIKnDgJ7e5lYwyJh0M E1qn2o89h/Ba4mjbGZePDvhDAuo4qxwll9jFplCQi3JhwOevlsPcjLuQV+gx7KS4ghwp LYCw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x10si3722214pfd.188.2018.03.15.04.44.17; Thu, 15 Mar 2018 04:44:34 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751966AbeCOLmq (ORCPT + 99 others); Thu, 15 Mar 2018 07:42:46 -0400 Received: from mga17.intel.com ([192.55.52.151]:38144 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751481AbeCOLmm (ORCPT ); Thu, 15 Mar 2018 07:42:42 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Mar 2018 04:42:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,310,1517904000"; d="scan'208";a="38211924" Received: from mattu-haswell.fi.intel.com (HELO [10.237.72.164]) ([10.237.72.164]) by fmsmga001.fm.intel.com with ESMTP; 15 Mar 2018 04:42:40 -0700 Subject: Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend To: Chris Chiu , mathias.nyman@intel.com, gregkh@linuxfoundation.org, linux-usb@vger.kernel.org, Linux Kernel , Linux Upstreaming Team References: From: Mathias Nyman Message-ID: <6c8df688-b456-6f07-9325-6f4dfd8f0883@linux.intel.com> Date: Thu, 15 Mar 2018 13:46:04 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15.03.2018 06:40, Chris Chiu wrote: > Hi, > I have a ASUS AIO V222GA and another Acer Desktop XC-830 both > have Intel CPU J5005 and they both hit the same problem. The XHCI > connected USB keyboard/mouse can never wakeup the system from suspend. > It reminds me that similiar thing happens on ApolloLake too which > needs the XHCI_PME_STUCK_QUIRK to get it work. It's also mentioned in > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-spec-update.pdf > page #14 for N-seris intel CPU. And I also find the same problem > description in https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/silver-celeron-spec-update.pdf > page #16 for J-series Intel CPU. Seems that they have different > workaround so I can not simply apply XHCI_PME_STUCK_QUIRK to make it > work. > > Anyone can help here? > N-Series CHP8: USB xHCI Controller May Not Re-Enter D3 State After a USB Wake Event - needs XHCI_PME_STUCK_QUIRK in driver (sets bit 28 at offset 80a4) Intel® Pentium® Silver N5000 Intel® Pentium® Silver J5005 Intel® Celeron® N4000 and N4100 Intel® Celeron® J4105 and J4005 USB xHCI Controller May Not Re-enter a D3 State After a USB Wake Even Need to clear PME_EN bit of of the standard PCI PM_CSR register. I think Linux does this anyway (clears enabling PME when reaching D0) So if I remember correct there was no specific workaround needed for this. what is the PCI ID of your xhci controller? (lspci -nn) One other possible cause is that xHCI never reaches PCI device D3 suspend state during system suspend. xHC can't generate PME# wake event from normal running PCI device D0 state. PCI code in Linux will check with ACPI about the lowest possible D state when suspending, If there is something missing from the xHCI entry in ACPI DSDT table it might select D0. as the suspend state, causing wake failure. Is there a BIOS update available for your ASUS and Acer? -Mathias