From: Neil Armstrong <narmstrong@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: ulf.hansson@linaro.org, baylibre-upstreaming@groups.io,
khilman@baylibre.com, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] mmc: meson-gx: add ddr-access-quirk
Date: Wed, 15 May 2019 14:45:38 +0200 [thread overview]
Message-ID: <a54f7a4a-c280-6181-969f-4979dadb36b2@baylibre.com> (raw)
In-Reply-To: <CAFBinCAMoNDnxoQA9XHKy0Xo9MduxD1CvQXOeLZQ3zZ4ViWm7A@mail.gmail.com>
On 14/05/2019 19:58, Martin Blumenstingl wrote:
> Hi Neil,
>
> On Mon, May 13, 2019 at 11:16 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
> [...]
>> @@ -1158,15 +1183,27 @@ static int meson_mmc_probe(struct platform_device *pdev)
>> */
>> mmc->caps2 &= ~MMC_CAP2_HS400;
>>
>> - /* data bounce buffer */
>> - host->bounce_buf_size = mmc->max_req_size;
>> - host->bounce_buf =
>> - dma_alloc_coherent(host->dev, host->bounce_buf_size,
>> - &host->bounce_dma_addr, GFP_KERNEL);
>> - if (host->bounce_buf == NULL) {
>> - dev_err(host->dev, "Unable to map allocate DMA bounce buffer.\n");
>> - ret = -ENOMEM;
>> - goto err_free_irq;
>> + if (host->ddr_access_quirk) {
>> + /*
>> + * The MMC Controller embeds 1,5KiB of internal SRAM
>> + * that can be used to be used as bounce buffer.
>> + * In the case of the G12A SDIO controller, use these
>> + * instead of the DDR memory
>> + */
>> + host->bounce_buf_size = SD_EMMC_SRAM_DATA_BUF_LEN;
>> + host->bounce_buf = host->regs + SD_EMMC_SRAM_DATA_BUF_OFF;
>> + host->bounce_dma_addr = res->start + SD_EMMC_SRAM_DATA_BUF_OFF;
> I'm curious: why do you need to set bounce_dma_addr in this case?
We still need the physical bounce buffer address since we write in the registers,
and we need the logical address to memcpy() in the buffer.
>
>> + } else {
>> + /* data bounce buffer */
>> + host->bounce_buf_size = mmc->max_req_size;
>> + host->bounce_buf =
>> + dma_alloc_coherent(host->dev, host->bounce_buf_size,
>> + &host->bounce_dma_addr, GFP_KERNEL);
>> + if (host->bounce_buf == NULL) {
>> + dev_err(host->dev, "Unable to map allocate DMA bounce buffer.\n");
>> + ret = -ENOMEM;
>> + goto err_free_irq;
>> + }
>> }
>>
>> host->descs = dma_alloc_coherent(host->dev, SD_EMMC_DESC_BUF_LEN,
> if host->descs cannot be allocated then you need to conditionally skip
> dma_free_coherent for the bounce buffer in the goto err_bounce_buf
> case a few lines below (just like you did in meson_mmc_remove)
It can be allocated, it's only useless. I can skip it but I don't want
to break any logic in the driver.
>
>
> Martin
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-05-15 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 9:15 [PATCH 0/3] mmc: meson-gx: add ddr-access-quirk support Neil Armstrong
2019-05-13 9:15 ` [PATCH 1/3] dt-bindings: mmc: meson-gx: add ddr-access-quirk property Neil Armstrong
2019-05-14 17:50 ` Martin Blumenstingl
2019-05-15 12:43 ` Neil Armstrong
2019-05-15 11:37 ` Ulf Hansson
2019-05-15 12:43 ` Neil Armstrong
2019-05-13 9:15 ` [PATCH 2/3] mmc: meson-gx: add ddr-access-quirk Neil Armstrong
2019-05-13 17:47 ` Kevin Hilman
2019-05-14 17:58 ` Martin Blumenstingl
2019-05-15 12:45 ` Neil Armstrong [this message]
2019-05-15 21:18 ` Martin Blumenstingl
2019-05-16 9:09 ` Neil Armstrong
2019-05-15 11:34 ` Ulf Hansson
2019-05-15 12:51 ` Neil Armstrong
2019-05-13 9:15 ` [PATCH 3/3] arm64: dts: meson-g12a: add ddr-access-quirk property to SDIO controller Neil Armstrong
2019-05-14 17:51 ` Martin Blumenstingl
2019-05-13 9:58 ` [PATCH 0/3] mmc: meson-gx: add ddr-access-quirk support Jerome Brunet
2019-05-13 11:28 ` Jerome Brunet
2019-05-14 9:14 ` [baylibre-upstreaming] " guillaume La Roque
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=a54f7a4a-c280-6181-969f-4979dadb36b2@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=baylibre-upstreaming@groups.io \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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
all inboxes | Powered by JetHome®