Received: by 10.213.65.68 with SMTP id h4csp311053imn; Fri, 16 Mar 2018 04:02:25 -0700 (PDT) X-Google-Smtp-Source: AG47ELuc2ShCYTHp7WVIQzZTvWF90PaOFU7WNEhCZlr+kiaJ8FdPlR84wPnWUED3mFWnmD5JVErV X-Received: by 2002:a17:902:7088:: with SMTP id z8-v6mr1681687plk.174.1521198145839; Fri, 16 Mar 2018 04:02:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521198145; cv=none; d=google.com; s=arc-20160816; b=stQQVe2uCG0VT98EBeoq07NYUzESidp79I45oQ1pLHgmZVyD8FRv3CQ6+ZL2AtfbZg MdL4t8rUJ+oSmBh0QD/6B/F1l0x2pujtaB7d6DYUX2d4oKVkNsZ3Iw51+KdwcTl1qXIY PQHN7Q6ae4Mx9pqlhCKBpE22BRWH6wuypfBac0dc95s1NRk6QtAs7Pzb45Ts9xE6CjMG xGLlOInVgEpIbsTUpnbrS5AsC23z6CSFbJBx8D6FXXM3EUWKab1qfdj4axxlR1ilakKl XyTKj7QTbGOAwHFg0ZTECOe68USZGC2tiKgQYrnxID9N6KSrgcdnVgUdxA+SDBA769NR W+jw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:arc-authentication-results; bh=ntn63JXJlrXW7Uo7JLKz3XILuZjvw0R3IvcKL+7PWlU=; b=oPVEUS+Qyrs2XoqnkGaaVRHfTLTd2sncr+U/wFIslqLC8Aoa+yCNgNs96D/MpuBtWo Xq5RmVn/rJnBPd2fqU8vYHnynNxq5tMn3GwTNtKdlnU3I2nhvY/69X2ZiHKvpUAmaolR EaUUX1jwNLfSHF121w6cXKZpMYM5mO5LD2Hxp4XOcXbPzHLAvoUYcWU2H9TktnTBXqaK MhvVYNb9VUbjfnKX+4gMCm3Ngv6p3hSxxAW6YKHGyx2A4for8eDwoImE/onkp0w4yjsF PtD2X6DkKouneCRl4HpUA/YkKljRdmvxw44KKBMPhfh+gph5Je3lEY8y0UlnCACtRUNe Uk1g== 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 j65si4853966pgc.808.2018.03.16.04.02.10; Fri, 16 Mar 2018 04:02:25 -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 S1753613AbeCPLBE (ORCPT + 99 others); Fri, 16 Mar 2018 07:01:04 -0400 Received: from mga12.intel.com ([192.55.52.136]:25320 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753019AbeCPLBD (ORCPT ); Fri, 16 Mar 2018 07:01:03 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Mar 2018 04:01:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,315,1517904000"; d="scan'208";a="34399146" Received: from pipin.fi.intel.com (HELO localhost) ([10.237.68.37]) by FMSMGA003.fm.intel.com with ESMTP; 16 Mar 2018 04:01:00 -0700 From: Felipe Balbi To: Roger Quadros Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] usb: dwc3: Prevent indefinite sleep in _dwc3_set_mode during suspend/resume In-Reply-To: <69517684-bd39-e945-0c9e-ccd52b8050d5@ti.com> References: <1519730526-22274-1-git-send-email-rogerq@ti.com> <69517684-bd39-e945-0c9e-ccd52b8050d5@ti.com> Date: Fri, 16 Mar 2018 13:00:47 +0200 Message-ID: <87y3isffog.fsf@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Roger Quadros writes: > Hi Felipe, > > On 09/03/18 14:47, Roger Quadros wrote: >> In the following test we get stuck by sleeping forever in _dwc3_set_mode() >> after which dual-role switching doesn't work. >> >> On dra7-evm's dual-role port, >> - Load g_zero gadget driver and enumerate to host >> - suspend to mem >> - disconnect USB cable to host and connect otg cable with Pen drive in it. >> - resume system >> - we sleep indefinitely in _dwc3_set_mode due to. >> dwc3_gadget_exit()->usb_del_gadget_udc()->udc_stop()-> >> dwc3_gadget_stop()->wait_event_lock_irq() >> >> To fix this instead of waiting indefinitely with wait_event_lock_irq() >> we use wait_event_interruptible_lock_irq_timeout() and print >> and error message if there was a timeout. >> >> Signed-off-by: Roger Quadros > > Thanks for picking this for -next. > Is it better to have this in v4.16-rc fixes? > and also stable? v4.12+ Well, there was no "Fixes: foobar" or "Cc: stable" lines in the commit log ;-) The best we can do now, is wait for -rc1 and manually send the commit to stable. -- balbi