Re: OOPS: musb_hdrc

2014-09-09 Thread Felipe Balbi
Hi, On Tue, Sep 09, 2014 at 08:17:32PM +0400, Matwey V. Kornilov wrote: > 2014-09-09 20:09 GMT+04:00 Felipe Balbi : > > On Tue, Sep 09, 2014 at 07:52:59PM +0400, Matwey V. Kornilov wrote: > >> 2014-09-09 19:11 GMT+04:00 Felipe Balbi : > >> > the proper way would be to move everything to dma_engine

Re: OOPS: musb_hdrc

2014-09-09 Thread Matwey V. Kornilov
2014-09-09 20:09 GMT+04:00 Felipe Balbi : > On Tue, Sep 09, 2014 at 07:52:59PM +0400, Matwey V. Kornilov wrote: >> 2014-09-09 19:11 GMT+04:00 Felipe Balbi : >> > the proper way would be to move everything to dma_engine. OMAP already >> > has support for DMA engine and both CPPI and Ux500 are alread

Re: OOPS: musb_hdrc

2014-09-09 Thread Felipe Balbi
On Tue, Sep 09, 2014 at 07:52:59PM +0400, Matwey V. Kornilov wrote: > 2014-09-09 19:11 GMT+04:00 Felipe Balbi : > > the proper way would be to move everything to dma_engine. OMAP already > > has support for DMA engine and both CPPI and Ux500 are already using > > that. > > If so, ux500_dma.c and m

Re: OOPS: musb_hdrc

2014-09-09 Thread Matwey V. Kornilov
2014-09-09 19:11 GMT+04:00 Felipe Balbi : > the proper way would be to move everything to dma_engine. OMAP already > has support for DMA engine and both CPPI and Ux500 are already using > that. If so, ux500_dma.c and musb_cppi41.c should be almost identically wrapping dmaengine, but they aren't.

Re: OOPS: musb_hdrc

2014-09-09 Thread Felipe Balbi
On Tue, Sep 09, 2014 at 07:00:10PM +0400, Matwey V. Kornilov wrote: > 2014-09-09 18:45 GMT+04:00 Felipe Balbi : > > On Tue, Sep 09, 2014 at 01:28:55PM +0400, Matwey V. Kornilov wrote: > >> Hi George, > >> > >> Why dma_controller_create can not be set in struct musb_platform_ops? > >> Then each modu

Re: OOPS: musb_hdrc

2014-09-09 Thread Matwey V. Kornilov
2014-09-09 18:45 GMT+04:00 Felipe Balbi : > On Tue, Sep 09, 2014 at 01:28:55PM +0400, Matwey V. Kornilov wrote: >> Hi George, >> >> Why dma_controller_create can not be set in struct musb_platform_ops? >> Then each module would be able to set dma_controller_create it wants, >> and musb_init_control

Re: OOPS: musb_hdrc

2014-09-09 Thread Felipe Balbi
On Tue, Sep 09, 2014 at 01:28:55PM +0400, Matwey V. Kornilov wrote: > Hi George, > > Why dma_controller_create can not be set in struct musb_platform_ops? > Then each module would be able to set dma_controller_create it wants, > and musb_init_controller would use musb->ops->dma_controller_create >

Re: OOPS: musb_hdrc

2014-09-09 Thread Matwey V. Kornilov
Hi George, Why dma_controller_create can not be set in struct musb_platform_ops? Then each module would be able to set dma_controller_create it wants, and musb_init_controller would use musb->ops->dma_controller_create instead of just dma_controller_create. 2014-09-09 13:15 GMT+04:00 Matwey V. K

Re: OOPS: musb_hdrc

2014-09-09 Thread Matwey V. Kornilov
Hi George, Many thanks for the hint. Am I right that we can not have multiple MUSB DMA modes within the same kernel? It is a pity. 2014-09-09 12:40 GMT+04:00 George Cherian : > Hi Matwey, > > > On 09/09/2014 01:58 PM, Matwey V. Kornilov wrote: >> >> Hi, >> Can you add a few printks around d

Re: OOPS: musb_hdrc

2014-09-09 Thread George Cherian
Hi Matwey, On 09/09/2014 01:58 PM, Matwey V. Kornilov wrote: Hi, Can you add a few printks around drivers/usb/musb/musb_cppi41.c to further narrow down where the problem is ? I ran v3.17-rc1 on my beaglebone black (a while back) and didn't have any issues. Now I am rebuilding the kernel to se

Re: OOPS: musb_hdrc

2014-09-08 Thread Felipe Balbi
Hi, it kinda helps if you Cc the maintainer :-) scripts/get_maintainer.pl helps by returning a (usually) correct (and extensive) list of people and mailing lists to Cc :-) anyway... On Mon, Sep 08, 2014 at 09:08:07PM +0400, Matwey V. Kornilov wrote: > Hi, > > Running 3.16.1 on beaglebone black,