Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965366AbeAJJ1v (ORCPT + 1 other); Wed, 10 Jan 2018 04:27:51 -0500 Received: from mail-lf0-f48.google.com ([209.85.215.48]:39840 "EHLO mail-lf0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965256AbeAJJ1p (ORCPT ); Wed, 10 Jan 2018 04:27:45 -0500 X-Google-Smtp-Source: ACJfBotGNjPqeF4FE8Sp0InkPdO5runiWs935UCNeummcrYuYXxgE2QSBmKh/KPSd97HdiV7To7ohg== Date: Wed, 10 Jan 2018 10:27:40 +0100 From: Johan Hovold To: "Ji-Ze Hong (Peter Hong)" Cc: Johan Hovold , gregkh@linuxfoundation.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, peter_hong@fintek.com.tw, "Ji-Ze Hong (Peter Hong)" Subject: Re: [PATCH V2 1/5] usb: serial: f81534: add high baud rate support Message-ID: <20180110092740.GX11344@localhost> References: <1515032961-29131-1-git-send-email-hpeter+linux_kernel@gmail.com> <20180109110841.GN11344@localhost> <18d4171a-1e1a-5476-dc9d-02a522cbf077@gmail.com> <20180110084914.GV11344@localhost> <3b594392-1b6d-f019-1e5f-3e3e3f87f7e8@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3b594392-1b6d-f019-1e5f-3e3e3f87f7e8@gmail.com> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Wed, Jan 10, 2018 at 05:16:01PM +0800, Ji-Ze Hong (Peter Hong) wrote: > Hi Johan, > > Johan Hovold 於 2018/1/10 下午 04:49 寫道: > >> Normally, the communication with F81534 ep0 will take less than 1 sec > >> (even only some milliseconds), but It maybe take much long time with > >> huge loading with UART functional. > >> > >> We had tested it on BurnInTest, 4 ports with 921600bps + MSR status > >> check to perform huge loading test. The worst case to read MSR register > >> via ep0 will take 15~18 seconds. So We'll still remain the max waiting > >> time for access ep0 with 2x10=20s in high baud rate mode. > > > > Wow, that's unfortunate. But note that your patch only doubles the > > timeout to 2000 ms, that is, two seconds and not twenty: > > > > -#define F81534_USB_TIMEOUT 1000 > > +#define F81534_USB_TIMEOUT 2000 > > > > If you really intended to increase this to twenty seconds, then please > > do so in a separate (preparatory) patch where you describe why that is > > needed (e.g. what you wrote above). > > In f81534_set_register()/f81534_get_register(), We'll use a while loop > with 10 times to get/set register and the timeout is 1000ms. So the > total minimum retry timeout is 1000x10=10s. > > But when introducing the high baud rate support, 10s is not enough for > heavily loading. We had tested the minimum retry is 16~18s, so we > enlarge the F81534_USB_TIMEOUT from 1000 to 2000 and the total minimum > retry timeout is 20s. > > Should I separate it as 2 patches? This issue is due to introducing > high baud patch. Ah, sorry. Forgot about the retries. Increasing it as part of this patch is fine. Johan