On Mon, 6 Jun 2011 15:30:12 +0800 Shawn Guo <shawn.guo@xxxxxxxxxx> wrote: > Like dma_set(get)_max_seg_size for max_segment_size, the patch adds > max_segment_number into device_dma_parameters and creates the > corresponding dmaengine API dma_set(get)_max_seg_number for it. As I wrote in another mail, dma_get|set_max_seg_size and dma_get|set_seg_boundary are added to the dma mapping API. That is, they enable the drivers (or subsystems) to tell IOMMUs about the device dma limitations. When IOMMUs merge scatter list entries, they look at the limitations. > Here is the user story that tells the need of the new api. The > mxs-mmc is the mmc host controller for Freescale MXS architecture. > There are a pair of mmc host specific parameters max_seg_size and > max_segs that mxs-mmc host driver needs to tell mmc core, so that > mmc core can know how big each data segment could be and how many > segments could be handled one time in a scatter list by host driver. > > The mxs-mmc driver is one user of dmaengine mxs-dma, and it will call > mxs-dma to transfer data in scatter list. That is to say mxs-mmc has > no idea of what max_seg_size and max_segs should be, because they are > all mxs-dma capability parameters, and mxs-mmc needs to query them > from mxs-dma. max_segs isn't unrelated with the dma mapping API. I explained above, IOMMUs doesn't increase the number of segments (could decrease the number of segments by merging). The limitation about the number of segment already lives elsewhere (e.g. queue's limits.max_segments). -- 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
