On Mon, Jun 10, 2013 at 11:15 AM, Lee Jones <lee.jones@xxxxxxxxxx> wrote: > On Wed, 15 May 2013, Linus Walleij wrote: > >> On Wed, May 15, 2013 at 11:51 AM, Lee Jones <lee.jones@xxxxxxxxxx> wrote: >> >> > It was required to pass DMA channel configuration information to the >> > MMC driver before the new DMA API was in place. Now that it is, and >> > is fully compatible with Device Tree we can stop doing that. >> > >> > Reviewed-by: Linus Walleij <linus.walleij@xxxxxxxxxx> >> > Signed-off-by: Lee Jones <lee.jones@xxxxxxxxxx> >> >> So since the use of dma_request_slave_channel() is not upstream, >> I guess this will break DMA use (i.e slow down transfers!) on all >> device tree boots? >> >> I'd be happy to apply it once the MMCI patch is in linux-next >> indicating there may just be a window in the merge period >> where it falls back to IRQ mode, but I don't want to disable >> DMA on DT boots for an entire kernel cycle just like that. >> >> Not applied as of yet. > > I believe it's now okay to apply this. Yep, I've rebased and applied it to the ux500-devicetree branch. I have some stuff on this branch which is queued up but may miss v3.11, because I need the 5 outstanding pull requests to land in ARM SoC so I get a merge base there before I can send any more stuff. It's mainly because this stuff isn't any orthogonal, everything just conflicts in the AUXDATA all the time. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
