Received: by 10.192.165.148 with SMTP id m20csp117924imm; Thu, 19 Apr 2018 17:29:45 -0700 (PDT) X-Google-Smtp-Source: AIpwx49icez5nVLukQ3R0E1kESl3lS+iVodWcqJTgBOk2KdOTRyRS6q/2C89eV7O4GNoShuXnuuC X-Received: by 10.99.55.1 with SMTP id e1mr6697038pga.237.1524184185273; Thu, 19 Apr 2018 17:29:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524184185; cv=none; d=google.com; s=arc-20160816; b=f4+yf5S9cRJOLVhwbpayhk/Xrn/GkCdEg2lQGITztM4FPJE5OGcvib0+sNx6QlIKjE +Yu+XrYDUMsel3gWTY9VNn31FTghyS4N5UW/Jlp4JDW7lUgBE86038gxX28obxzpcorG rzaMx4hmqKwcgtLCbJj7+0Y7A5WEN3jF84WNdfkpPq0I+5oSia/g3GVFsNlioW7palQr FVGQf7SHHtJ6awJDG6xfhQeo8EvMSqbRgdafQ0O5iHDcizHr3FBZ9uE64j29YxzNMKdd rsqnhB4K7M8JPN+MHe7fnFCJnQoUnVRdp89JHVKccRwmCSRWv0vT2tx6qRA0p820vwfa 2AFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature:arc-authentication-results; bh=/kkBl9eHvCDrr47uc1OavNPBpYLlQbwTyAgN0+sF2pM=; b=EN13fRgVsgUon545zR59bbvpzH/N4CRuMMD714CqScmtgOPRdAGSYdQDdHglGMCt5e pzhygOwC4hXxN2XjoQ5hJDpInRXeUthkPz0rpZ4WwDfRgwdzR4XY5pE/KgtIVIExN4oy SVFnAk04UK3A7I26N20WN5lNptUwlK3BR0DSKLLnaYeczecLhb+ig9zrPzIquuAEdMpF tvsuyTBcAcQmafGuF2b1G5py5eACIPzl8Ql+BxV/CXel2firFF8ckvebLzwf39cq+WNk pYM0gJtAa8HmPOuEzekixXZtzMD9TfwXHzGqKWsCUZcP5lgdkltq0JENVkQC5JPKh/p6 SZJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=IkIbZZp0; 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=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 88-v6si3318459pla.307.2018.04.19.17.29.29; Thu, 19 Apr 2018 17:29:45 -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; dkim=pass header.i=@chromium.org header.s=google header.b=IkIbZZp0; 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=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753983AbeDTA2N (ORCPT + 99 others); Thu, 19 Apr 2018 20:28:13 -0400 Received: from mail-pl0-f66.google.com ([209.85.160.66]:42512 "EHLO mail-pl0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753817AbeDTA2L (ORCPT ); Thu, 19 Apr 2018 20:28:11 -0400 Received: by mail-pl0-f66.google.com with SMTP id t20-v6so4210857ply.9 for ; Thu, 19 Apr 2018 17:28:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=/kkBl9eHvCDrr47uc1OavNPBpYLlQbwTyAgN0+sF2pM=; b=IkIbZZp0TBXMNj5sP4ZCUZ3+x6Es/uxmTkhnsx5FFVb1keLFenFa9uw2yDe4ZXHaXa 2hZRNK/pMP7EcwEw/So6AQygcZItI4YjfCkFd4Iv7x22Il3y/jKzRQ9j2JHgcxCHe725 F8BDu6qLNx2veQMrZhLiWCJsfypu+1PzG2BLA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=/kkBl9eHvCDrr47uc1OavNPBpYLlQbwTyAgN0+sF2pM=; b=DlDpVD20HmaS/+955ko/U6pcOGDsFtbgOCi5jmPawRphH+NUaObO9FJHpxSKWvW+Vv VbUCQKOcgakp7zMTLcBf8YJJQ6op1oLyNqPlbLIDJn9ZhTyZXP650UXX/q+U5viho849 t5UhMMkI3q4twrRfC/cJ51H2m5XZ1VUu/KwZ338WEmyiB+JdS6AabQCDedO94NtMdPnf Q41rMMbnbCWWzuXhVnzcNlUulmJBo8MaLGcCD9sSwTtREQkPWygkmFG4he9YQwNQKZi2 lfJUUp2158yaJQEvcmD3e56yKqFYAH6zZWRAP2qcmZuUtNScWkjRtBALuH+xO47rRwBQ 0mwA== X-Gm-Message-State: ALQs6tABOMDWfE9S3/nYoeR2b1Ta1IL6+9dkK7phHOKI1ioPnOEBUz4V zronuK665xzVv8fvyX3Ei2pr0A== X-Received: by 2002:a17:902:31a4:: with SMTP id x33-v6mr8027454plb.355.1524184091264; Thu, 19 Apr 2018 17:28:11 -0700 (PDT) Received: from ravisadineni0.mtv.corp.google.com ([2620:0:1000:1501:22d6:f20d:f2b7:3315]) by smtp.gmail.com with ESMTPSA id d83sm12402382pfl.176.2018.04.19.17.28.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Apr 2018 17:28:10 -0700 (PDT) From: Ravi Chandra Sadineni To: stern@rowland.harvard.edu, gregkh@linuxfoundation.org, martin.blumenstingl@googlemail.com, ravisadineni@google.com, chunfeng.yun@mediatek.com, johan@kernel.org, arvind.yadav.cs@gmail.com, dtor@google.com, anton.bondarenko.sama@gmail.com, f.fainelli@gmail.com, keescook@chromium.org, mathias.nyman@linux.intel.com, felipe.balbi@linux.intel.com, ekorenevsky@gmail.com, peter.chen@nxp.com, joe@perches.com Cc: tbroch@google.com, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, rajatja@google.com, bleung@google.com, Ravi Chandra Sadineni Subject: [PATCH V2] USB: Increment wakeup count on remote wakeup. Date: Thu, 19 Apr 2018 17:27:52 -0700 Message-Id: <20180420002752.181261-1-ravisadineni@chromium.org> X-Mailer: git-send-email 2.17.0.484.g0c8726318c-goog In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On chromebooks we depend on wakeup count to identify the wakeup source. But currently USB devices do not increment the wakeup count when they trigger the remote wake. This patch addresses the same. Resume condition is reported differently on USB 2.0 and USB 3.0 devices. On USB 2.0 devices, a wake capable device, if wake enabled, drives resume signal to indicate a remote wake (USB 2.0 spec section 7.1.7.7). The upstream facing port then sets C_PORT_SUSPEND bit and reports a port change event (USB 2.0 spec section 11.24.2.7.2.3). Thus if a port has resumed before driving the resume signal from the host and C_PORT_SUSPEND is set, then the device attached to the given port might be the reason for the last system wakeup. Increment the wakeup count for the same. On USB 3.0 devices, a function may signal that it wants to exit from device suspend by sending a Function Wake Device Notification to the host (USB3.0 spec section 8.5.6.4) Thus on receiving the Function Wake, increment the wakeup count. Signed-off-by: Ravi Chandra Sadineni --- drivers/usb/core/hcd.c | 2 ++ drivers/usb/core/hub.c | 10 +++++++++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c index 777036ae63674..ee0f3ec57ce49 100644 --- a/drivers/usb/core/hcd.c +++ b/drivers/usb/core/hcd.c @@ -2374,7 +2374,9 @@ static void hcd_resume_work(struct work_struct *work) void usb_hcd_resume_root_hub (struct usb_hcd *hcd) { unsigned long flags; + struct device *dev = &hcd->self.root_hub->dev; + pm_wakeup_event(dev, 0); spin_lock_irqsave (&hcd_root_hub_lock, flags); if (hcd->rh_registered) { set_bit(HCD_FLAG_WAKEUP_PENDING, &hcd->flags); diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c index f6ea16e9f6bb9..aa9968d90a48c 100644 --- a/drivers/usb/core/hub.c +++ b/drivers/usb/core/hub.c @@ -653,12 +653,17 @@ void usb_wakeup_notification(struct usb_device *hdev, unsigned int portnum) { struct usb_hub *hub; + struct usb_port *port_dev; if (!hdev) return; hub = usb_hub_to_struct_hub(hdev); if (hub) { + port_dev = hub->ports[portnum - 1]; + if (port_dev && port_dev->child) + pm_wakeup_event(&port_dev->child->dev, 0); + set_bit(portnum, hub->wakeup_bits); kick_hub_wq(hub); } @@ -3434,8 +3439,11 @@ int usb_port_resume(struct usb_device *udev, pm_message_t msg) /* Skip the initial Clear-Suspend step for a remote wakeup */ status = hub_port_status(hub, port1, &portstatus, &portchange); - if (status == 0 && !port_is_suspended(hub, portstatus)) + if (status == 0 && !port_is_suspended(hub, portstatus)) { + if (portchange & USB_PORT_STAT_C_SUSPEND) + pm_wakeup_event(&udev->dev, 0); goto SuspendCleared; + } /* see 7.1.7.7; affects power usage, but not budgeting */ if (hub_is_superspeed(hub->hdev)) -- 2.13.5