On Tue, 23 Aug 2011 17:11:06 +0200, Felipe Balbi <balbi@xxxxxx> wrote:
I'm trying to think if this is really what we want. This might mean
$current_config will be different depending if we connect it to SS, HS
or FS hubs.
On Tue, Aug 23, 2011 at 05:26:24PM +0200, Michal Nazarewicz wrote:
What do you mean by $current_config? The bConfigurationValue will be
On Tue, 23 Aug 2011 19:19:43 +0200, Felipe Balbi <balbi@xxxxxx> wrote:
the currently chosen configuration.
So yes, it potentially ma be different depending on the speed.
the same for "the same" configuration regardless of speed but different
configurations may be available for different speeds and "the same"
configuration in various speeds might have different functions.
So just for the sake of having something concrete, let's say we have:
Configuration #1 with
function A supporting FS and HS and
my question is what happens with the HS support on function A
(descriptors, endpoints, etc) when you connect it to a HS hub or to a FS
hub.
When you connect it to HS hub you get it's HS descriptors (and FS
descriptors
if you request “other speed descriptors”). When you connect it to FS hub
you
get it's FS descriptors.
function B supporting FS only.
Configuration #2 with
function B supporting FS only.
Configuration #3 with
function A supporting FS and HS and
function C supporting HS only (dunno if that makes sense).
When connected to FS hub, we will return the following:
Configuration #1: A, B
Configuration #2: B
Configuration #3: A
When connect to HS hub, we will return the following:
Configuration #1: A
See, I'm not sure this is allowed by USB spec. But I could be wrong. (I
mean having a function disappear)
I'm hardly an expert so I cannot address that concern.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michal "mina86" Nazarewicz (o o)
ooo +-----<email/xmpp: mnazarewicz@xxxxxxxxxx>-----ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
