From: Borislav Petkov <bp@alien8.de>
To: wei_wang@realsil.com.cn
Cc: gregkh@linuxfoundation.org, devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
cjb@laptop.org, arnd@arndb.de, aaron.lu@amd.come
Subject: Re: [PATCH 3/3] drivers/mmc/host: Add realtek sdmmc interface driver
Date: Tue, 31 Jul 2012 17:22:04 +0200 [thread overview]
Message-ID: <20120731152204.GA4563@x1.osrc.amd.com> (raw)
In-Reply-To: <1343720576-22181-1-git-send-email-wei_wang@realsil.com.cn>
On Tue, Jul 31, 2012 at 03:42:56PM +0800, wei_wang@realsil.com.cn wrote:
> From: Wei WANG <wei_wang@realsil.com.cn>
>
> Realtek SD/MMC card interface driver is used to access
> SD/MMC card, with the help of Realtek card reader adapter driver.
Yep,
it builds and boots fine with latest Linus tree.
When I put the card in, the kernel says:
[ 1162.197980] rtsx_core: MMC/SD card detected in socket 0:0
[ 1162.302571] rtsx_sdmmc: Realtek SDMMC controller found
[ 1163.202172] mmc0: new ultra high speed SDR50 SDHC card at address e624
[ 1163.237151] mmcblk0: mmc0:e624 SU16G 14.8 GiB
[ 1163.263627] mmcblk0: p1
Then when I format the card it says:
[ 1284.457681] DMA: Out of SW-IOMMU space for 524288 bytes at device 0000:03:00.0
[ 1284.475972] DMA: Out of SW-IOMMU space for 368640 bytes at device 0000:03:00.0
which doesn't look too kosher to me. It comes from
swiotlb.c:swiotlb_full() and it says that in both cases map_single fails
mapping those 524Kb and 368K buffers.
It looks from here as if the driver is trying to map too big buffers
which the swiotlb can't handle? But I'm just stabbing in the dark here.
Accessing the card seems ok, I'll play with it for a while and keep you
posted.
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-07-31 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 7:42 [PATCH 3/3] drivers/mmc/host: Add realtek sdmmc interface driver wei_wang
2012-07-31 15:22 ` Borislav Petkov [this message]
2012-07-31 18:11 ` Borislav Petkov
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=20120731152204.GA4563@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=aaron.lu@amd.come \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=wei_wang@realsil.com.cn \
/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).