linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pengbo Mu <pengbo.mu@nxp.com>
To: Felipe Balbi <balbi@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	ran.wang_1@nxp.com, pengbo.mu@nxp.com
Subject: [PATCH] usb: dwc3: call set incr burst type func()
Date: Mon, 23 Jul 2018 14:40:57 +0800	[thread overview]
Message-ID: <1532328057-41777-1-git-send-email-pengbo.mu@nxp.com> (raw)

Calling dwc3_set_incr_burst_type() in dwc3_core_init().
This function enabled the undefined length INCR burst type and
set INCRx. Different platform may has the different burst size
type. In order to get best performance, we need to tune the burst
size to one special value, instead of the default value.

Signed-off-by: Pengbo Mu <pengbo.mu@nxp.com>
---
Changes in v1:
 - add the calling of dwc3_set_incr_burst_type.
---
 drivers/usb/dwc3/core.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index 29df9e8..21e4931 100644
--- a/drivers/usb/dwc3/core.c
+++ b/drivers/usb/dwc3/core.c
@@ -932,6 +932,8 @@ static int dwc3_core_init(struct dwc3 *dwc)
 	/* Adjust Frame Length */
 	dwc3_frame_length_adjustment(dwc);
 
+	dwc3_set_incr_burst_type(dwc);
+
 	usb_phy_set_suspend(dwc->usb2_phy, 0);
 	usb_phy_set_suspend(dwc->usb3_phy, 0);
 	ret = phy_power_on(dwc->usb2_generic_phy);
-- 
2.7.4


             reply	other threads:[~2018-07-23  6:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23  6:40 Pengbo Mu [this message]
2018-07-23  7:00 ` [PATCH] usb: dwc3: call set incr burst type func() Greg Kroah-Hartman
2018-07-23  7:48   ` Pengbo Mu
  -- strict thread matches above, loose matches on Subject: below --
2018-07-23  3:34 Pengbo Mu
2018-07-23  5:16 ` Greg Kroah-Hartman
2018-07-23  6:37   ` Pengbo Mu
2018-07-23  6:59     ` Greg Kroah-Hartman
2018-07-23  7:05 ` kbuild test robot
2018-07-23  9:29   ` Pengbo Mu
2018-07-23 10:03     ` Felipe Balbi
2018-07-23 10:35       ` Pengbo Mu
2018-07-23  7:10 ` kbuild test robot

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=1532328057-41777-1-git-send-email-pengbo.mu@nxp.com \
    --to=pengbo.mu@nxp.com \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ran.wang_1@nxp.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 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).