All of lore.kernel.org
 help / color / mirror / Atom feed
From: tlinder@codeaurora.org
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "Brokhman Tatyana" <tlinder@codeaurora.org>,
	linux-usb@vger.kernel.org,
	"David Brownell" <dbrownell@users.sourceforge.net>,
	"Greg Kroah-Hartman" <gregkh@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 2/2] usb: Adding SuperSpeed support to dummy_hcd
Date: Tue, 12 Oct 2010 11:07:04 -0700 (PDT)	[thread overview]
Message-ID: <50cefd84a7623992aaa547f1476a67d4.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1010120953070.1705-100000@iolanthe.rowland.org>

> On Tue, 12 Oct 2010, Brokhman Tatyana wrote:

Hi Alan

I see your point. I'll update this in the next patch.

Thanks
Tanya

>> Hi Alan
>>
>> Thanks you for your comments. Please see my reply inline.
>
>> > In addition, I suspect the dummy_hcd driver structure shouldn't
>> contain
>> > an address_device entry.  It should be present only in dummy_ss_hcd.
>>
>> I'm not sure I follow...
>> According to the code and comments in hub.c address_device cb is used if
>> the host controller wishes to choose the device address itself instead
>> of
>> the address chosen by the core.
>
> Correct.
>
>>  It seems to me that there is nothing
>> preventing the dummy_hcd from supplying such cb as well. Is there?
>> Having both HS and SS dummy_hcd determine the device address seems more
>> convenient for testing proposes.
>
> For testing purposes, it is best to imitate the behavior of a real
> device as closely as possible.  USB-2.0 host controllers do not assign
> their own addresses to devices; they use the addresses provided by
> usbcore.  I think this is also true for the low/full/high-speed
> components of a USB-3.0 controller.
>
> Alan Stern
>
>



  reply	other threads:[~2010-10-12 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-10 14:29 [RFC/PATCH 2/2] usb: Adding SuperSpeed support to dummy_hcd Tatyana Brokhman
2010-10-10 20:58 ` Alan Stern
2010-10-12  7:21   ` Brokhman Tatyana
2010-10-12 13:55     ` Alan Stern
2010-10-12 18:07       ` tlinder [this message]
2010-10-20 23:44       ` Sarah Sharp
2010-10-21 14:02         ` Alan Stern

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=50cefd84a7623992aaa547f1476a67d4.squirrel@www.codeaurora.org \
    --to=tlinder@codeaurora.org \
    --cc=dbrownell@users.sourceforge.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.