From: George Cherian <george.cherian@ti.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] ARM: dts: am33xx: fix DMA support for the second USB interface
Date: Tue, 29 Apr 2014 10:01:21 +0530 [thread overview]
Message-ID: <535F2B19.7020300@ti.com> (raw)
In-Reply-To: <CAGm1_kt_yQZowthaFq=imM5J6=1FkJX_1LtRV7eEiqeursbDZQ@mail.gmail.com>
On 4/28/2014 9:47 PM, Yegor Yefremov wrote:
> On Mon, Apr 28, 2014 at 4:25 PM, George Cherian <george.cherian@ti.com> wrote:
>> On 4/28/2014 2:07 PM, yegorslists@googlemail.com wrote:
>>> From: Yegor Yefremov <yegorslists@googlemail.com>
>>>
>>> This patch creates unique DMA channels for the second USB
>>> interface, otherwise the second USB interface is not usable
>>> at all.
>> MUSB_DMA_NUM_CHANNELS is 15, so if you pass any dma-names > 15 (>
>> rx15/tx15),
>> the dma_controller_create in musb_core.c fails and it falls back to PIO
>> mode.
> What's the proper fix for the DMA issue?
I could not understand what issue you are referring to.
In my setup I use both BBB and BBW (Beagle Bone Black/White)with one USB
in host (USB1)
and one USB in gadget (USB0). I dont see any issues with DMA.
Can you be more specific?
>
> Yegor
--
-George
WARNING: multiple messages have this Message-ID (diff)
From: george.cherian@ti.com (George Cherian)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: am33xx: fix DMA support for the second USB interface
Date: Tue, 29 Apr 2014 10:01:21 +0530 [thread overview]
Message-ID: <535F2B19.7020300@ti.com> (raw)
In-Reply-To: <CAGm1_kt_yQZowthaFq=imM5J6=1FkJX_1LtRV7eEiqeursbDZQ@mail.gmail.com>
On 4/28/2014 9:47 PM, Yegor Yefremov wrote:
> On Mon, Apr 28, 2014 at 4:25 PM, George Cherian <george.cherian@ti.com> wrote:
>> On 4/28/2014 2:07 PM, yegorslists at googlemail.com wrote:
>>> From: Yegor Yefremov <yegorslists@googlemail.com>
>>>
>>> This patch creates unique DMA channels for the second USB
>>> interface, otherwise the second USB interface is not usable
>>> at all.
>> MUSB_DMA_NUM_CHANNELS is 15, so if you pass any dma-names > 15 (>
>> rx15/tx15),
>> the dma_controller_create in musb_core.c fails and it falls back to PIO
>> mode.
> What's the proper fix for the DMA issue?
I could not understand what issue you are referring to.
In my setup I use both BBB and BBW (Beagle Bone Black/White)with one USB
in host (USB1)
and one USB in gadget (USB0). I dont see any issues with DMA.
Can you be more specific?
>
> Yegor
--
-George
next prev parent reply other threads:[~2014-04-29 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 8:37 [PATCH] ARM: dts: am33xx: fix DMA support for the second USB interface yegorslists
2014-04-28 8:37 ` yegorslists at googlemail.com
2014-04-28 14:25 ` George Cherian
2014-04-28 14:25 ` George Cherian
2014-04-28 16:17 ` Yegor Yefremov
2014-04-28 16:17 ` Yegor Yefremov
2014-04-29 4:31 ` George Cherian [this message]
2014-04-29 4:31 ` George Cherian
2014-04-29 6:16 ` Yegor Yefremov
2014-04-29 6:16 ` Yegor Yefremov
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=535F2B19.7020300@ti.com \
--to=george.cherian@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.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 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.