On Thu, May 11, 2017 at 09:19:17AM +0300, Peter Ujfalusi wrote: > > > On 2017-05-11 02:16, Joe Perches wrote: > >On Wed, 2017-05-10 at 12:07 -0500, Bin Liu wrote: > >>On Wed, May 10, 2017 at 11:42:27AM +0300, Peter Ujfalusi wrote: > >>>We have one register for each EP to set the maximum packet size for both > >>>TX and RX. > >>>If for example an RX programming would happen before the previous TX > >>>transfer finishes we would reset the TX packet side. > >>> > >>>To fix this issue, only modify the TX or RX part of the register. > >[] > >>>diff --git a/drivers/usb/musb/tusb6010_omap.c b/drivers/usb/musb/tusb6010_omap.c > >[] > >>>@@ -389,15 +389,19 @@ static int tusb_omap_dma_program(struct dma_channel *channel, u16 packet_sz, > >>> if (chdat->tx) { > >>> /* Send transfer_packet_sz packets at a time */ > >>>- musb_writel(ep_conf, TUSB_EP_MAX_PACKET_SIZE_OFFSET, > >>>- chdat->transfer_packet_sz); > >>>+ u32 psize = musb_readl(ep_conf, TUSB_EP_MAX_PACKET_SIZE_OFFSET); > >> > >>checkpatch.pl complains about declaration and assignment together. > > > >No it doesn't. > > It 'only' complains about: > WARNING: Missing a blank line after declarations It was it. My bad, I was multi-tasking and didn't read the log carefully. > > which is valid. So will you update the patch to move the declaration to the beginning of the function to avoid this WARNING. I would just fix it locally if you prefer. Regards, -Bin. -- 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