From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"tgih.jun@samsung.com" <tgih.jun@samsung.com>,
"arc-linux-dev@synopsys.com" <arc-linux-dev@synopsys.com>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>
Subject: Re: [PATCH] mmc: dw_mmc: handle data blocks > than 4kB if IDMAC is used
Date: Wed, 1 Jul 2015 15:45:31 +0530 [thread overview]
Message-ID: <5593BDC3.6040301@synopsys.com> (raw)
In-Reply-To: <1435744933.4689.31.camel@synopsys.com>
On Wednesday 01 July 2015 03:32 PM, Alexey Brodkin wrote:
> Hi Jaehoon, Seungwon, Ulf,
>
> On Thu, 2015-06-25 at 11:25 +0300, Alexey Brodkin wrote:
>> > As per DW MobileStorage databook "each descriptor can transfer up to
>> > 4kB
>> > of data in chained mode", moreover buffer size that is put in "des1"
>> > is
>> > limited to 13 bits, i.e. for example on attempt to
>> > IDMAC_SET_BUFFER1_SIZE(desc, 8192) size value that's effectively
>> > written
>> > will be 0.
>> >
>> > On the platform with 8kB PAGE_SIZE I see dw_mmc gets data blocks in
>> > SG-list of 8kB size and that leads to unpredictable behavior of the
>> > SD/MMC controller.
>> >
>> > In particular on write to FAT partition of SD-card the controller
>> > will
>> > stuck in the middle of DMA transaction.
>> >
>> > Solution to the problem is simple - we need to pass large (> 4kB)
>> > data
>> > buffers to the controller via multiple descriptors. And that's what
>> > that change does.
>> >
>> > What's interesting I did try original driver on same platform but
>> > configured with 4kB PAGE_SIZE and may confirm that data blocks passed
>> > in SG-list to dw_mmc never exeed 4kB limit - that explains why nobody
>> > ever faced a problem I did.
>> >
>> > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
>> > Cc: Seungwon Jeon <tgih.jun@samsung.com>
>> > Cc: Jaehoon Chung <jh80.chung@samsung.com>
>> > Cc: Ulf Hansson <ulf.hansson@linaro.org>
>> > Cc: arc-linux-dev@synopsys.com
>> > Cc: linux-kernel@vger.kernel.org
>> > ---
>> > drivers/mmc/host/dw_mmc.c | 109 ++++++++++++++++++++++++++++++------
>> > ----------
> I'm wondering if there're any comments on that patch or if it could be
> applied?
>
> It fixes a real problem on systems on 4K PAGE_SIZE so would be good to
s/4K/8k
Alexey fat-fingered it seems. ARC cores by default have 8k MMU page size and we
saw this issue on ARC SDP boards !
-Vineet
> have it in upstream. In particular this is the case with ARC AXS board
> which made its way in upstream kernel recently.
>
> Regards,
> Alexey--
next prev parent reply other threads:[~2015-07-01 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 8:25 [PATCH] mmc: dw_mmc: handle data blocks > than 4kB if IDMAC is used Alexey Brodkin
2015-07-01 10:02 ` Alexey Brodkin
2015-07-01 10:13 ` Jaehoon Chung
2015-07-06 7:12 ` Alexey Brodkin
2015-07-01 10:15 ` Vineet Gupta [this message]
2015-07-08 4:14 ` Jaehoon Chung
2015-07-08 8:45 ` Alexey Brodkin
2015-07-09 13:04 ` Alexey Brodkin
2015-07-09 14:44 ` Jaehoon Chung
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=5593BDC3.6040301@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=arc-linux-dev@synopsys.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.com \
--cc=ulf.hansson@linaro.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).