All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <mporter@linaro.org>
To: Felipe Balbi <balbi@ti.com>
Cc: Robert Baldyga <r.baldyga@samsung.com>,
	gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, b.zolnierkie@samsung.com,
	m.szyprowski@samsung.com, andrzej.p@samsung.com,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Matt Porter <matt.porter@linaro.org>
Subject: Re: [PATCH 1/2] USB: gadget: s3c-hsotg: fix maxpacket size in s3c_hsotg_irq_enumdone
Date: Thu, 12 Dec 2013 08:47:53 -0500	[thread overview]
Message-ID: <20131212134753.GC20773@beef> (raw)
In-Reply-To: <20131206203523.GK21086@saruman.home>

On Fri, Dec 06, 2013 at 02:35:23PM -0600, Felipe Balbi wrote:
> Hi,
> 
> On Fri, Dec 06, 2013 at 01:03:44PM +0100, Robert Baldyga wrote:
> > This patch set maximum possible maxpacket value for each speed. Previous
> > values didn't allow to use maxpacket sizes greater than 64 in full speed
> > and 512 in high speed, although hardware is able to handle up to 1023 in fs
> > and 1024 in hs.
> > 
> > Signed-off-by: Robert Baldyga <r.baldyga@samsung.com>
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> 
> Matt, will this cause any problems for your efforts on Bcom ?

I tested this patch in both full and high speed mode on my Capri board
and it works fine for me in both cases.

Tested-by: Matt Porter <mporter@linaro.org>

Thanks,
Matt

  reply	other threads:[~2013-12-12 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 12:03 [PATCH 0/2] usb: s3c-hsotg: fixes for maxpacket and TX FIFO handling Robert Baldyga
2013-12-06 12:03 ` [PATCH 1/2] USB: gadget: s3c-hsotg: fix maxpacket size in s3c_hsotg_irq_enumdone Robert Baldyga
2013-12-06 20:35   ` Felipe Balbi
2013-12-12 13:47     ` Matt Porter [this message]
2013-12-06 12:03 ` [PATCH 2/2] USB: gadget: s3c-hsotg: add flush TX FIFO when kill all requests Robert Baldyga

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=20131212134753.GC20773@beef \
    --to=mporter@linaro.org \
    --cc=andrzej.p@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=matt.porter@linaro.org \
    --cc=r.baldyga@samsung.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 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.