From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
devicetree@vger.kernel.org, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, arnd@arndb.de,
brendanhiggins@google.com, tglx@linutronix.de,
boris.brezillon@collabora.com, anders.roxell@linaro.org,
masonccyang@mxic.com.tw, piotrs@cadence.com, robh+dt@kernel.org,
linux-mips@vger.kernel.org, hauke.mehrtens@intel.com,
qi-ming.wu@intel.com, cheol.yong.kim@intel.com
Subject: Re: [PATCH v2 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC
Date: Mon, 20 Apr 2020 11:28:13 +0800 [thread overview]
Message-ID: <cee6075c-a801-a0a9-f0b7-83c0a8c4fe80@linux.intel.com> (raw)
In-Reply-To: <20200419222817.GK185537@smile.fi.intel.com>
Hi Andy,
Thank you very much for the review comments and your time...
On 20/4/2020 6:28 am, Andy Shevchenko wrote:
> On Fri, Apr 17, 2020 at 04:21:47PM +0800, Ramuthevar,Vadivel MuruganX wrote:
>> From: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>>
>> This patch adds the new IP of Nand Flash Controller(NFC) support
>> on Intel's Lightning Mountain(LGM) SoC.
>>
>> DMA is used for burst data transfer operation, also DMA HW supports
>> aligned 32bit memory address and aligned data access by default.
>> DMA burst of 8 supported. Data register used to support the read/write
>> operation from/to device.
>>
>> NAND controller driver implements ->exec_op() to replace legacy hooks,
>> these specific call-back method to execute NAND operations.
> I guess untested version slipped into mailing list...
> See below why.
Sorry, This is original patch only , header files are mis-aligned so
looks like un-tested patch.
> ...
>
>> +#include <linux/clk.h>
>> +#include <linux/completion.h>
>> +#include <linux/dmaengine.h>
>> +#include <linux/dma-direction.h>
>> +#include <linux/dma-mapping.h>
>> +#include <linux/err.h>
>> +#include <linux/init.h>
>> +#include <linux/iopoll.h>
>> +#include <linux/module.h>
>> +#include <linux/resource.h>
>> +#include <linux/sched.h>
>> +#include <linux/types.h>
>> +#include <linux/mtd/mtd.h>
>> +#include <linux/mtd/rawnand.h>
>> +#include <linux/mtd/nand_ecc.h>
>> +#include <linux/platform_device.h>
>> +#include <linux/of.h>
> Do you need this?
Noted, will check and drop if it is notnecessary.
>> +#include <linux/mtd/partitions.h>
>> +#include <linux/io.h>
>> +#include <linux/slab.h>
>> +#include <mtd/mtd-abi.h>
>> +#include <linux/mod_devicetable.h>
>> +#include <linux/mtd/nand.h>
> Basically, do you need all of them?
>
> And maybe keep them in order?
Sure, will update.
> ...
>
>> +static int lgm_dma_init(struct device *dev, struct lgm_nand_host *lgm_host)
>> +{
>> + int ret;
>> +
>> + /* Prepare for TX DMA: */
>> + lgm_host->dma_tx = dma_request_chan(dev, "tx");
>> + if (IS_ERR(lgm_host->dma_tx)) {
>> + ret = PTR_ERR(lgm_host->dma_tx);
>> + dev_err(dev, "can't get the TX DMA channel, error %d!\n", ret);
>> + goto err;
>> + }
>> +
>> + /* Prepare for RX: */
>> + lgm_host->dma_rx = dma_request_chan(dev, "rx");
>> + if (IS_ERR(lgm_host->dma_rx)) {
>> + ret = PTR_ERR(lgm_host->dma_rx);
>> + dev_err(dev, "can't get the RX DMA channel, error %d\n", ret);
> I suspect this error path hasn't been tested. I don't see where tx channel
> freeing is happening.
Good catch, Thanks!, will update
>> + goto err;
>> + }
>> +
>> + return 0;
>> +err:
>> + return ret;
> Redundant label.
Noted.
>> +}
> ...
>
>> + res = devm_platform_ioremap_resource_byname(pdev, lgm_host->cs_name);
>> + lgm_host->nandaddr_va = res;
>> + nandaddr_pa = res->start;
>> + if (IS_ERR(lgm_host->nandaddr_va))
>> + return PTR_ERR(lgm_host->nandaddr_va);
> I'm wonderig what is this. How is it even compile?
Agreed!, need a correction, but it's compiled.
Regards
Vadivel
>
next prev parent reply other threads:[~2020-04-20 3:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 8:21 [PATCH v2 0/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Ramuthevar,Vadivel MuruganX
2020-04-17 8:21 ` [PATCH v2 1/2] dt-bindings: mtd: Add YAML for Nand Flash Controller support Ramuthevar,Vadivel MuruganX
2020-04-17 8:21 ` [PATCH v2 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Ramuthevar,Vadivel MuruganX
2020-04-17 17:05 ` Hauke Mehrtens
2020-04-20 3:49 ` Ramuthevar, Vadivel MuruganX
2020-04-18 8:55 ` Boris Brezillon
2020-04-19 22:20 ` Andy Shevchenko
2020-04-20 9:17 ` Boris Brezillon
2020-04-20 9:44 ` Andy Shevchenko
2020-04-20 9:52 ` Boris Brezillon
2020-04-20 10:14 ` Andy Shevchenko
2020-04-20 10:28 ` Boris Brezillon
2020-04-20 10:41 ` Andy Shevchenko
2020-04-20 11:06 ` Boris Brezillon
2020-04-20 4:18 ` Ramuthevar, Vadivel MuruganX
2020-04-20 7:40 ` Boris Brezillon
2020-04-20 8:51 ` Ramuthevar, Vadivel MuruganX
2020-04-27 15:38 ` Miquel Raynal
2020-04-27 18:30 ` Boris Brezillon
2020-04-19 22:28 ` Andy Shevchenko
2020-04-20 3:28 ` Ramuthevar, Vadivel MuruganX [this message]
2020-04-20 8:29 ` Boris Brezillon
2020-04-20 9:15 ` Ramuthevar, Vadivel MuruganX
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=cee6075c-a801-a0a9-f0b7-83c0a8c4fe80@linux.intel.com \
--to=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=anders.roxell@linaro.org \
--cc=andriy.shevchenko@intel.com \
--cc=arnd@arndb.de \
--cc=boris.brezillon@collabora.com \
--cc=brendanhiggins@google.com \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke.mehrtens@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=masonccyang@mxic.com.tw \
--cc=miquel.raynal@bootlin.com \
--cc=piotrs@cadence.com \
--cc=qi-ming.wu@intel.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=vigneshr@ti.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).