Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2531654imu; Thu, 29 Nov 2018 06:29:45 -0800 (PST) X-Google-Smtp-Source: AFSGD/U3xh2c34Yy7TC7d+xEbAxAa53QiLHI71pRRkbzhJHTsfaGjXNoJP2KntJEvmVTmWIaKg3x X-Received: by 2002:a62:75d1:: with SMTP id q200mr1601678pfc.254.1543501785260; Thu, 29 Nov 2018 06:29:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543501785; cv=none; d=google.com; s=arc-20160816; b=t+ykn/nR8onMW9MguIf45zMJ0gtPI2wawGlBYQqlaK1yKUE3NYvO1vOEeYlqDiW6nW 4N2ixw5fGGUJ7uzcUFN0K0OeJBfD+ZGVtQFRpC8py6X5LLPWGpyTwMKMcWIc1u2XuV8E ncVK/yCBXMovzKAs+XfsREYHvYNUti7ntRFi4ATTDDJFXlkVBQnQ2n8VNhD/aSINVsth l9pT8g2XLMOqyMvQovacZcKPAAPtypzD06CZyK6hgnH660WeCGzJ+VWvwcFmvmu1wXco TgV5Laqev9qWhegny6FaS1bNsksCe0kUS+YA3CgPxZq/r5gmSCAMKqJbP0b4in0/Nav8 y+0g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=KaeBZcnyMsWmilhphaZEo/S9IkNvT5dtueuZy62a4+o=; b=qLBEKugxsbWgaiAHgx3q9LxCTVSgf311OZrCzBfJraXaNiWhmz4SYXsE4gdcQW4l0m 6VfyAehMFfOxi6ekaUPNok+dQoYUujqyJyzhPnaSwSvsu9c2dkTWTCDOKA/VLX34tQma I0sOg/dw+KCFW1+E2UnKK7FiEOQm5mrggre6P4c4yLU0QoZ31DA87yW+p9awheMh2xBn JJEFEAcIIm0TPOfCGpYC2/e67HsMezfhcEf+ijEnZs1+agV8VDWrrJ53Bi0dbdupkcmd Qh1k+VWoro3+SOy6CDz5ZAdgn5qxfQFFqo2BlTAiG427yY0jNg32jEtDyrwU3+K433YS 4wgQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=knNqe71F; 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 11si2090329pgs.126.2018.11.29.06.29.29; Thu, 29 Nov 2018 06:29:45 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=knNqe71F; 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 S2388207AbeK3BeY (ORCPT + 99 others); Thu, 29 Nov 2018 20:34:24 -0500 Received: from mail.kernel.org ([198.145.29.99]:35556 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731986AbeK3BeY (ORCPT ); Thu, 29 Nov 2018 20:34:24 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E41442145D; Thu, 29 Nov 2018 14:28:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1543501731; bh=qmxegUPCZuHVOI+K69giJymHcT3+DJSeHBZIsJ0E6NA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=knNqe71F16ck7p9RVg7mOqsivN2MWOKVBJYAs2jNjGzatByiuyQnEbakYMC4HxCJ9 fq1TK8z4uIChv0FL5tc61fxI8cipiYHyJbF9p3sXBjTpSCuYYdmb2wtk+25eAgFmk6 Zg7zGXvtKF5eMdYpy46xhL/n+VGC1wI+7Ie+QY7A= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Dennis Wassenberg , Mathias Nyman Subject: [PATCH 4.19 003/110] usb: core: Fix hub port connection events lost Date: Thu, 29 Nov 2018 15:11:34 +0100 Message-Id: <20181129135921.372719964@linuxfoundation.org> X-Mailer: git-send-email 2.19.2 In-Reply-To: <20181129135921.231283053@linuxfoundation.org> References: <20181129135921.231283053@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.19-stable review patch. If anyone has any objections, please let me know. ------------------ From: Dennis Wassenberg commit 22454b79e6de05fa61a2a72d00d2eed798abbb75 upstream. This will clear the USB_PORT_FEAT_C_CONNECTION bit in case of a hub port reset only if a device is was attached to the hub port before resetting the hub port. Using a Lenovo T480s attached to the ultra dock it was not possible to detect some usb-c devices at the dock usb-c ports because the hub_port_reset code will clear the USB_PORT_FEAT_C_CONNECTION bit after the actual hub port reset. Using this device combo the USB_PORT_FEAT_C_CONNECTION bit was set between the actual hub port reset and the clear of the USB_PORT_FEAT_C_CONNECTION bit. This ends up with clearing the USB_PORT_FEAT_C_CONNECTION bit after the new device was attached such that it was not detected. This patch will not clear the USB_PORT_FEAT_C_CONNECTION bit if there is currently no device attached to the port before the hub port reset. This will avoid clearing the connection bit for new attached devices. Signed-off-by: Dennis Wassenberg Acked-by: Mathias Nyman Cc: stable Signed-off-by: Greg Kroah-Hartman --- drivers/usb/core/hub.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) --- a/drivers/usb/core/hub.c +++ b/drivers/usb/core/hub.c @@ -2847,7 +2847,9 @@ static int hub_port_reset(struct usb_hub USB_PORT_FEAT_C_BH_PORT_RESET); usb_clear_port_feature(hub->hdev, port1, USB_PORT_FEAT_C_PORT_LINK_STATE); - usb_clear_port_feature(hub->hdev, port1, + + if (udev) + usb_clear_port_feature(hub->hdev, port1, USB_PORT_FEAT_C_CONNECTION); /*