On Fri, Oct 30, 2015 at 10:15:09PM +0200, Andy Shevchenko wrote: > On Fri, Oct 30, 2015 at 10:08 PM, Al Stone <al.stone@xxxxxxxxxx> wrote: > > On 10/30/2015 01:01 PM, Mark Rutland wrote: > >> On Fri, Oct 30, 2015 at 02:48:06PM -0400, Sinan Kaya wrote: > > >> The CSRT is listed under "Want", not "Never" or "Don't Care", so Linaro > >> have certainly not said that CSRT will not be supported. If anything, > >> they have stated that the table should be supported. > > > > "Want" means interesting, and probably useful, but no clear indication that > > anyone actually needs it. At one point, we thought we might use the CSRT > > for describing DMA, but it turns out we have not needed to. > > Then you are going to have either 1 or 0 DMAC for slave devices, right? I suspect that the currently supported platforms have 0. If not, we have problems. > The CSRT, unfortunately, the only way how to enumerate DMAC to be used > by slave devices. > You may look into drivers/dma/acpi-dma.c for usage in Linux. > > Yes, I know about _DSD, but I don't think it will provide soon any > other official mechanisms to what we have now. Better to ask Rafael > and Mika. _DSD is insufficient here, given that there is no prescribed way to use it to describe DMA. Anything for that would have to go through ASWG before we could use it. Thanks, Mark. -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
