public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Carsten Behling <carsten.behling@ridgerun.com>
Cc: <linux-usb@vger.kernel.org>, <balbi@ti.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: usb: musb: Scheduling of interrupt endpoints
Date: Tue, 23 Dec 2014 17:50:45 -0600	[thread overview]
Message-ID: <20141223235045.GC32702@saruman> (raw)
In-Reply-To: <5499C4E2.8090407@ridgerun.com>

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

Hi,

A: No.
Q: Should I include quotations after my reply?

On Tue, Dec 23, 2014 at 01:39:14PM -0600, Carsten Behling wrote:
> The following comment can be found in 'musb_schedule()':
> 
> '* REVISIT what we really want here is a regular schedule tree
>  * like e.g. OHCI uses.'
> 
> So I assume the best practice would be to make an implementation based
> on the code in in ohci-q.c. And it would be waste of time to port the
> old interrupt endpoint scheduling feature of TI.
> 
> Am I right?

Frankly, OHCI is a better example than TI's MUSB from 200 years ago,
that's correct :-)

cheers

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2014-12-23 23:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54947E99.4010908@ridgerun.com>
2014-12-23 14:59 ` usb: musb: Scheduling of interrupt endpoints Carsten Behling
2014-12-23 18:27   ` Felipe Balbi
2014-12-23 20:16     ` Carsten Behling
2014-12-23 23:48       ` Felipe Balbi
2014-12-23 19:39   ` Carsten Behling
2014-12-23 23:50     ` Felipe Balbi [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=20141223235045.GC32702@saruman \
    --to=balbi@ti.com \
    --cc=carsten.behling@ridgerun.com \
    --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