public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steve Calfee <stevecalfee@gmail.com>
Cc: Greg KH <gregkh@suse.de>, Michal Nazarewicz <mina86@mina86.com>,
	Klaus Schwarzkopf <schwarzkopf@sensortherm.de>,
	balbi@ti.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: add new usb gadget for ACM and mass storage
Date: Fri, 16 Sep 2011 20:55:07 +0200	[thread overview]
Message-ID: <4E739B8B.9060209@linutronix.de> (raw)
In-Reply-To: <CAJJ6jxsC3vUS1dPSYDXCcjrdYB=ybHWaC9=RhHDWQgM6WgcGmw@mail.gmail.com>

On 09/16/2011 08:22 PM, Steve Calfee wrote:
> Hi,
Hi Steve,

> To literally make a gadget that can emulate a hub (where it could
> present port 1 as function x, port 2 as function y etc) would require
> special hardware. The (bus speed) translations and (ack/nak) timings
> are speced very tightly for hubs (see chapter 11 of the spec). Each
> function would have its own usb bus address - otherwise one gadget
> could not nak while another transfered data. Each bus address would
> have to meet the spec in responding to all signaling.

That is something I haven't figured out. So the plan was to expose each
gadget as an individual port with its own descriptors. The device
number is indeed a problem that can be hardly solved. The Host sets the
address of the device it talks to and the hub routes it properly. This
is someting we can't emulate.
Hmm. So it boils down to an efficient way of providing multiple
interface descriptors without adding a lot of code each time?

> Regards, Steve
Sebastian

  reply	other threads:[~2011-09-16 18:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 18:24 [PATCH] usb: add new usb gadget for ACM and mass storage Klaus Schwarzkopf
2011-09-08 19:11 ` Greg KH
2011-09-09  8:37   ` Klaus Schwarzkopf
2011-09-09 10:30     ` Michal Nazarewicz
2011-09-09 18:45     ` Greg KH
2011-09-09 10:20   ` Michal Nazarewicz
2011-09-09 18:43     ` Greg KH
2011-09-16 17:18       ` Sebastian Andrzej Siewior
2011-09-16 17:25         ` Greg KH
2011-09-16 17:30         ` Michal Nazarewicz
2011-09-16 18:22         ` Steve Calfee
2011-09-16 18:55           ` Sebastian Andrzej Siewior [this message]
2011-09-16 21:22         ` Alan Stern
2011-10-06 12:08 ` Felipe Balbi
2011-10-07  8:23   ` Klaus Schwarzkopf
2011-10-07  8:38     ` Felipe Balbi
2011-10-07 10:07       ` Klaus Schwarzkopf
2011-10-07 10:14         ` Felipe Balbi
2011-10-07 11:13           ` Sergei Shtylyov
2011-10-07 12:55             ` Felipe Balbi
2011-10-07 11:11     ` Sergei Shtylyov
2011-10-07  8:16 ` [PATCH v2] " Klaus Schwarzkopf
2011-10-07  8:39   ` Felipe Balbi
2011-10-08  7:44 ` [PATCH v3] " Klaus Schwarzkopf
2011-10-10  5:50   ` Felipe Balbi
2011-10-10  8:33     ` Klaus Schwarzkopf
2011-10-10  8:49       ` Felipe Balbi
2011-10-10 10:30         ` Klaus Schwarzkopf
2011-10-10 15:14       ` Alan Stern
2011-10-10 16:00       ` Michal Nazarewicz
2011-10-10  8:32 ` [PATCH v4] " Klaus Schwarzkopf
2011-10-13 17:43   ` Felipe Balbi

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=4E739B8B.9060209@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=balbi@ti.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mina86@mina86.com \
    --cc=schwarzkopf@sensortherm.de \
    --cc=stevecalfee@gmail.com \
    /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