On Wed, Sep 23, 2015 at 12:39 PM, Felipe Tonello wrote:
> Hi Peter,
>
> On Wed, Sep 23, 2015 at 4:09 AM, Peter Chen wrote:
>> On Tue, Sep 22, 2015 at 07:51:34PM +0100, Felipe Tonello wrote:
>>> Hi all,
>>>
>>> On Tue, Sep 22, 2015 at 10:13 AM,
Hi Peter,
On Wed, Sep 23, 2015 at 4:09 AM, Peter Chen wrote:
> On Tue, Sep 22, 2015 at 07:51:34PM +0100, Felipe Tonello wrote:
>> Hi all,
>>
>> On Tue, Sep 22, 2015 at 10:13 AM, Felipe Tonello
>> wrote:
>> > Hi Peter,
>> >
>> > On Tue, Sep 22,
Hi all,
On Tue, Sep 22, 2015 at 10:13 AM, Felipe Tonello wrote:
> Hi Peter,
>
> On Tue, Sep 22, 2015 at 8:03 AM, Peter Chen wrote:
>> On Tue, Sep 22, 2015 at 09:07:23AM +0100, Felipe Tonello wrote:
>>> On Tue, Sep 22, 2015 at 12:41 AM, Peter
On Tue, Sep 22, 2015 at 07:51:34PM +0100, Felipe Tonello wrote:
> Hi all,
>
> On Tue, Sep 22, 2015 at 10:13 AM, Felipe Tonello
> wrote:
> > Hi Peter,
> >
> > On Tue, Sep 22, 2015 at 8:03 AM, Peter Chen
> > wrote:
> >> On Tue, Sep 22, 2015 at
Hi Peter,
On Tue, Sep 22, 2015 at 8:03 AM, Peter Chen wrote:
> On Tue, Sep 22, 2015 at 09:07:23AM +0100, Felipe Tonello wrote:
>> On Tue, Sep 22, 2015 at 12:41 AM, Peter Chen
>> wrote:
>> > On Mon, Sep 21, 2015 at 03:25:28PM +0100, Felipe
On Tue, Sep 22, 2015 at 12:41 AM, Peter Chen wrote:
> On Mon, Sep 21, 2015 at 03:25:28PM +0100, Felipe Tonello wrote:
>> Hi all,
>>
>> I actually found the problem but can't really understand. The ci_irq()
>> handler (from core.c) is not been called after a ep_queue()
On Tue, Sep 22, 2015 at 09:07:23AM +0100, Felipe Tonello wrote:
> On Tue, Sep 22, 2015 at 12:41 AM, Peter Chen wrote:
> > On Mon, Sep 21, 2015 at 03:25:28PM +0100, Felipe Tonello wrote:
> >> Hi all,
> >>
> >> I actually found the problem but can't really understand. The
On Mon, Sep 21, 2015 at 03:25:28PM +0100, Felipe Tonello wrote:
> Hi all,
>
> I actually found the problem but can't really understand. The ci_irq()
> handler (from core.c) is not been called after a ep_queue() from
> f_midi_transmit().
>
> Is there any reason for that?
>
> I used mass_storage
Hi,
(it's kinda bad to drop *all* the context from the email)
On Mon, Sep 21, 2015 at 03:25:28PM +0100, Felipe Tonello wrote:
> Hi all,
>
> I actually found the problem but can't really understand. The ci_irq()
> handler (from core.c) is not been called after a ep_queue() from
>
Hi all,
I actually found the problem but can't really understand. The ci_irq()
handler (from core.c) is not been called after a ep_queue() from
f_midi_transmit().
Is there any reason for that?
I used mass_storage gadget, made file transfers and others, and the
interrupt handler was been called
On Fri, Sep 18, 2015 at 11:03:26AM +0100, Felipe Tonello wrote:
> After some debugging, here is where I am:
>
> The crash trace is like this:
>
> (f_midi.c)
> -> ALSA calls f_midi_in_trigger()
> ->tasklet_hi_schedule(>tasklet)
> -> f_midi_transmit(midi, NULL) the NULL here causes the
After some debugging, here is where I am:
The crash trace is like this:
(f_midi.c)
-> ALSA calls f_midi_in_trigger()
->tasklet_hi_schedule(>tasklet)
-> f_midi_transmit(midi, NULL) the NULL here causes the f_midi to
request a usb_request allocation, also it sets req->complete (which is
not
Balbi,
On Fri, Sep 18, 2015 at 5:02 PM, Felipe Balbi wrote:
> Hi,
>
> On Fri, Sep 18, 2015 at 04:53:09PM +0100, Felipe Tonello wrote:
>> Hi Balbi,
>>
>> On Fri, Sep 18, 2015 at 3:25 PM, Felipe Balbi wrote:
>> > On Fri, Sep 18, 2015 at 11:03:26AM +0100, Felipe Tonello
Hi,
On Fri, Sep 18, 2015 at 04:53:09PM +0100, Felipe Tonello wrote:
> Hi Balbi,
>
> On Fri, Sep 18, 2015 at 3:25 PM, Felipe Balbi wrote:
> > On Fri, Sep 18, 2015 at 11:03:26AM +0100, Felipe Tonello wrote:
> >> After some debugging, here is where I am:
> >>
> >> The crash trace is
Hi Balbi,
On Fri, Sep 18, 2015 at 3:25 PM, Felipe Balbi wrote:
> On Fri, Sep 18, 2015 at 11:03:26AM +0100, Felipe Tonello wrote:
>> After some debugging, here is where I am:
>>
>> The crash trace is like this:
>>
>> (f_midi.c)
>> -> ALSA calls f_midi_in_trigger()
>>
On Wed, Sep 16, 2015 at 06:22:27PM +0100, Felipe Tonello wrote:
> Hi Estevam,
>
> On Tue, Sep 15, 2015 at 5:09 AM, Fabio Estevam wrote:
> > On Thu, Sep 10, 2015 at 6:47 AM, Felipe Tonello
> > wrote:
> >> Hi,
> >>
> >> I have the following setup:
> >>
Hi Clemens,
On Mon, Sep 14, 2015 at 4:24 AM, Clemens Ladisch wrote:
> The "fsl_usb2_udc" driver (if that is what you're using) uses a coherent
> DMA pool for "TD management". I see no obvious problem with how it
> calls dma_pool_alloc()/dma_pool_free(). Are there any
Hi Estevam,
On Tue, Sep 15, 2015 at 5:09 AM, Fabio Estevam wrote:
> On Thu, Sep 10, 2015 at 6:47 AM, Felipe Tonello
> wrote:
>> Hi,
>>
>> I have the following setup:
>>
>> DSP (read sensors and read/send MIDI) <- UART -> SOC (imx6) <- USB
>> MIDI
On Thu, Sep 10, 2015 at 6:47 AM, Felipe Tonello wrote:
> Hi,
>
> I have the following setup:
>
> DSP (read sensors and read/send MIDI) <- UART -> SOC (imx6) <- USB
> MIDI GADGET -> HOST
>
> When the throughput from the DSP is high, thus causing the throughput
> on the USB
Felipe Tonello wrote:
> DSP (read sensors and read/send MIDI) <- UART -> SOC (imx6) <- USB
> MIDI GADGET -> HOST
>
> When the throughput from the DSP is high, thus causing the throughput
> on the USB to be high as well, I get a Kernel Panic saying to increase
> the coherent_pool. I've used some
I wrote:
> Felipe Tonello wrote:
>> DSP (read sensors and read/send MIDI) <- UART -> SOC (imx6) <- USB
>> MIDI GADGET -> HOST
>>
>> When the throughput from the DSP is high, thus causing the throughput
>> on the USB to be high as well, I get a Kernel Panic saying to increase
>> the coherent_pool.
Hi,
I have the following setup:
DSP (read sensors and read/send MIDI) <- UART -> SOC (imx6) <- USB
MIDI GADGET -> HOST
When the throughput from the DSP is high, thus causing the throughput
on the USB to be high as well, I get a Kernel Panic saying to increase
the coherent_pool. I've used some
22 matches
Mail list logo