public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: gadget: fastboot: improve download progress bar
Date: Thu, 18 Sep 2014 09:34:18 +0800	[thread overview]
Message-ID: <541A369A.8000901@atmel.com> (raw)
In-Reply-To: <201409171316.55811.marex@denx.de>

Hi Marek,

On 09/17/2014 07:16 PM, Marek Vasut wrote:
> On Wednesday, September 17, 2014 at 12:28:57 PM, Bo Shen wrote:
>> Hi Marek,
>>
>> On 09/17/2014 06:10 PM, Marek Vasut wrote:
>>> On Wednesday, September 17, 2014 at 09:43:56 AM, Bo Shen wrote:
>>>
>>> +CC Lukasz, this is his turf.
>>>
>>>> When download is ongoing, if the actual size of one transfer
>>>> is not the same as BTYES_PER_DOT, which will cause the dot
>>>> won't print anymore. Then it will let the user thinking it
>>>> is stuck, actually it is transfering without dot printed.
>>>>
>>>> So, improve the method to show the progress bar (print dot).
>>>>
>>>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>>>> ---
>>>>
>>>>    drivers/usb/gadget/f_fastboot.c | 7 +++++--
>>>>    1 file changed, 5 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/usb/gadget/f_fastboot.c
>>>> b/drivers/usb/gadget/f_fastboot.c index 7a1acb9..2f13bf0 100644
>>>> --- a/drivers/usb/gadget/f_fastboot.c
>>>> +++ b/drivers/usb/gadget/f_fastboot.c
>>>> @@ -51,6 +51,7 @@ static inline struct f_fastboot
>>>> *func_to_fastboot(struct usb_function *f) static struct f_fastboot
>>>> *fastboot_func;
>>>>
>>>>    static unsigned int download_size;
>>>>    static unsigned int download_bytes;
>>>>
>>>> +static unsigned int num_of_dot;
>>>>
>>>>    static struct usb_endpoint_descriptor fs_ep_in = {
>>>>
>>>>    	.bLength            = USB_DT_ENDPOINT_SIZE,
>>>>
>>>> @@ -414,9 +415,10 @@ static void rx_handler_dl_image(struct usb_ep *ep,
>>>> struct usb_request *req) req->length = ep->maxpacket;
>>>>
>>>>    	}
>>>>
>>>> -	if (download_bytes && !(download_bytes % BYTES_PER_DOT)) {
>>>> +	if (download_bytes && ((download_bytes / BYTES_PER_DOT) > num_of_dot))
>>>> { +		num_of_dot = download_bytes / BYTES_PER_DOT;
>>>>
>>>>    		putc('.');
>>>>
>>>> -		if (!(download_bytes % (74 * BYTES_PER_DOT)))
>>>> +		if (!(num_of_dot % 74))
>>>>
>>>>    			putc('\n');
>>>>    	
>>>>    	}
>>>>    	req->actual = 0;
>>>>
>>>> @@ -431,6 +433,7 @@ static void cb_download(struct usb_ep *ep, struct
>>>> usb_request *req) strsep(&cmd, ":");
>>>>
>>>>    	download_size = simple_strtoul(cmd, NULL, 16);
>>>>    	download_bytes = 0;
>>>>
>>>> +	num_of_dot = 0;
>>>
>>> Make it a 'download_total' and log the total amount of bytes transferred
>>> please, that way it can be re-used for other purposes in the future ;
>>> for example for printing how much data were already transferred ;-)
>>
>> The download_bytes record the total amount of bytes transferred.
>> And the download_bytes will print after finishing transfer.
>
> So why can this not be used to indicate the total progress ? Because the
> transfeer speed is variating too much ?

As I described in the commit message. If the transfer length is not 
exactly the same as the request length, then the old method
   "download_bytes % BYTES_PER_DOT"
won't be 0 anymore, so for the following transfer, it won't print dot 
anymore.

Best Regards,
Bo Shen

  reply	other threads:[~2014-09-18  1:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17  7:43 [U-Boot] [PATCH] usb: gadget: fastboot: improve download progress bar Bo Shen
2014-09-17 10:10 ` Marek Vasut
2014-09-17 10:28   ` Bo Shen
2014-09-17 11:16     ` Marek Vasut
2014-09-18  1:34       ` Bo Shen [this message]
2014-09-18  2:31         ` Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=541A369A.8000901@atmel.com \
    --to=voice.shen@atmel.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox