From afbf72505be3da3bb7563e3e403020a3ba62f4f7 Mon Sep 17 00:00:00 2001 From: Rui Miguel Silva <rui.silva@linaro.org> Date: Tue, 9 Aug 2016 23:35:35 +0100 Subject: [PATCH] greybus: sdio: increase maximum segment size Adjust maximum segment size of the sg list to meet the maximum request size, this will allow to have less segments which increase the performance of data movement during transfer operations. Test Done: using mmc_test with best-case read/write performance and see that only one segment is used and that the results are better (288KiB vs 300KiB in read operation). Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@google.com> --- drivers/staging/greybus/sdio.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/greybus/sdio.c b/drivers/staging/greybus/sdio.c index 3d3599a8b077f..a78d9e4a03211 100644 --- a/drivers/staging/greybus/sdio.c +++ b/drivers/staging/greybus/sdio.c @@ -802,11 +802,11 @@ static int gb_sdio_probe(struct gbphy_device *gbphy_dev, mmc->ops = &gb_sdio_ops; - /* for now we just make a map 1:1 between max blocks and segments */ mmc->max_segs = host->mmc->max_blk_count; - mmc->max_seg_size = host->mmc->max_blk_size; + /* for now we make a map 1:1 between max request and segment size */ mmc->max_req_size = mmc->max_blk_size * mmc->max_blk_count; + mmc->max_seg_size = mmc->max_req_size; mutex_init(&host->lock); spin_lock_init(&host->xfer); -- 2.30.2