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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8C1B0C77B7A for ; Wed, 17 May 2023 20:01:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229550AbjEQUBf (ORCPT ); Wed, 17 May 2023 16:01:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42128 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229497AbjEQUBb (ORCPT ); Wed, 17 May 2023 16:01:31 -0400 Received: from netrider.rowland.org (netrider.rowland.org [192.131.102.5]) by lindbergh.monkeyblade.net (Postfix) with SMTP id 3049F5B8E for ; Wed, 17 May 2023 13:01:29 -0700 (PDT) Received: (qmail 887386 invoked by uid 1000); 17 May 2023 16:01:28 -0400 Date: Wed, 17 May 2023 16:01:28 -0400 From: Alan Stern To: Badhri Jagan Sridharan Cc: gregkh@linuxfoundation.org, colin.i.king@gmail.com, xuetao09@huawei.com, quic_eserrao@quicinc.com, water.zhangjiantao@huawei.com, peter.chen@freescale.com, balbi@ti.com, francesco@dolcini.it, alistair@alistair23.me, stephan@gerhold.net, bagasdotme@gmail.com, luca@z3ntu.xyz, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Francesco Dolcini Subject: Re: [PATCH v1] usb: gadget: udc: core: Offload usb_udc_vbus_handler processing Message-ID: References: <20230517115955.1078339-1-badhri@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 17, 2023 at 10:19:25AM -0700, Badhri Jagan Sridharan wrote: > On Wed, May 17, 2023 at 7:44 AM Alan Stern wrote: > > > > On Wed, May 17, 2023 at 11:59:55AM +0000, Badhri Jagan Sridharan wrote: > > > chipidea udc calls usb_udc_vbus_handler from udc_start gadget > > > ops causing a deadlock. Avoid this by offloading usb_udc_vbus_handler > > > processing. > > > > Surely that is the wrong approach. > > > > The real problem here is that usb_udc_vbus_handler() gets called from > > within a udc_start routine. But this is totally unnecessary, because > > the UDC core will call usb_udc_connect_control_locked() itself, later on > > during gadget_bind_driver(). > > Hi Alan, > > usb_udc_vbus_handler sets the udc->vbus flag as well apart from > calling usb_udc_connect_control_locked(). So, removing usb_udc_vbus_handler > from chip specific start callback might prevent the controller from > starting. > > void usb_udc_vbus_handler(struct usb_gadget *gadget, bool status) > { > struct usb_udc *udc = gadget->udc; > > mutex_lock(&udc->connect_lock); > if (udc) { > udc->vbus = status; > usb_udc_connect_control_locked(udc); Then add "udc->vbus = true;" at the appropriate spot in gadget_bind_driver(). Alan Stern PS: I just noticed that in max3420_udc.c, the max_3420_vbus_handler() function calls usb_udc_vbus_handler() from within an interrupt handler. This won't work, since interrupt handlers aren't allowed to sleep and therefore can't lock mutexes.