On Thu, 30 Jul 2009 15:49:32 +0300
Eduardo Valentin <eduardo.valentin@xxxxxxxxx> wrote:
> From: Peter Ujfalusi <peter.ujfalusi@xxxxxxxxx>
>
> Do not allow applications to use the full buffer found on
> McBSP1,3,4,5. Using the full buffer in threshold mode causes
> the McBSP buffer to run dry, which can be observed as channels
> are switching (in reality the channels are shifting).
>
...
> --- a/arch/arm/mach-omap2/mcbsp.c
> +++ b/arch/arm/mach-omap2/mcbsp.c
> @@ -129,7 +129,7 @@ static struct omap_mcbsp_platform_data
> omap34xx_mcbsp_pdata[] = { .rx_irq =
> INT_24XX_MCBSP1_IRQ_RX, .tx_irq =
> INT_24XX_MCBSP1_IRQ_TX, .ops = &omap2_mcbsp_ops,
> - .buffer_size = 0x7F,
> + .buffer_size = 0x6F,
> },
Is it possible that also McBSP2 would require that maximum burst
transmit size should be 0x10 smaller than size of internal buffer/fifo?
--
Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
