Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758023AbcDHI3K (ORCPT ); Fri, 8 Apr 2016 04:29:10 -0400 Received: from szxga02-in.huawei.com ([119.145.14.65]:54440 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754204AbcDHI3I (ORCPT ); Fri, 8 Apr 2016 04:29:08 -0400 Subject: Re: [RESEND PATCH v9] mtd: spi-nor: add hisilicon spi-nor flash controller driver To: Marek Vasut , Brian Norris References: <1458979861-3619-1-git-send-email-xuejiancheng@huawei.com> <56F73BC9.5000300@gmail.com> <56F8F630.5050008@huawei.com> <20160404064418.GC13995@localhost> <5705C17F.9030904@huawei.com> <5705C5E2.6070206@denx.de> CC: , , , , , , , , , , , , , , , From: Jiancheng Xue Message-ID: <57076B26.7030700@huawei.com> Date: Fri, 8 Apr 2016 16:26:14 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <5705C5E2.6070206@denx.de> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.217.211] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.57076B2B.003B,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 9df6db9ea8cf08eae4fc161db59bc727 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2177 Lines: 65 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! Regards, Jiancheng >> } else { >> /* read HIFMC_DMA_MAX_LEN bytes at a time */ >> for (i = 0; i < len; i += HIFMC_DMA_MAX_LEN) { >> hisi_spi_nor_dma_transfer(nor, from + i, host->dma_buffer, >> HIFMC_DMA_MAX_LEN, FMC_OP_READ); >> memcpy(read_buf + i, host->buffer, HIFMC_DMA_MAX_LEN); >> } >> /* read remaining bytes */ >> i -= HIFMC_DMA_MAX_LEN; >> hisi_spi_nor_dma_transfer(nor, from + i, host->dma_buffer, >> len - i, FMC_OP_READ); >> memcpy(read_buf + i, host->buffer, len - i); >> } >> *retlen = len; >> >> return 0; >> } >> [...] >> On 2016/4/4 14:44, Brian Norris wrote: >>> Hi Jiancheng, >>> >>> Looking good. In addition to Marek's comments, I have just a few small >>> comments. I'll post a small diff at the end, and a few inline comments. >>> > >