Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp1731272rwl; Fri, 24 Mar 2023 14:52:48 -0700 (PDT) X-Google-Smtp-Source: AKy350ZJdHElETcigD/lmrQlfL9yNhQhLdR/7UlVsi9vKJfGu410yIQQfBV1djf1FVhX8eWIYQox X-Received: by 2002:aa7:c318:0:b0:4fe:961d:cab0 with SMTP id l24-20020aa7c318000000b004fe961dcab0mr4201715edq.5.1679694767872; Fri, 24 Mar 2023 14:52:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679694767; cv=none; d=google.com; s=arc-20160816; b=s09uHds/k+ywiqzbDKgmCfw6fu55yOVzGLsclJUw3L/JywXC4e9RZRAhJ/Nr58Uw6C QHfwoJNgp0Q1eB7z3bDPMlQ0YClyP6c9M+T56nZ63n3g9AdiiiOcJt4MqMC7Cs3T8PFq z3gGbOLxiiJh8X6xa60OCVn9xZi+Fsa14fmOvelY9t8HdUNqZcnlEaNJekQ+YXzMRhQC O9v3uW82sMAZRdwensx3R2ZfbVII1aSAlKbfvY+T7DQ6xty3LOCWDpvvU3aWYUHCJO99 8Bn8ql9Y093Vo/yCdXTRIkqdisPyMrx8N3OmpR+tD5Gg/1BMvP0X7DqJYAHymDNV+P7C 8upw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:subject:cc:to:from :dkim-signature; bh=GxFN1Mz02uScJLXQDqm29cATi91Hixspz+FPWGqEbGc=; b=DpPI3NZvXQjPTnONWcA2YZA5y+mO8YHc+Mk/hxGxtfnO/KTZk9+McCCpQnn00n5FgN SdM7LpHGYPfGVzPpG2ESNgWstDLgLZmyYtzZLRVBi+Bt9D/Nck9DoLPDbcP0PbDhtliU EL3/TEToGdeGkbTsea7hEV01Z6b1yWjLmDxNjjv0QQSV6xUKZ4dIx0p4Cqfsxvlr6CWn ReH3pbZT/A5JiRsm7pZP2A1IXl5pxjJK4+VNm4vaNy+mxDZRMjMQFiXabibndS8mNTAK pStmPEgJ+FkT+itrUYujBWwhkOL+OjsX5ZlPPGTavjUpiyDSjGzM+fxMUpFZ5fXzKD8F 03OQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=KG3HQmQd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w10-20020aa7da4a000000b004acd3188052si21860513eds.558.2023.03.24.14.52.23; Fri, 24 Mar 2023 14:52:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=KG3HQmQd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232206AbjCXVsW (ORCPT + 99 others); Fri, 24 Mar 2023 17:48:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55936 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232021AbjCXVsL (ORCPT ); Fri, 24 Mar 2023 17:48:11 -0400 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0BA026587; Fri, 24 Mar 2023 14:48:07 -0700 (PDT) Received: from pps.filterd (m0279866.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 32OAt1gD004926; Fri, 24 Mar 2023 21:48:05 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=from : to : cc : subject : date : message-id; s=qcppdkim1; bh=GxFN1Mz02uScJLXQDqm29cATi91Hixspz+FPWGqEbGc=; b=KG3HQmQdLobbKfvcVkdAD/fXU7ZHvJRvtBaNXTBXu3pNPii24UhG9Lr5nFN2usMMe+cE QgDksW4BriMOOYAqWD9PSLH/fFwHlVurwkw4yXBOwyRqy41N5l4RiKNNVrQ6V3wKUFmW eyLqoO0Mrv9l8u0vXfL5R2/E056B9f9rm6wtcpns27X74cn4pOK4AB6fafDmO0wX/Q0O hyfioZJFTk45HmJZyFd9SHRHYybYeI7gQWCnwdC1FC6n95yPTIFtFG+fQTCEGIUqtRbC au9Zd/C/G2GMD6vuC2+L6tEHCsn0BIXkul51bba8UVBCJy5G8YHDq3mWQcWwaqw2YN0r SA== Received: from nalasppmta01.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3pgyeeb5a3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 24 Mar 2023 21:48:05 +0000 Received: from pps.filterd (NALASPPMTA01.qualcomm.com [127.0.0.1]) by NALASPPMTA01.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTP id 32OLm4e7003626; Fri, 24 Mar 2023 21:48:04 GMT Received: from pps.reinject (localhost [127.0.0.1]) by NALASPPMTA01.qualcomm.com (PPS) with ESMTP id 3phhr8rp9n-1; Fri, 24 Mar 2023 21:48:04 +0000 Received: from NALASPPMTA01.qualcomm.com (NALASPPMTA01.qualcomm.com [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 32OLm4eV003620; Fri, 24 Mar 2023 21:48:04 GMT Received: from hu-devc-lv-c.qualcomm.com (hu-eserrao-lv.qualcomm.com [10.47.235.164]) by NALASPPMTA01.qualcomm.com (PPS) with ESMTP id 32OLm4mS003616; Fri, 24 Mar 2023 21:48:04 +0000 Received: by hu-devc-lv-c.qualcomm.com (Postfix, from userid 464172) id 181F320DAB; Fri, 24 Mar 2023 14:48:04 -0700 (PDT) From: Elson Roy Serrao To: gregkh@linuxfoundation.org, Thinh.Nguyen@synopsys.com Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, quic_wcheng@quicinc.com, quic_jackp@quicinc.com, Elson Roy Serrao Subject: [PATCH v13 0/6] Add function suspend/resume and remote wakeup support Date: Fri, 24 Mar 2023 14:47:56 -0700 Message-Id: <1679694482-16430-1-git-send-email-quic_eserrao@quicinc.com> X-Mailer: git-send-email 2.7.4 X-QCInternal: smtphost X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: 0d_7N7vc5AWcuUDhqHSs50_bkhk0IJjY X-Proofpoint-ORIG-GUID: 0d_7N7vc5AWcuUDhqHSs50_bkhk0IJjY X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-03-24_11,2023-03-24_01,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 adultscore=0 lowpriorityscore=0 suspectscore=0 clxscore=1015 mlxlogscore=746 malwarescore=0 phishscore=0 priorityscore=1501 mlxscore=0 bulkscore=0 impostorscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303200000 definitions=main-2303240166 X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Changes in v13 - Added function suspend feature selector handling and related functionalities in composite layer and removed them from f_ecm. This will also lay a generic framework for other functions to use. Changes in v12 - Added a new patch to arm the function for triggering remote wakeup based on the function suspend packet sent by the host. Also handle get_status in composite layer as default. - Removed set/reset of func_wakeup_armed flag in f_ecm and let composite layer handle it Changes in v11 - When ecm function suspend is called return negative error only if host is trying to arm for function wakeup and device is not wakeup capable. Changes in v10 - Modified the return value to 0 in ecm_get_status() so that device responds with both remote wakeup armed and remote wakeup capable bit reset to 0. - Return negative errno if wakeup is not supported when func suspend feature selector is sent by the host. Changes in v9 - Added bmAtrributes wakeup bit check for arming the function for function remote wakeup and also in get_status api Changes in v8 - Added else case to return error value while setting remote wakeup feature selector so that device will respond with a protocl stall Changes in v7 - Added a check to set device remote wakeup feature selector in ep0.c based on whether the device is configured for remote wakeup. - Commit message and usb_func_wakeup documentation changes. Changes in v6 - Combined usb_gadget_func_wakeup API with usb_func_wakeup API in composite layer so that there is only 1 API for triggering function remote wakeup for better error handling. Since function suspend is something specific to usb functions, better to keep the related APIs in composite layer and above. Also documented the usage and applicability of the usb_func_wakeup API. Changes in v5 - Add wakeup_armed check in patch2 in the link status change event handler so that resume gets triggeed only in the remote wakeup context. - Costmetic changes in patch3 and patch4 Changes in v4 - Moved the wakeup bit check to bind function for warning the user at an early stage itself. - Added the remote wakeup configured check to gadget_wakeup() and func_wakeup() routines so that wakeup can be triggered only if user has configured it. - Cosmetic changes with respect to renaming the variables to reflect the operation better. Changes in v3 - Modified rw_capable flag to reflect the gadgets capability for wakeup signalling. - Added a check to configure wakeup bit in bmAttributes only if gadget is capable of triggering wakeup. - Implemented a gadget op for composite layer to inform UDC whether device is configured for remote wakeup. - Added a check in __usb_gadget_wakeup() API to trigger wakeup only if the device is configured for it. - Cosmetic changes in dwc3_gadget_func_wakeup() API. Changes in v2 - Added a flag to indicate whether the device is remote wakeup capable. - Added an async parameter to _dwc3_gadget_wakeup() API and few cosmetic changes. - Added flags to reflect the state of function suspend and function remote wakeup to usb_function struct rather than function specific struct (f_ecm). - Changed the dwc3_gadget_func__wakeup() API to run synchronously by first checking the link state and then sending the device notification. Also added debug log for DEVICE_NOTIFICATION generic cmd. - Added changes to arm the device for remotewakeup/function remotewakeup only if device is capable. An usb device can initate a remote wakeup and bring the link out of suspend as dictated by the DEVICE_REMOTE_WAKEUP feature selector. To achieve this an interface can invoke gadget_wakeup op and wait for the device to come out of LPM. But the current polling based implementation fails if the host takes a long time to drive the resume signaling specially in high speed capable devices. Switching to an interrupt based approach is more robust and efficient. This can be leveraged by enabling link status change events and triggering a gadget resume when the link comes to active state. If the device is enhanced super-speed capable, individual interfaces can also be put into suspend state. An interface can be in function suspend state even when the device is not in suspend state. Function suspend state is retained throughout the device suspend entry and exit process. A function can be put to function suspend through FUNCTION_SUSPEND feature selector sent by the host. This setup packet also decides whether that function is capable of initiating a function remote wakeup. When the function sends a wakeup notification to the host the link must be first brought to a non-U0 state and then this notification is sent. This change adds the infrastructure needed to support the above functionalities. Elson Roy Serrao (6): usb: gadget: Properly configure the device for remote wakeup usb: dwc3: Add remote wakeup handling usb: gadget: Add function wakeup support usb: dwc3: Add function suspend and function wakeup support usb: gadget: Handle function suspend feature selector usb: gadget: f_ecm: Add suspend/resume and remote wakeup support drivers/usb/dwc3/core.h | 5 ++ drivers/usb/dwc3/debug.h | 2 + drivers/usb/dwc3/ep0.c | 19 +++--- drivers/usb/dwc3/gadget.c | 118 ++++++++++++++++++++++++++++++-- drivers/usb/gadget/composite.c | 123 ++++++++++++++++++++++++++++++++-- drivers/usb/gadget/configfs.c | 3 + drivers/usb/gadget/function/f_ecm.c | 22 ++++++ drivers/usb/gadget/function/u_ether.c | 63 +++++++++++++++++ drivers/usb/gadget/function/u_ether.h | 4 ++ drivers/usb/gadget/udc/core.c | 27 ++++++++ drivers/usb/gadget/udc/trace.h | 5 ++ include/linux/usb/composite.h | 8 +++ include/linux/usb/gadget.h | 9 +++ 13 files changed, 389 insertions(+), 19 deletions(-) -- 2.7.4