From: "Kyungmin Park" <kmpark@infradead.org>
To: "David Brownell" <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com,
linux-kernel@vger.kernel.org, kyungmin.park@samsung.com,
tony@atomide.com
Subject: Re: USB device DMA support on OMAP2
Date: Mon, 5 Nov 2007 15:31:43 +0900 [thread overview]
Message-ID: <9c9fda240711042231s1f698683o20eb5332879d3ec5@mail.gmail.com> (raw)
In-Reply-To: <20071105062408.46E6423CA67@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
On 11/5/07, David Brownell <david-b@pacbell.net> wrote:
> > The current omap udc dosen't support the DMA mode
>
> It most certainly does!! I think you it has DMA issues on OMAP2.
>
Ah, Yes, OMAP1 supports the DMA mode. It means the OMAP2 DMA support.
>
> > and it has some problem at setup time on OMAP2 with previous patch file.
> > I found that the code assumes bulk out required the big data transfer.
> > But MODE SELECT(6) sent the only 24 bytes. it makes a problem.
> > So I implement the small packets handling for it.
> >
> > It is tested with both linux and windows.
> >
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
>
> I'll have a look at it, thanks.
>
> Is this aginst the linux-omap tree, or current kernel.org code?
> (There _shouldn't_ be any differences, but I've not checked in
> some time now and such issues do creep in from time to time.)
>
There's some difference related with double buffering.
It's against the latest kernel code. I checked it.
Thank you,
Kyungmin Park
prev parent reply other threads:[~2007-11-05 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 5:38 Kyungmin Park
2007-11-05 6:24 ` David Brownell
2007-11-05 6:31 ` Kyungmin Park [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=9c9fda240711042231s1f698683o20eb5332879d3ec5@mail.gmail.com \
--to=kmpark@infradead.org \
--cc=david-b@pacbell.net \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®