On Tue, Jun 7, 2011 at 10:23 PM, FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx> wrote: > On Mon, 6 Jun 2011 11:48:56 -0700 > Dan Williams <dan.j.williams@xxxxxxxxx> wrote: > >> dmaengine expands the class of dma providers to include standalone dma >> agents on a host bus (or elsewhere) in addition to the traditional bus >> mastering host-bus-adapters that the existing api understands. So in >> the case of slave dma the dma capabilities of the block-device are >> irrelevant because another agent will do the transfer on behalf of the >> block-device driver. So the value should be whatever the dma device >> driver says it is. > > The dma parameter restriction could be due to software (HBA drivers, > or subsystem). The value should be whatever the dma device driver says > it is in such case? I'm assuming that the dma driver is taking responsibility for setting this correctly. How would this work otherwise... HBA driver or subsystem queries the dmaengine device and then sets this parameter on its behalf? In other words dmanengine *is* the subsystem, if I am understanding your definition. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
