From: Carsten Behling <carsten.behling@ridgerun.com>
To: balbi@ti.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: usb: musb: Scheduling of interrupt endpoints
Date: Tue, 23 Dec 2014 14:16:57 -0600 [thread overview]
Message-ID: <5499CDB9.6050602@ridgerun.com> (raw)
In-Reply-To: <20141223182737.GF9147@saruman>
Hi Felipe,
On 12/23/2014 12:27 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Dec 23, 2014 at 08:59:39AM -0600, Carsten Behling wrote:
>> Would it help if I send a patch as a suggestion and as basis for
>> discussion?
> yes, it would also help if you didn't top-post :-)
>
So would you suggestion be to port that feature from the old
linux-2.6.32.17-psp03.01.01.39
kernel from TI or should we rather add a tree based implementation as
done for OHCI?
-Carsten
next prev parent reply other threads:[~2014-12-23 20:17 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 [this message]
2014-12-23 23:48 ` Felipe Balbi
2014-12-23 19:39 ` Carsten Behling
2014-12-23 23:50 ` Felipe Balbi
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=5499CDB9.6050602@ridgerun.com \
--to=carsten.behling@ridgerun.com \
--cc=balbi@ti.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