public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Bryan Wu" <cooloney.lkml@gmail.com>
Cc: "Robin Getz" <rgetz@blackfin.uclinux.org>,
	linux-usb-devel@lists.sourceforge.net, gregkh@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] : Allow embedded developers USB options normally reserved for OTG
Date: Wed, 2 Jan 2008 23:36:09 -0800	[thread overview]
Message-ID: <200801022336.10355.david-b@pacbell.net> (raw)
In-Reply-To: <386072610801022040ja4919bapa8a0712c1246c3f3@mail.gmail.com>

On Wednesday 02 January 2008, Bryan Wu wrote:
> B.T.W, 2 questions about the MUSB driver:
> 1. What's the plan for mainline merge of the whole MUSB driver? maybe
> I can cleanup current Blackfin ports to you guys.

It might as well merge in 2.6.25-early.  It'll be easier to integrate
patches that way.  Including your Blackfin port.  When I asked before,
nobody hugely objected to "one big patch".


> 2. Do you remember the PING issue I reported in OMAP list? How do you
> think of that?

Yes, something needs to be done.  EHCI might benefit from the same
kind of patch, to cope with ill-behaved usb thumb drives.


> > I have an idea: the USB_NAKLIMIT0 should be set to some value, when we
> > got NAK timeout interrupt, we can disable PING. When enumerating normal
> > USB stick, there is no NAK timeout, because PING is efficient for
> > handshaking. While problem USB stick will generate NAK timeout
> > interrupt, we disable PING for this kind of USB device enumeration.
 
That sounds much better than your original patch, which disabled it
always.  It might even be worth allocating a flag somewhere in the
usb_device structure to record when ep0 pings seem to misbehave.

- Dave



  reply	other threads:[~2008-01-03  7:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 14:48 [PATCH] : Allow embedded developers USB options normally reserved for OTG Robin Getz
2008-01-02 18:47 ` [linux-usb-devel] " David Brownell
2008-01-02 18:57   ` Felipe Balbi
2008-01-02 19:14     ` David Brownell
2008-01-02 18:58   ` Mike Frysinger
2008-01-02 19:16     ` David Brownell
2008-01-02 19:46     ` Alan Stern
2008-01-02 20:25       ` David Brownell
2008-01-02 20:58         ` Alan Stern
2008-01-03  3:50           ` David Brownell
2008-01-03  3:52           ` Bryan Wu
2008-01-03 17:01           ` Richard D
2008-01-03  3:03   ` Robin Getz
2008-01-03  3:43     ` David Brownell
2008-01-03  4:40       ` Bryan Wu
2008-01-03  7:36         ` David Brownell [this message]
2008-01-03  8:05           ` Bryan Wu
2008-01-03 17:04             ` Richard D
2008-01-04  1:20               ` Robin Getz
2008-01-03  7:58       ` Robin Getz
2008-01-03  3:47   ` Bryan Wu

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=200801022336.10355.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=cooloney.lkml@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rgetz@blackfin.uclinux.org \
    /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