public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sevak Arakelyan <SEVAK.ARAKELYAN@synopsys.com>
To: John Youn <John.Youn@synopsys.com>,
	Felipe Balbi <balbi@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Sevak Arakelyan <SEVAK.ARAKELYAN@synopsys.com>
Subject: [PATCH 0/4] usb: dwc2: gadget: Fix dynamic FIFO initialization flow
Date: Wed, 26 Apr 2017 23:22:46 +0400	[thread overview]
Message-ID: <cover.1493234662.git.sevaka@synopsys.com> (raw)

This series fixes FIFO initialization issue of getting wrong insufficent FIFO memory warning.
Fixes duplicate FIFO initialization issue, replaces FIFO flushing code with function calls.
Separates initialization of periodic and non-periodic FIFOs.

Tested on HAPS platform with DWC_hsotg IP version 3.30a.

Sevak Arakelyan (4):
  usb: dwc2: gadget: Fix in TX FIFO initialization flow.
  usb: dwc2: gadget: Remove duplicated FIFO initialization.
  usb: dwc2: gadget: Replace code with function calls.
  usb: dwc2: gadget: Separate non-periodic and periodic FIFO inits

 drivers/usb/dwc2/gadget.c | 96 +++++++++++++++++++----------------------------
 1 file changed, 38 insertions(+), 58 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-04-26 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 19:22 Sevak Arakelyan [this message]
2017-04-26 19:22 ` [PATCH 1/4] usb: dwc2: gadget: Fix in TX FIFO initialization flow Sevak Arakelyan
2017-04-26 19:22 ` [PATCH 2/4] usb: dwc2: gadget: Remove duplicated FIFO initialization Sevak Arakelyan
2017-04-26 19:23 ` [PATCH 3/4] usb: dwc2: gadget: Replace code with function calls Sevak Arakelyan
2017-04-26 19:23 ` [PATCH 4/4] usb: dwc2: gadget: Separate non-periodic and periodic FIFO inits Sevak Arakelyan

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=cover.1493234662.git.sevaka@synopsys.com \
    --to=sevak.arakelyan@synopsys.com \
    --cc=John.Youn@synopsys.com \
    --cc=balbi@kernel.org \
    --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