OMAP2/3: DMA: FIFO drain errata fixes
Get series with b4
b4 am [email protected]Versions newest first
- v5 Latest0 of 3 patches 0 repliesNew
Patches in v5 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.
Cover letter [PATCH v5 0/3] OMAP2/3: DMA: FIFO drain errata fixes
Quoted 32 lines · Tony Lindgren
Hi Greg,
Considering below..
Quoted 27 lines · Peter Ujfalusi
Sorry, I did missed this mail...
Quoted 12 lines · On Saturday 09 October 2010 01:17:46 ext Tony Lindgren wrote:
Guys, as we're so late into getting 2.6.36 tagged, I'm thinking about just queueing these for 2.6.37 for the following reasons:
- The 24xx patch is a fix for commit c12abc0 that's was merged over a year ago. We've lived with it for over a year now. What difference does extra few more months make if we have it in 2.6.37 instead of 2.6.36?
- The second 34xx fix seems to happen only when disabling DMA on the fly. Again, we've had support for 34xx in the mainline kernel for a few years, and we're not seeing unrecoverable issues with MMC or USB or any other code calling
omap_dma_stop().Quoted 6 lines
Sure these fix major issues with the DMA, but are these really critical for 2.6.36?
So if you really want me to argue for merging these into 2.6.36, please let me know some oops causing cases or data corruption that happens without these patches.
Well 2.6.36 is released.
I still would like to see this to be part of the 2.6.36.1 release. We can reproduce the DMA error in 2.6.36 with audio.
Quoted 8 lines
Quoted 1 line
Tony: can you make sure it is going to part of 2.6.36.1?
..are you interested in these two patches for stable kernels?
The two patches in question are the following mainline commits:
3e57f1626b5febe5cc99aa6870377deef3ae03cc0e4905c0199d683497833be60a428c784d7575b8
Now queued up, thanks.
greg k-h