From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0701.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe42::701]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id AB5FC81DCA for ; Sun, 13 Nov 2016 19:32:47 -0800 (PST) Received: from AT5PR84MB0276.NAMPRD84.PROD.OUTLOOK.COM (10.162.138.22) by AT5PR84MB0273.NAMPRD84.PROD.OUTLOOK.COM (10.162.138.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.10; Mon, 14 Nov 2016 03:32:51 +0000 Received: from AT5PR84MB0276.NAMPRD84.PROD.OUTLOOK.COM ([10.162.138.22]) by AT5PR84MB0276.NAMPRD84.PROD.OUTLOOK.COM ([10.162.138.22]) with mapi id 15.01.0721.015; Mon, 14 Nov 2016 03:32:51 +0000 From: "Anbazhagan, Baraneedharan" To: "Tian, Feng" , "edk2-devel@lists.01.org" Thread-Topic: USB hub port reset Thread-Index: AdI9P9a4p+GKnaQeTV6wi4G+bYD8YgA2K+ggAABY8XA= Date: Mon, 14 Nov 2016 03:32:51 +0000 Message-ID: References: <7F1BAD85ADEA444D97065A60D2E97EE566E4F108@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <7F1BAD85ADEA444D97065A60D2E97EE566E4F108@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=anbazhagan@hp.com; x-originating-ip: [66.135.176.178] x-microsoft-exchange-diagnostics: 1; AT5PR84MB0273; 7:qbBYkQcp0GTuwV3WwlN22Xp3MK6Gu9bRMKUh7iaaJuXbJC81q9KixRXyJoow9UlOmwyywuLsXvI9uQIKpjpwFpy8rilftSoJ+FpOgFRlR8vB6yw4pPXSCWoM09G8hCG1wWU7iLHfNg5ZdBE2YxHIJFKa2HaRUry3gQ0ItFqVhP+mL9+KAUVLEnxgxIFDlRkvXqKDyErO5oU57MIaLY5N919nuGlos/nX5wG+oVZ8W1eDj3vZRb+EtE/HGu8b9cKDw0MoLuzk7XcKyenTyqZKa03pfA/EnyQ/u3xFs53XUcW2zRGQMI3xucUNqIwlCOY+dHKzCPNSRRc1vXFsy1EbFALLY5QWo5+1fZQKLPt1jcQ= x-ms-office365-filtering-correlation-id: 824f49d4-3f1a-42d8-3c0b-08d40c3ee9ac x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AT5PR84MB0273; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(166708455590820)(162533806227266)(228905959029699)(73583498263828); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:AT5PR84MB0273; BCL:0; PCL:0; RULEID:; SRVR:AT5PR84MB0273; x-forefront-prvs: 0126A32F74 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(336003)(199003)(377454003)(6602003)(189002)(2501003)(101416001)(106356001)(3660700001)(3280700002)(99286002)(86362001)(105586002)(8676002)(76176999)(54356999)(50986999)(107886002)(189998001)(5001770100001)(74316002)(97736004)(81166006)(81156014)(3480700004)(77096005)(8936002)(229853002)(66066001)(122556002)(2900100001)(68736007)(9686002)(33656002)(2906002)(87936001)(5660300001)(586003)(102836003)(6116002)(3846002)(92566002)(7736002)(2950100002)(305945005)(7846002)(7696004); DIR:OUT; SFP:1102; SCL:1; SRVR:AT5PR84MB0273; H:AT5PR84MB0276.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Nov 2016 03:32:51.1454 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ca7981a2-785a-463d-b82a-3db87dfc3ce6 X-MS-Exchange-Transport-CrossTenantHeadersStamped: AT5PR84MB0273 Subject: Re: USB hub port reset X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 03:32:47 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I didn't mean to have extra delays. Am asking whether EDKII have to be upda= ted for 10ms reset recovery time regardless of port status to align with sp= ec? >From: Tian, Feng [mailto:feng.tian@intel.com]=20 >Sent: Sunday, November 13, 2016 7:46 PM >To: Anbazhagan, Baraneedharan ; edk2-devel@lists.01.org >Cc: Tian, Feng >Subject: RE: USB hub port reset > >Hi, Baranee > >Linux wait 10 + 40 ms (TRSTRCY =3D 10 ms, plus extra 40 ms). Do you mean E= DKII should be same with linux to wait more time? > >Thanks >Feng > >From: Anbazhagan, Baraneedharan [mailto:anbazhagan@hp.com]=20 >Sent: Sunday, November 13, 2016 11:53 AM >To: mailto:edk2-devel@lists.01.org; Tian, Feng >Subject: USB hub port reset > >EDK2 have reset recovery time of 10ms for hub port based on port status re= set bit but USB spec doesn't mention that port status can be used for t6/re= set recovery time. Could you please clarify? > >USB vendor mentions EDK2 doesn't have reset recovery time on hub port rese= t and also highlighting EDK2 hub port reset differs from https://github.com= /torvalds/linux/blob/master/drivers/usb/core/hub.c#L2789 > >-Baranee