From: Jiancheng Xue <xuejiancheng@huawei.com>
To: Marek Vasut <marex@denx.de>, Brian Norris <computersforpeace@gmail.com>
Cc: <linux-mtd@lists.infradead.org>, <robh+dt@kernel.org>,
<dwmw2@infradead.org>, <boris.brezillon@free-electrons.com>,
<juhosg@openwrt.org>, <furquan@google.com>,
<suwenping@hisilicon.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <yanhaifeng@hisilicon.com>,
<raojun@hisilicon.com>, <xuejiancheng@hisilicon.com>,
<ml.yang@hisilicon.com>, <gaofei@hisilicon.com>,
<yanghongwei@hisilicon.com>, <zhangzhenxing@hisilicon.com>
Subject: Re: [RESEND PATCH v9] mtd: spi-nor: add hisilicon spi-nor flash controller driver
Date: Mon, 11 Apr 2016 09:28:15 +0800 [thread overview]
Message-ID: <570AFDAF.9050607@huawei.com> (raw)
In-Reply-To: <5707821F.4020300@denx.de>
Hi,
On 2016/4/8 18:04, Marek Vasut wrote:
> On 04/08/2016 10:26 AM, Jiancheng Xue wrote:
>> Hi,
>>
>> On 2016/4/7 10:28, Marek Vasut wrote:
>>> On 04/07/2016 04:10 AM, Jiancheng Xue wrote:
>>>> Hi Brian,
>>>> Thank you very much for your comments. I'll fix these issues in next version.
>>>> In addition, for easy understanding I'd like to rewrite hisi_spi_nor_write and
>>>> hisi_spi_nor_read. Your comments on these modifications will be highly appreciated.
>>>
>>> Would you please stop top-posting ? It rubs some people the wrong way.
>>>
>> I feel very sorry about that. I have read the etiquette and won't make the same mistake again.
>>
>>>> static int hisi_spi_nor_read(struct spi_nor *nor, loff_t from, size_t len,
>>>> size_t *retlen, u_char *read_buf)
>>>> {
>>>> struct hifmc_priv *priv = nor->priv;
>>>> struct hifmc_host *host = priv->host;
>>>> int i;
>>>>
>>>> /* read all bytes in only one time */
>>>> if (len <= HIFMC_DMA_MAX_LEN) {
>>>> hisi_spi_nor_dma_transfer(nor, from, host->dma_buffer,
>>>> len, FMC_OP_READ);
>>>> memcpy(read_buf, host->buffer, len);
>>>
>>> Is all the ad-hoc memcpying necessary? I think you can use
>>> dma_map_single() and co to obtain DMAble memory for your
>>> controller's use and then you can probably get rid of most
>>> of this stuff.
>>>
>> Considering read_buf >= high_mem case, I think it is also complicated to use dma_map_*
>> and the DMA buffer allocated by the driver is still needed. But I am not sure about
>> this. Please let me know if I am wrong. Thank you!
>
> Does your controller/DMA have a limitation where it's buffers must be in
> the bottom 4GiB range ? The DMA framework should be able to take care of
> such platform limitations.
>
When read_buf is allocated by vmalloc, the underlying physical memory may be not contiguous.
In this case, dma_map_single can't be used directly. I think inner DMA buffer and memcpy are still
needed. Am I right?
Regards,
Jiancheng.
next prev parent reply other threads:[~2016-04-11 1:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 8:11 [RESEND PATCH v9] mtd: spi-nor: add hisilicon spi-nor flash controller driver Jiancheng Xue
2016-03-27 1:47 ` Marek Vasut
2016-03-28 9:15 ` Jiancheng Xue
2016-04-04 6:44 ` Brian Norris
2016-04-07 2:10 ` Jiancheng Xue
2016-04-07 2:28 ` Marek Vasut
2016-04-08 8:26 ` Jiancheng Xue
2016-04-08 10:04 ` Marek Vasut
2016-04-11 1:28 ` Jiancheng Xue [this message]
2016-04-11 19:21 ` Marek Vasut
2016-04-12 9:32 ` Jiancheng Xue
2016-04-12 9:44 ` Boris Brezillon
2016-04-13 9:24 ` Jiancheng Xue
2016-03-31 7:24 ` Jiancheng Xue
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=570AFDAF.9050607@huawei.com \
--to=xuejiancheng@huawei.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=furquan@google.com \
--cc=gaofei@hisilicon.com \
--cc=juhosg@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=ml.yang@hisilicon.com \
--cc=raojun@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=suwenping@hisilicon.com \
--cc=xuejiancheng@hisilicon.com \
--cc=yanghongwei@hisilicon.com \
--cc=yanhaifeng@hisilicon.com \
--cc=zhangzhenxing@hisilicon.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).