From: Adrian Hunter <adrian.hunter@intel.com>
To: Chunyan Zhang <zhang.chunyan@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linaro.org>,
Billows Wu <billows.wu@spreadtrum.com>,
zhang.lyra@gmail.com
Subject: Re: [PATCH V3 2/7] mmc: sdhci: made changes for System Address register of SDMA
Date: Mon, 16 Jul 2018 16:23:37 +0300 [thread overview]
Message-ID: <ff9c22dc-b462-98d9-fb74-930107a3d66f@intel.com> (raw)
In-Reply-To: <1653583c-8d5b-6781-e923-9dcfd1e96403@intel.com>
On 16/07/18 16:03, Adrian Hunter wrote:
> On 09/07/18 06:19, Chunyan Zhang wrote:
>> According to the SD host controller specification version 4.10, when
>> Host Version 4 is enabled, SDMA uses ADMA System Address register
>> (05Fh-058h) instead of using SDMA System Address register to
>> support both 32-bit and 64-bit addressing.
>
> The commit message is good but the subject is not so good. What about
> "Change SDMA address register for V4 mode"
>
>>
>> Signed-off-by: Chunyan Zhang <zhang.chunyan@linaro.org>
>> ---
>> drivers/mmc/host/sdhci.c | 25 ++++++++++++++++++-------
>> 1 file changed, 18 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
>> index 525862f..c7de6a5 100644
>> --- a/drivers/mmc/host/sdhci.c
>> +++ b/drivers/mmc/host/sdhci.c
>> @@ -701,7 +701,7 @@ static void sdhci_adma_table_post(struct sdhci_host *host,
>> }
>> }
>>
>> -static u32 sdhci_sdma_address(struct sdhci_host *host)
>> +static dma_addr_t sdhci_sdma_address(struct sdhci_host *host)
>> {
>> if (host->bounce_buffer)
>> return host->bounce_addr;
>> @@ -709,6 +709,18 @@ static u32 sdhci_sdma_address(struct sdhci_host *host)
>> return sg_dma_address(host->data->sg);
>> }
>>
>> +static void sdhci_set_sdma_addr(struct sdhci_host *host, dma_addr_t addr)
>> +{
>> + if (host->v4_mode) {
>> + sdhci_writel(host, addr, SDHCI_ADMA_ADDRESS);
>> + if (host->flags & SDHCI_USE_64_BIT_DMA)
>> + sdhci_writel(host, (u64)addr >> 32, SDHCI_ADMA_ADDRESS_HI);
Also need to adjust the initialization in sdhci_setup_host() which prevents
SDMA with 64-bit DMA i.e.
/* SDMA does not support 64-bit DMA */
if (host->flags & SDHCI_USE_64_BIT_DMA)
host->flags &= ~SDHCI_USE_SDMA;
>> + } else {
>> + sdhci_writel(host, addr, SDHCI_DMA_ADDRESS);
>> + }
>> +
>> +}
>> +
>> static unsigned int sdhci_target_timeout(struct sdhci_host *host,
>> struct mmc_command *cmd,
>> struct mmc_data *data)
>> @@ -968,8 +980,7 @@ static void sdhci_prepare_data(struct sdhci_host *host, struct mmc_command *cmd)
>> SDHCI_ADMA_ADDRESS_HI);
>> } else {
>> WARN_ON(sg_cnt != 1);
>> - sdhci_writel(host, sdhci_sdma_address(host),
>> - SDHCI_DMA_ADDRESS);
>> + sdhci_set_sdma_addr(host, sdhci_sdma_address(host));
>> }
>> }
>>
>> @@ -2796,7 +2807,7 @@ static void sdhci_data_irq(struct sdhci_host *host, u32 intmask)
>> * some controllers are faulty, don't trust them.
>> */
>> if (intmask & SDHCI_INT_DMA_END) {
>> - u32 dmastart, dmanow;
>> + dma_addr_t dmastart, dmanow;
>>
>> dmastart = sdhci_sdma_address(host);
>> dmanow = dmastart + host->data->bytes_xfered;
>> @@ -2807,9 +2818,9 @@ static void sdhci_data_irq(struct sdhci_host *host, u32 intmask)
>> ~(SDHCI_DEFAULT_BOUNDARY_SIZE - 1)) +
>
> That isn't going to work with 64-bit addresses. Need to cast
> SDHCI_DEFAULT_BOUNDARY_SIZE to dma_addr_t
>
>> SDHCI_DEFAULT_BOUNDARY_SIZE;
>> host->data->bytes_xfered = dmanow - dmastart;
>> - DBG("DMA base 0x%08x, transferred 0x%06x bytes, next 0x%08x\n",
>> - dmastart, host->data->bytes_xfered, dmanow);
>> - sdhci_writel(host, dmanow, SDHCI_DMA_ADDRESS);
>> + DBG("DMA base 0x%016llx, transferred 0x%06x bytes, next 0x%016llx\n",
>
> Can you use %pad for dma_addr_t
>
>> + (u64)dmastart, host->data->bytes_xfered, (u64)dmanow);
>> + sdhci_set_sdma_addr(host, dmanow);
>> }
>>
>> if (intmask & SDHCI_INT_DATA_END) {
>>
>
>
next prev parent reply other threads:[~2018-07-16 13:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 3:19 [PATCH V3 0/7] mmc: add support for sdhci 4.0 Chunyan Zhang
2018-07-09 3:19 ` [PATCH V3 1/7] mmc: sdhci: add sd host v4 mode Chunyan Zhang
2018-07-09 3:19 ` [PATCH V3 2/7] mmc: sdhci: made changes for System Address register of SDMA Chunyan Zhang
2018-07-16 13:03 ` Adrian Hunter
2018-07-16 13:23 ` Adrian Hunter [this message]
2018-07-09 3:19 ` [PATCH V3 3/7] mmc: sdhci: add ADMA2 64-bit addressing support for V4 mode Chunyan Zhang
2018-07-16 13:34 ` Adrian Hunter
2018-07-09 3:19 ` [PATCH V3 4/7] mmc: sdhci: add 32-bit block count support for v4 mode Chunyan Zhang
2018-07-17 8:29 ` Adrian Hunter
2018-07-17 9:14 ` Chunyan Zhang
2018-07-17 10:36 ` Adrian Hunter
2018-07-23 7:11 ` Chunyan Zhang
2018-07-09 3:19 ` [PATCH V3 5/7] mmc: sdhci: add Auto CMD Auto Select support Chunyan Zhang
2018-07-17 11:16 ` Adrian Hunter
2018-07-23 7:11 ` Chunyan Zhang
2018-07-09 3:19 ` [PATCH V3 6/7] mmc: sdhci-sprd: added Spreadtrum's initial host controller Chunyan Zhang
2018-07-17 11:52 ` Adrian Hunter
2018-07-18 7:24 ` Chunyan Zhang
2018-07-18 7:47 ` Adrian Hunter
2018-07-09 3:19 ` [PATCH V3 7/7] dt-bindings: sdhci-sprd: Add bindings for the sdhci-sprd controller Chunyan Zhang
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=ff9c22dc-b462-98d9-fb74-930107a3d66f@intel.com \
--to=adrian.hunter@intel.com \
--cc=baolin.wang@linaro.org \
--cc=billows.wu@spreadtrum.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=zhang.chunyan@linaro.org \
--cc=zhang.lyra@gmail.com \
/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).