2014-09-17 19:46 GMT+04:00 Felipe Balbi <balbi@xxxxxx>: > On Wed, Sep 17, 2014 at 07:35:14PM +0400, Matwey V. Kornilov wrote: >> 2014-09-17 19:25 GMT+04:00 Felipe Balbi <balbi@xxxxxx>: >> > On Wed, Sep 17, 2014 at 10:46:57AM +0400, Matwey V. Kornilov wrote: >> >> 2014-09-16 22:39 GMT+04:00 Felipe Balbi <balbi@xxxxxx>: >> >> > Hi, >> >> > >> >> > (man, talk about trimming... leave some context ;-) >> >> > >> >> > On Tue, Sep 16, 2014 at 10:06:33PM +0400, Matwey V. Kornilov wrote: >> >> >> Ok. What is about musb_io.h? What does it mean "TUSB6010 doesn't allow >> >> >> 8-bit access; 16-bit access is the minimum."? >> >> > >> >> > it means that readb() won't work. >> >> > >> >> >> I think __raw_readb is kind of return *(u8_t*)(addr), but this is CPU >> >> >> stuff as far as I understand. >> >> > >> >> > tusb6010 is a discrete device connected through GPMC (general purpose >> >> > memory controller). Basically, this tells you that tusb6010 cannot >> >> > understand 8-bit accesses through gpmc. >> >> > >> >> >> >> So, I checked the stuff in musb_io.h and it doesn't work properly for >> >> my BBB. I don't know why. With this tusb6010-custom >> >> musb_readb/musb_writeb functions I am not able to mount USB flash >> >> drive (the device is being reset constantly, at the same time the >> >> webcam works fine). With __raw functions, it is fine. >> >> >> >> Do you have an idea how this could be refactored? >> > >> > can't think of a solution off the top of my head. >> >> Using musb->ops->readb everywhere will add too much overhead probably. > > correct :-) > > -- > balbi Could you please fix the Kconfig to prevent broken configurations until this fixed? -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
