01.05.2014 23:51, Felipe Balbi пишет:
I don't think you need that. Have tusb_get_revision() run only one
during tusb6010 probe/init function and cache the returned value inside
musb->revision or something like that, then remove all other calls to
tusb_get_revision() and have tusb6010_omap.c check
Hi,
On Thu, May 01, 2014 at 11:44:03PM +0400, Matwey V. Kornilov wrote:
> 01.05.2014 23:40, Felipe Balbi пишет:
> >Hi,
> >
> >On Thu, May 01, 2014 at 11:13:19PM +0400, Matwey V. Kornilov wrote:
> >>
> >>Hi,
> >>
> >>With the following configure options, musb_hdrc and tusb6010 make dependency
> >>l
01.05.2014 23:40, Felipe Balbi пишет:
Hi,
On Thu, May 01, 2014 at 11:13:19PM +0400, Matwey V. Kornilov wrote:
Hi,
With the following configure options, musb_hdrc and tusb6010 make dependency
loop:
CONFIG_USB_MUSB_HDRC=m
CONFIG_USB_MUSB_TUSB6010=m
CONFIG_USB_TUSB_OMAP_DMA=y
tusb6010.ko provi
Hi,
On Thu, May 01, 2014 at 11:13:19PM +0400, Matwey V. Kornilov wrote:
>
> Hi,
>
> With the following configure options, musb_hdrc and tusb6010 make dependency
> loop:
>
> CONFIG_USB_MUSB_HDRC=m
> CONFIG_USB_MUSB_TUSB6010=m
> CONFIG_USB_TUSB_OMAP_DMA=y
>
> tusb6010.ko provides function `tusb_
Hi,
With the following configure options, musb_hdrc and tusb6010 make
dependency loop:
CONFIG_USB_MUSB_HDRC=m
CONFIG_USB_MUSB_TUSB6010=m
CONFIG_USB_TUSB_OMAP_DMA=y
tusb6010.ko provides function `tusb_get_revision` which is used by
tusb6010_omap.o which is a part of musb_hdrc.ko
In its tur