Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp865820pxb; Wed, 6 Apr 2022 02:31:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwr91VXSu05kZSsHA0sK9tXhDdnTulY5tG6HXlo5SzBHXK7faIC6r8MzCocv23X/nVXlhtH X-Received: by 2002:a05:6a00:1a88:b0:4fa:9a8c:c05f with SMTP id e8-20020a056a001a8800b004fa9a8cc05fmr8098033pfv.46.1649237497072; Wed, 06 Apr 2022 02:31:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649237497; cv=none; d=google.com; s=arc-20160816; b=Db9HawpI0sj4fHr1/HmmHPsFWZBDT3UXXbqlftR8javjVPEuWqQ8XEAzDlgGsgPQej HqEsulHq9XLbewzqO3qoRgyYT95KzlrNfU3SRbvT0NEMJ8KE6aO8xJFRScW3pWB5EkPK z5MhvxTYWxvOutW0u6BY+v+xx3F6++9dxHWO5mLO5B628Mryc2vdykSNTh0troVPlpoU hODyEIXGNbZyrNJZXsyPXm5/MumqJJmvOB2YNCB+Iw14ZlK5aNkbnEMmppTfengW7jlp Z5e6f/O6pRhJ8CG++BS6MUf8GilsSqP4zVvrXa0cm3OYl60BHvCKKbHO9MvFlQMZ3VVm c++A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=EEtsp+K2HLuvKRCWNAk1iWCns3ByXKMb0kNOEYvawJU=; b=yw1AFlHLXtbyQ8TSm8kqtOLFFIfU0vUFkGr2B4xg8g34RrRYTsR9q2DvFAIMrBg8Hr jU2Q42HDI7jLjVc5z7MaKomzikiIO/05cWBSeu3CTPL4IRhO86hMQl2LGnRMVsN36X00 N8GfPD8p6nkMvUzhfuTsAR1bADFVgcigzKVn/XtaXt2xQrf2+J9jxzlWU89LGRGIyfRL W8AOmUCTQrEMfNbrOkswTS77WAZlrX4IUVe8mcsQbu1CgCaUSCRQ/0vVtAzlmQlbwfOW mTeAEOLtDMA8aDNeXrJYRmlcbG2XFQ9eCOG13Py14L3EykdkgoW/ok3AQ64cLQCGRcPI 0voA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Jxc7Wj5d; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id e17-20020a631e11000000b00382044ef7afsi16021077pge.779.2022.04.06.02.31.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Apr 2022 02:31:37 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Jxc7Wj5d; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id C627F522A53; Wed, 6 Apr 2022 01:03:17 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1846135AbiDFCC4 (ORCPT + 99 others); Tue, 5 Apr 2022 22:02:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56044 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1454028AbiDEP5t (ORCPT ); Tue, 5 Apr 2022 11:57:49 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D545167F87; Tue, 5 Apr 2022 08:03:00 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id DEB3C6179F; Tue, 5 Apr 2022 15:02:59 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EB57BC385A4; Tue, 5 Apr 2022 15:02:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1649170979; bh=qNv9WCGw+H4LJDj4fT2rA98UYD02WLOHpYP7c+6zAxU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Jxc7Wj5dW0eM8sgkO1wX3113Q5/56VIuZs3gNSexvnbVAgzV2iDk7oiXCV9x/jAOr Hbs1KRTXzrpGvuCd9gnbxAURMYmfjIW6T7bkvOG2sZqHPkX8ZFEGRekFM1VFcOc9Sy x8qkS/8jN/R2vWMCk8/RlnYuB3Xs1y2A1cZKBJcI= Date: Tue, 5 Apr 2022 17:02:56 +0200 From: Greg Kroah-Hartman To: Sean Anderson Cc: linux-usb@vger.kernel.org, Robert Jarzmik , Felipe Balbi , linux-kernel@vger.kernel.org, Rob Herring , devicetree@vger.kernel.org Subject: Re: [PATCH 0/4] usb: phy: generic: Support enabling/disabling VBUS Message-ID: References: <20220114170941.800068-1-sean.anderson@seco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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 On Tue, Apr 05, 2022 at 10:51:34AM -0400, Sean Anderson wrote: > > > On 1/14/22 12:09 PM, Sean Anderson wrote: > > The generic USB phy has had VBUS-related code for a long time, but it > > has always been broken, since the regulator was never gotten from the > > device tree. However, the support itself seems not very useful, since > > e.g. usb_phy_vbus_on/off has no users and usb_phy_set_power is only > > used by gadgets to make sure they don't draw too much current. Instead, > > use the VBUS regulator to implement otg_set_vbus, which is called from > > several drivers. This results in a change in semantics of VBUS, but > > since support was always broken I don't think this will have any affect. > > > > > > Sean Anderson (4): > > dt-bindings: usb: usb-nop-xceiv: Repurpose vbus-regulator > > usb: phy: generic: Get the vbus supply > > usb: phy: generic: Implement otg->set_vbus > > usb: phy: generic: Disable vbus on removal > > > > .../bindings/usb/usb-nop-xceiv.yaml | 8 +-- > > drivers/usb/phy/phy-generic.c | 55 +++++++++---------- > > 2 files changed, 31 insertions(+), 32 deletions(-) > > > > ping? > > When this was submitted I got an email saying that the merge window was > closed... but I think it has opened and closed again during the > intervening time. It opened yesterday. Please give us a chance to catch up. While that happens, please take the time to review other changes on the mailing lists, we can always use the help. thanks, greg k-h