All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Douglas Anderson <dianders@chromium.org>,
	hminas@synopsys.com, gregkh@linuxfoundation.org
Cc: Jerome Brunet <jbrunet@baylibre.com>,
	Zhangfei Gao <zhangfei.gao@linaro.org>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Bruno Herrera <bruherrera@gmail.com>,
	Douglas Anderson <dianders@chromium.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFT PATCH 0/4] usb: dwc2: Turn on uframe sched everywhere
Date: Thu, 26 Jul 2018 13:59:58 +0300	[thread overview]
Message-ID: <87o9eu1cup.fsf@linux.intel.com> (raw)
In-Reply-To: <20180706162154.196345-1-dianders@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

Douglas Anderson <dianders@chromium.org> writes:

> While looking at a dwc2 recently, I noticed that some platforms still
> have the uframe scheduler off.  As far as I know, nothing good can
> come out of having the uframe scheduler off.  Let's turn it on
> everywhere.  Assuming this all works out then some time in the future
> we can gut all the old code that handles the old non-uframe scheduler
> and make everything simpler.
>
> NOTE: I don't have access to any of the platforms that I'm changing
> here, so I'm hoping to see a Tested-by from those on the list.
>
>
> Douglas Anderson (4):
>   usb: dwc2: Turn on uframe_sched on "bcm" platforms
>   usb: dwc2: Turn on uframe_sched on "his" platforms
>   usb: dwc2: Turn on uframe_sched on "amlogic" platforms
>   usb: dwc2: Turn on uframe_sched on "stm32f4x9_fsotg" platforms

care to resend without RFT prefix and with collected acks, tested-bys, etc?

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-07-26 11:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 16:21 [RFT PATCH 0/4] usb: dwc2: Turn on uframe sched everywhere Douglas Anderson
2018-07-26 10:59 ` Felipe Balbi [this message]
2018-07-26 20:11   ` Doug Anderson
2018-07-27  6:55     ` Felipe Balbi
  -- strict thread matches above, loose matches on Subject: below --
2018-07-06 16:21 [RFT,1/4] usb: dwc2: Turn on uframe_sched on "bcm" platforms Doug Anderson
2018-07-06 16:21 ` [RFT PATCH 1/4] " Douglas Anderson
2018-07-06 16:21 [RFT,2/4] usb: dwc2: Turn on uframe_sched on "his" platforms Doug Anderson
2018-07-06 16:21 ` [RFT PATCH 2/4] " Douglas Anderson
2018-07-06 16:21 [RFT,3/4] usb: dwc2: Turn on uframe_sched on "amlogic" platforms Doug Anderson
2018-07-06 16:21 ` [RFT PATCH 3/4] " Douglas Anderson
2018-07-06 16:21 [RFT,4/4] usb: dwc2: Turn on uframe_sched on "stm32f4x9_fsotg" platforms Doug Anderson
2018-07-06 16:21 ` [RFT PATCH 4/4] " Douglas Anderson
2018-07-10 13:57 [RFT PATCH 0/4] usb: dwc2: Turn on uframe sched everywhere Stefan Wahren
2018-07-10 15:21 ` Doug Anderson
2018-07-11 11:29   ` Stefan Wahren
2018-07-10 23:34 [RFT,2/4] usb: dwc2: Turn on uframe_sched on "his" platforms John Stultz
2018-07-10 23:34 ` [RFT PATCH 2/4] " John Stultz

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=87o9eu1cup.fsf@linux.intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=bruherrera@gmail.com \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hminas@synopsys.com \
    --cc=jbrunet@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=zhangfei.gao@linaro.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 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.