Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp2591020pxb; Mon, 19 Apr 2021 09:05:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzucS/2nlziC8BwwABMIegXp78dcLAedsj2G3vNb9v8Sidh/fFvyd1qOIEqpragPBLyqTkw X-Received: by 2002:a17:906:95cb:: with SMTP id n11mr23399853ejy.251.1618848346206; Mon, 19 Apr 2021 09:05:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618848346; cv=none; d=google.com; s=arc-20160816; b=uAQgs9A6P8JdfPK/kSOq7pJPR7wbeoVA2h5iwQmVxRE+PhSO1GKrMGfB6BHEC8nIpZ mHrkuVnBA4nMr5jsMhBRFzFUGnqH0HVfCgGTNbsYx1V2gWyGUosv4n90Zun8cBQIoT0H mk+7HRhCPcf+sFfq7Za0RxgnjFDVHT9acnEc+s7GbmQtoQ1Og/Xv70ekeqwD6ffmXWAd i6SR3VGGNSPJLguvoLf6aqzTycuvgJyObjYKnCj3jqPEwylmJEQrbzv7ZEZTN2exkj9j CY2FzzVQWcc6sLAdF300sZ/gAdyCw++FOm9D/OPUtjD4qxBwy1KZKn66h2a64MxBowYf DFUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=ELijVMdmKQI4Lt+gop2Lya/Skiu3/iOAz2Kx+AVBcys=; b=nZpxJDRqoamo2Yp/F3LN5f+l0bgFZzNBkUmof2uoJ7Rv65JT1X3ZMBvhj+2onhsI8j n8c9ahlMIXteL+/oTwyM3Bep/uL9Ef6mKw+Rx/hRUeK2A0XvRCk09dRvzyU1kpEUn3Fg 7To8M/FtfaLnS8oKr345QeabFw23QWwPFbf7vhK4P6ib3csYJgWZEiHlUYBD4eD4+xBg DXsnlbLFpTBHlKeZnamPBs5uYd7muIb0lS/ieletA9macH+piRDuC0C4CwWA97tjiIen nnqYEhZL6Fw7a/1JJBOJmBq2KWdb9IF9vERgH1kH2HMpRK3pXHKGj6xE50ewWVDkCxoH 2Nlw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dp5si13041502ejc.284.2021.04.19.09.05.21; Mon, 19 Apr 2021 09:05:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238209AbhDSOT5 (ORCPT + 99 others); Mon, 19 Apr 2021 10:19:57 -0400 Received: from netrider.rowland.org ([192.131.102.5]:52119 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S232452AbhDSOTz (ORCPT ); Mon, 19 Apr 2021 10:19:55 -0400 Received: (qmail 134732 invoked by uid 1000); 19 Apr 2021 10:19:21 -0400 Date: Mon, 19 Apr 2021 10:19:21 -0400 From: Alan Stern To: Chris Chiu Cc: Greg KH , m.v.b@runbox.com, hadess@hadess.net, linux-usb@vger.kernel.org, Linux Kernel Subject: Re: [PATCH v3] USB: Don't set USB_PORT_FEAT_SUSPEND on WD19's Realtek Hub Message-ID: <20210419141921.GA133494@rowland.harvard.edu> References: <20210415114856.4555-1-chris.chiu@canonical.com> <20210415184637.GA15445@rowland.harvard.edu> <20210416153932.GD42403@rowland.harvard.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 19, 2021 at 01:11:38AM -0400, Chris Chiu wrote: > Sorry that I didn't make myself clear. I found that if I applied RESET_RESUME > quirk on the problematic hub, the Set-Port-Feature(suspend) timeout error > disappeared. SInce the timeout is not happening for each suspend by default, > I suspect maybe reset-resume take everything back to clean state for the hub > and the Set-Port-Feature(suspend) can be taken care of w/o problems. Okay, that's a good solution for system suspend. > I didn't like RESET_RESUME because runtime PM would not work on the quirked > device. A more interesting question is whether it will work for devices plugged into the hub. Even though the hub won't be runtime suspended, the things attached to it might be. > But if the Set-Port-Feature(suspend) can't be handled and > skipped, I can't > expect the runtime PM to work for all devices connected to the hub either. > Is that right? If what I proposed in the patch can not get better > result than existing > quirk, I think using the RESET_RESUME would be a better option. Any suggestions? Try the RESET_RESUME quirk and see how well it works with runtime suspend. Alan Stern