linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: balbi@ti.com
Cc: gregkh@suse.de, linux-arm-msm@vger.kernel.org,
	ablay@codeaurora.org,
	"'open list:USB GADGET/PERIPH...'" <linux-usb@vger.kernel.org>,
	'open list' <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/5 v8] usb: Adding SuperSpeed support to dummy_hcd
Date: Sun, 27 Mar 2011 14:19:25 +0200	[thread overview]
Message-ID: <000201cbec79$3a7dc4f0$af794ed0$@org> (raw)
In-Reply-To: <20110325134730.GO2609@legolas.emea.dhcp.ti.com>

Hi

> >
> >  MODULE_DESCRIPTION (DRIVER_DESC);
> >  MODULE_AUTHOR ("David Brownell");
> > @@ -220,6 +223,7 @@ static inline struct dummy *gadget_dev_to_dummy
> (struct device *dev)
> >  }
> >
> >  static struct dummy			*the_controller;
> > +static struct dummy			*the_ss_controller;
> 
> the only thing I don't like, is why you splitted the ss controller to a
> separate controller. Why don't you use the same ? From SW perspective,
> we can treat SS and HS/FS/LS controllers as one unit.
> 

Actually I'm not sure about that... Because SS controller handles things a
bit differently than HS/FS/LS. For example look at set_ss_link_state(), the
port status is reported differently than for HS/FS/LS devices.
It could be done, I mean spare the the_ss_controller variable and use
the_controller, and we did that at first, but later on we decided to go back
to this implementation since the code got too complex. Since dummy_hcd.c is
used for debugging purposes we decided that simplicity is the better
approach here.


Best regards,
Tanya Brokhman
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

  reply	other threads:[~2011-03-27 12:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  8:02 [PATCH 1/5 v8] usb: Adding SuperSpeed support to dummy_hcd Tatyana Brokhman
     [not found] ` <1300867372-20811-1-git-send-email-tlinder-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-03-25 13:47   ` Felipe Balbi
2011-03-27 12:19     ` Tanya Brokhman [this message]
2011-03-28  8:41       ` Felipe Balbi
     [not found]         ` <20110328084157.GH2251-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-04-14 11:46           ` [PATCH] usb: merge the two dummy_hcds into one Sebastian Andrzej Siewior
2011-04-14 15:45             ` Alan Stern
2011-04-14 17:45               ` Sebastian Andrzej Siewior
2011-04-26  6:18               ` Tanya Brokhman
2011-04-26 10:24                 ` Sebastian Andrzej Siewior
2011-04-28  5:18                   ` Tanya Brokhman

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='000201cbec79$3a7dc4f0$af794ed0$@org' \
    --to=tlinder@codeaurora.org \
    --cc=ablay@codeaurora.org \
    --cc=balbi@ti.com \
    --cc=gregkh@suse.de \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).