From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] mmc: mxs-mmc: call dmaengine API to set mmc->max_segs
Date: Thu, 26 May 2011 14:31:33 +0800 [thread overview]
Message-ID: <1306391493-29425-3-git-send-email-shawn.guo@linaro.org> (raw)
In-Reply-To: <1306391493-29425-1-git-send-email-shawn.guo@linaro.org>
With dmaengine API dma_get_max_seg_number added, we now can call
the API to get and number and then set mmc->max_segs instead of
hard-coding it.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
---
drivers/mmc/host/mxs-mmc.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/mxs-mmc.c b/drivers/mmc/host/mxs-mmc.c
index 99d39a6..d783af3 100644
--- a/drivers/mmc/host/mxs-mmc.c
+++ b/drivers/mmc/host/mxs-mmc.c
@@ -745,11 +745,15 @@ static int mxs_mmc_probe(struct platform_device *pdev)
mmc->f_max = 288000000;
mmc->ocr_avail = MMC_VDD_32_33 | MMC_VDD_33_34;
- mmc->max_segs = 52;
mmc->max_blk_size = 1 << 0xf;
mmc->max_blk_count = (ssp_is_old()) ? 0xff : 0xffffff;
mmc->max_req_size = (ssp_is_old()) ? 0xffff : 0xffffffff;
mmc->max_seg_size = dma_get_max_seg_size(host->dmach->device->dev);
+ /*
+ * Reserve one segment for carrying on pio words to get dma engine
+ * program mmc controller registers
+ */
+ mmc->max_segs = dma_get_max_seg_number(host->dmach->device->dev) - 1;
platform_set_drvdata(pdev, mmc);
--
1.7.4.1
next prev parent reply other threads:[~2011-05-26 6:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 6:31 [PATCH 1/3] dmaengine: add new dma API for max_segment_number Shawn Guo
2011-05-26 6:31 ` [PATCH 2/3] dmaengine: mxs-dma: set up max_segment_number Shawn Guo
2011-05-26 6:31 ` Shawn Guo [this message]
2011-06-01 2:33 ` [PATCH 1/3] dmaengine: add new dma API for max_segment_number Shawn Guo
2011-06-05 1:30 ` FUJITA Tomonori
2011-06-06 5:28 ` Koul, Vinod
2011-06-06 6:38 ` FUJITA Tomonori
2011-06-06 6:54 ` Shawn Guo
2011-06-06 8:06 ` FUJITA Tomonori
2011-06-01 7:42 ` Koul, Vinod
2011-06-02 5:56 ` Shawn Guo
2011-06-06 5:35 ` Koul, Vinod
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1306391493-29425-3-git-send-email-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).