OMAP3: McBSP: Change the way how the FIFO is handled
authorPeter Ujfalusi <peter.ujfalusi@nokia.com>
Thu, 3 Jun 2010 04:39:33 +0000 (07:39 +0300)
committerLiam Girdwood <lrg@slimlogic.co.uk>
Thu, 3 Jun 2010 15:12:40 +0000 (16:12 +0100)
commit451fd82dc148bd5ac9ed5b19b6915a1afe32b9cb
tree0bd09462f284fbdef0ed98f7d05ed4018302f296
parent0acce82b3dd792c85079ca1f4f7ffd8c82427e0a
OMAP3: McBSP: Change the way how the FIFO is handled

Use the actual FIFO size in words as buffer_size on OMAP3.
Change the threshold configuration to use 1 based numbering, when
specifying the allowed threshold maximum or the McBSP threshold value.
Set the default maximum threshold to (buffer_size - 0x10) intialy.
>From users of McBSP, now it is expected to use this method.
Asking for threshold 1 means that the value written to threshold registers
are going to be 0, which means 1 word threshold.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Acked-by: Jarkko Nikula <jhnikula@gmail.com>
Acked-by: Mark Brown <broonie@opensource.wolsfonmicro.com>
Acked-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
arch/arm/mach-omap2/mcbsp.c
arch/arm/plat-omap/mcbsp.c