From: Sergei Shtylyov <sshtylyov@mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 2/2] USB-CDC: called handle_interrupts inside usb_eth_send
Date: Sat, 14 Aug 2010 16:26:27 +0400 [thread overview]
Message-ID: <4C668B73.80909@mvista.com> (raw)
In-Reply-To: <1281773969-16492-1-git-send-email-sbabic@denx.de>
Stefano Babic wrote:
> The patch removes an endless loop in the usb_eth_send
> if the tx_complete is not called before going
> in the loop. The driver interrupt routine is called
> allowing the driver to check if the TX is completed.
> Signed-off-by: Stefano Babic <sbabic@denx.de>
> ---
[...]
> diff --git a/drivers/usb/gadget/ether.c b/drivers/usb/gadget/ether.c
> index 0b4ed18..f082c03 100644
> --- a/drivers/usb/gadget/ether.c
> +++ b/drivers/usb/gadget/ether.c
> @@ -1808,6 +1808,8 @@ static int usb_eth_send(struct eth_device* netdev, volatile void* packet, int le
> struct usb_request *req = NULL;
>
> struct eth_dev *dev = &l_ethdev;
> + unsigned long ts;
> + unsigned long timeout = USB_CONNECT_TIMEOUT;
Please keep an empty line after the declaration block.
> @@ -1833,13 +1835,19 @@ static int usb_eth_send(struct eth_device* netdev, volatile void* packet, int le
> #endif
> dev->tx_qlen=1;
>
> + ts = get_timer(0);
> + packet_sent=0;
Please keep the style consistent and add spaces before/after =.
> retval = usb_ep_queue (dev->in_ep, req, GFP_ATOMIC);
>
> if (!retval)
> - dprintf("%s: packet queued\n",__func__);
> + debug("%s: packet queued\n",__func__);
> while(!packet_sent)
> {
> - packet_sent=0;
> + if (get_timer(ts) > timeout) {
> + printf ("timeout sending packets to usb ethernet\n");
Please be consistent and remove space before paren. U-Boot nwo seems to
follow the Linux coding style...
WBR, Sergei
next prev parent reply other threads:[~2010-08-14 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 8:19 [U-Boot] [PATCH V2 2/2] USB-CDC: called handle_interrupts inside usb_eth_send Stefano Babic
2010-08-14 12:26 ` Sergei Shtylyov [this message]
2010-08-14 15:48 ` Remy Bohmer
2010-08-15 12:17 ` Stefano Babic
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=4C668B73.80909@mvista.com \
--to=sshtylyov@mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.