Mark Brown wrote:
> On Sat, Jul 04, 2009 at 07:30:01PM -0700, Troy Kisky wrote:
> If you mean that it should start and
> stop the clocks
Yes.
> that causes issues in situations like TDM since there
> can be transfers going on independantly of the CPU which may need the
> clocks running. Not every
Mark Brown wrote:
>>> battery life by setting up very big DMAs. On a similar vein is it worth
>>> considering making this feature entirely optional and/or falling back to
>>> non-SRAM if SRAM allocation fails?
>
>> Yes Chris Ring also asked for that, and it is fairly easy to allocate another
>> S
Troy Kisky wrote:
> Mark Brown wrote:
>
> Even when using SDRAM, there is still another advantage to double buffering.
> That is tolerating very long interrupt latency on dma completion. The current
> code sets up the next periods dma transfer on dma completion. This could
> easily
> lead to unde
Troy Kisky wrote:
> Troy Kisky wrote:
>> Mark Brown wrote:
>>
>> Even when using SDRAM, there is still another advantage to double buffering.
>> That is tolerating very long interrupt latency on dma completion. The current
>> code sets up the next periods dma transfer on dma completion. This could
