From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Chen, Alvin" <alvin.chen@intel.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Boon Leong Ong <boon.leong.ong@intel.com>
Subject: Re: [PATCH v5] USB: ehci-pci: USB host controller support for Intel Quark X1000
Date: Wed, 9 Jul 2014 16:07:49 -0700 [thread overview]
Message-ID: <20140709230749.GA22234@kroah.com> (raw)
In-Reply-To: <1404291498-28841-1-git-send-email-alvin.chen@intel.com>
On Wed, Jul 02, 2014 at 01:58:18AM -0700, Chen, Alvin wrote:
> From: Bryan O'Donoghue <bryan.odonoghue@intel.com>
>
> The EHCI packet buffer in/out threshold is programmable for Intel Quark X1000
> USB host controller, and the default value is 0x20 dwords. The in/out threshold
> can be programmed to 0x80 dwords (512 Bytes) to maximize the perfomrance,
> but only when isochronous/interrupt transactions are not initiated by the USB
> host controller. This patch is to reconfigure the packet buffer in/out
> threshold as maximal as possible to maximize the performance, and 0x7F dwords
> (508 Bytes) should be used because the USB host controller initiates
> isochronous/interrupt transactions.
>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@intel.com>
> Signed-off-by: Alvin (Weike) Chen <alvin.chen@intel.com>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
> Reviewed-by: Jingoo Han <jg1.han@samsung.com>
> ---
> Changlog v5:
> * Correct the wrong comment style.
>
> drivers/usb/host/ehci-pci.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
This should go to stable kernel releases as well, right?
thanks,
greg k-h
prev parent reply other threads:[~2014-07-09 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 8:58 [PATCH v5] USB: ehci-pci: USB host controller support for Intel Quark X1000 Chen, Alvin
2014-07-09 23:07 ` Greg Kroah-Hartman [this message]
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=20140709230749.GA22234@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alvin.chen@intel.com \
--cc=boon.leong.ong@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox