public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
To: unlisted-recipients:; (no To-header on input)
Cc: felipe Balbi <balbi@ti.com>, Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH]  usb: gadget: USB3 support to the legacy printer driver
Date: Tue, 18 Nov 2014 12:52:11 -0500	[thread overview]
Message-ID: <546B874B.8060700@linaro.org> (raw)
In-Reply-To: <20141118151753.GB8223@saruman>

On 11/18/2014 10:17 AM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Nov 18, 2014 at 09:19:36AM -0500, Jorge Ramirez-Ortiz wrote:
>> Hi Felipe/Greg
>>
>> Thanks for your comments on my previous attempt.
>> I think I addressed them here.
> no you haven't. Read Documentation/SubmittingPatches, read the mailing
> list archives and you'll see your basic mistake.

For this fundamental mistake, could you not just share with me what I am missing?
I don't see anything wrong other than maybe adding more maintainers to the DL as per the scripts since the feature itself is self explanatory.

     

> you have no clue what these mean, do you ? How about reading the USB
> specification of even http://www.beyondlogic.org/usbnutshell/usb1.shtml


Unfortunately I do.
It was easier to temporarily hack the driver code for a test - while I was at it - rather than modifying the host code.
Since you asked for them, I though you would read the logs and wonder where the funny ids where coming from.
That hack above would have given you an answer: so I kind of know what the ids are for. honestly.
anyway, will send the new logs - it took me a while to find and modify the host test code.


>
> do you want to debug that and find the culprit since you're already at
> it ?

probably: I still need to get used to this process, thanks for bearing with me on this.

I spoke to Ricardo Ribalda three months ago while I was doing this stuff.
but yes, I might work on this -after I finish with this patch!- since I have access to the hardware locally.


>
>>
>> 3) Patch:
>> ---------
>>
>>
>>
>> From 9b5ee9330c5c02cf51328c350036c1dac998b732 Mon Sep 17 00:00:00 2001
>> From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
>> Date: Thu, 25 Sep 2014 16:17:20 -0400
>> Subject: [PATCH 2/3] usb: gadget: add USB3 support to the printer driver
>>
>> Add SS descriptors to support the capabilities provided by USB3 controller
>> drivers; unit tests run using a PLX 3380 [max transfer speed measured of 1Gbps]
>>
>> This driver shall fallback to lower operating modes when the higher ones are
>> not available.
>>
>> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
>> ---
>>  drivers/usb/gadget/legacy/printer.c | 65 +++++++++++++++++++++++++++++++++----
>>  1 file changed, 59 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/usb/gadget/legacy/printer.c b/drivers/usb/gadget/legacy/printer.c
>> index 6474081..456730b 100644
>> --- a/drivers/usb/gadget/legacy/printer.c
>> +++ b/drivers/usb/gadget/legacy/printer.c
>> @@ -208,6 +208,43 @@ static struct usb_descriptor_header *hs_printer_function[] = {
>>      NULL
>>  };
>>  
>> +/*
>> + * Added endpoint descriptors for 3.0 devices
>> + */
>> +
>> +static struct usb_endpoint_descriptor ss_ep_in_desc = {
>> +    .bLength =              USB_DT_ENDPOINT_SIZE,
>> +    .bDescriptorType =      USB_DT_ENDPOINT,
>> +    .bmAttributes =         USB_ENDPOINT_XFER_BULK,
>> +    .wMaxPacketSize =       cpu_to_le16(1024),
>> +};
>> As mentioned above, using the usb338x driver from PLX instead of the net2280 from
>> kernel.org, the effective file transfer rate increases 1Gbps.
>>
> all your tabs have been converted into spaces. Perhaps try:
>
> 	$ git help send-email
>
> and figure out how to use that ?
>

crap. really sorry about this!


  reply	other threads:[~2014-11-18 17:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 23:19 [PATCH] usb: gadget: USB3 support to the legacy printer driver Jorge Ramirez-Ortiz
2014-11-18  0:30 ` Felipe Balbi
2014-11-18  0:54   ` Greg KH
2014-11-18  1:14     ` Jorge Ramirez-Ortiz
2014-11-18 14:19   ` Jorge Ramirez-Ortiz
2014-11-18 15:17     ` Felipe Balbi
2014-11-18 17:52       ` Jorge Ramirez-Ortiz [this message]
2014-11-18 18:00         ` Felipe Balbi
2014-11-18 20:41           ` Jorge Ramirez-Ortiz
2014-11-18 20:47             ` Felipe Balbi
2014-11-18 21:33               ` Jorge Ramirez-Ortiz
2014-11-19  3:14                 ` Felipe Balbi
2014-11-18 21:45               ` Paul Zimmerman
2014-11-19  3:10                 ` 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=546B874B.8060700@linaro.org \
    --to=jorge.ramirez-ortiz@linaro.org \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.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