From: Shawn Lin <shawn.lin@rock-chips.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: shawn.lin@rock-chips.com, linux-mmc <linux-mmc@vger.kernel.org>,
"Jyan Chou [周芷安]" <jyanchou@realtek.com>,
Jisheng.Zhang@synaptics.com
Subject: Re: Question about EMMC CMDQ HOST CONTROLLER INTERFACE (CQHCI) DRIVER
Date: Tue, 8 Nov 2022 17:14:44 +0800 [thread overview]
Message-ID: <dcac1f10-98a7-b831-005c-542b8a0d4337@rock-chips.com> (raw)
In-Reply-To: <38161cf2-4e6e-dbb3-4743-a21657b92451@intel.com>
+ Jisheng Zhang
On 2022/11/8 16:34, Adrian Hunter wrote:
> On 8/11/22 10:28, Shawn Lin wrote:
>> On 2022/11/8 16:20, Adrian Hunter wrote:
>>> On 8/11/22 09:25, Jyan Chou [周芷安] wrote:
>>>> Hello Adrian Hunter,
>>>>
>>>> We are now using the upstream code of EMMC CMDQ HOST CONTROLLER INTERFACE (CQHCI) DRIVER, but we found that the existing driver cannot support the limitation of Synopsys IP.
>>>>
>>>> Synopsys IP has a description on their data book " While using DMA, the host memory data buffer size and start address must not exceed 128 MB".
>>
>> Synopsys-based SDHCI IP does have a limitation of 128MB boundary. But it
>> has already been solved by upstream driver.
>>
>> FYI:
>>
>> commit b85c997d2cfefe7d1f706b85ae46e35a50e3131c ("mmc: sdhci-of-dwcmshc: solve 128MB DMA boundary limitation")
>
> CQHCI has its own DMA descriptors, so maybe a similar change is needed for CQHCI?
I didn't find this limitation in synopsys DW IP databook.
>
>>
>>>>
>>>> I am wondering whether there is a method or patch that can fix this boundary limitation.
>>>> Thanks.
>>>> Best Regards,
>>>> Jyan Chou
>>>
>>> Hello Jyan Chou
>>>
>>> I am not clear on what the exact limitation is. The driver never uses buffers as big as 128 MB.
>>> To restrict DMA to low memory addresses a DMA mask can be used.
>>>
>>> But perhaps you mean not to cross a 128 MB boundary?
>>>
>>> Please cc your questions to the linux kernel mmc mailing list: linux-mmc@vger.kernel.org because others
>>> can answer too.
>>>
>>> Regards
>>> Adrian
>
next prev parent reply other threads:[~2022-11-08 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5842d536cb0d4086a225ea0fa2d42e72@realtek.com>
2022-11-08 8:20 ` Question about EMMC CMDQ HOST CONTROLLER INTERFACE (CQHCI) DRIVER Adrian Hunter
2022-11-08 8:28 ` Shawn Lin
2022-11-08 8:34 ` Adrian Hunter
2022-11-08 9:14 ` Shawn Lin [this message]
2022-11-08 9:19 ` Jyan Chou [周芷安]
2022-11-09 3:45 ` Shawn Lin
2022-11-10 2:11 ` Jyan Chou [周芷安]
2022-11-10 8:11 ` Adrian Hunter
2022-11-08 8:35 ` Jyan Chou [周芷安]
[not found] <6d989a63463b4d1e8c1f468754f4f424@realtek.com>
2023-06-20 6:46 ` Adrian Hunter
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=dcac1f10-98a7-b831-005c-542b8a0d4337@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=adrian.hunter@intel.com \
--cc=jyanchou@realtek.com \
--cc=linux-mmc@vger.kernel.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