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 EAF6BECAAD1 for ; Wed, 31 Aug 2022 08:36:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231200AbiHaIgA (ORCPT ); Wed, 31 Aug 2022 04:36:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45022 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229607AbiHaIf4 (ORCPT ); Wed, 31 Aug 2022 04:35:56 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D0063DF52; Wed, 31 Aug 2022 01:35:55 -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 6EFAA619E6; Wed, 31 Aug 2022 08:35:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 53862C433C1; Wed, 31 Aug 2022 08:35:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1661934954; bh=qarNLkbsovoU00cxARj4JK5LNUtmsCMbYs74KZGYTFw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=xChazdSoYVW5s5aVqTj5k7pq6DpGnJDBFMofmNGZx5wsWbxkrFJB4ua/ShpHLnrfX Tl3b4npNAP5E5F+GOeNE9sXyU6k2Z0ZBczu3IhP37XS2aQ9Fk/4nWU9KNhhwQUOVde +CVzHjJ7r/P38SeA7+yT/N0ZsgcZrzH1ItKwOkyA= Date: Wed, 31 Aug 2022 10:35:51 +0200 From: Greg KH To: jflf_kernel@gmx.com Cc: Oliver Neukum , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] usb: add quirks for Lenovo OneLink+ Dock Message-ID: References: <20220824160946.10128-1-jflf_kernel@gmx.com> <31aeee3c-f4f1-16a8-272b-96da5d4a565e@suse.com> <4b92eee0-b020-9211-2039-18ac3ac72a7b@suse.com> <9a17ea86-079f-510d-e919-01bc53a6d09f@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9a17ea86-079f-510d-e919-01bc53a6d09f@gmx.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 31, 2022 at 09:43:02AM +0200, jflf_kernel@gmx.com wrote: > > On 31/08/2022 09.31, Greg KH wrote: > > On Tue, Aug 30, 2022 at 09:50:03PM +0200, jflf_kernel@gmx.com wrote: > >> > >> On 30/08/2022 16.47, Oliver Neukum wrote: > >> > >>> 1) force a reset after a resume and call reset_resume() instead of resume() > >>> 2) block autosuspend if remote wakeup is required > >>> > >>> I suspect you are actually using the second effect. Have you > >>> tested with "usbcore.autosuspend=-1" on the kernel command line. > >> > >> After further testing, your suspicion is correct. > >> > >> TL;DR: the two VL812 hubs don't behave well when suspended. > >> > >> I'd like to prepare a better patch for that issue. What's the recommended strategy? The current patch works, even if only as a side effect and when there's a wakeup source downstream. It's currently in Greg KH's usb-linus branch, and will land in linux-next at some point. I'm tempted to let it be and undo it later in the better patch. Is that acceptable? Or should I ask Greg KH to pull it? > > > > I can revert it if you want me to, just let me know. > > > > thanks, > > > > greg k-h > > [keeping the lists in CC this time] > > Please revert if possible, and apologies for the trouble. No problem at all, now reverted. greg k-h