On 11/12/11 10:51, Jassi Brar wrote: > On Sat, Dec 10, 2011 at 1:20 AM, Javi Merino <javi.merino@xxxxxxx> wrote: >> >> What about properly tracking what we have sent to the DMA? Something >> like the following (warning *ugly* and untested code ahead, may eat your >> kitten): >> > Yeah, this is like I said 'marker' method. Though we can clean it up a bit. > 1) Pack req_running and lstenq together. Make lsteng return invalid value > should there be no buff programmed, otherwise 0 or 1. This can lead to starvation. If lstenq is -1 when the DMA hasn't been programmed yet, in _trigger() you don't know which buffer is the "oldest", so you may end up always starting the new buffer and forgetting about the other one. lstenq as it is right now prevents that. > 2) Try to merge req_running modification as part of MARK_FREE. Yes, I thought about that, but I didn't want to code a proper solution and then receive a "no, we shouldn't go down this road". I'll clean it up and send a proper patch. Cheers, Javi -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |