linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ramuthevar, Vadivel MuruganX"  <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: anders.roxell@linaro.org, andriy.shevchenko@intel.com,
	arnd@arndb.de, boris.brezillon@collabora.com,
	brendanhiggins@google.com, cheol.yong.kim@intel.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mtd@lists.infradead.org, masonccyang@mxic.com.tw,
	miquel.raynal@bootlin.com, piotrs@cadence.com,
	qi-ming.wu@intel.com, richard@nod.at, robh+dt@kernel.org,
	tglx@linutronix.de, vigneshr@ti.com
Subject: Re: [PATCH v1 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC
Date: Thu, 16 Apr 2020 17:35:26 +0800	[thread overview]
Message-ID: <c33c8653-16a2-5bcd-97a9-511d958b755a@linux.intel.com> (raw)
In-Reply-To: <20200415220533.733834-1-martin.blumenstingl@googlemail.com>

Hi Martin,

     Thank you so much for review comments and your time...

On 16/4/2020 6:05 am, Martin Blumenstingl wrote:
> Hi,
>
> first of all: thank you for working on upstreaming this.
> Especially since you are going to use the new exec_op style in v2 as
> Boris suggested.
>
>> 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.
> I am wondering how this new hardware is different from the Lantiq NAND
> controller IP - for which there is already a driver in mainline (it's
> in drivers/mtd/nand/raw/xway_nand.c).
> The CON and WAIT registers look suspiciously similar.
>
> As far as I understand the "old" SoCs (VRX200 and earlier) don't have
> a built-in ECC engine. This seems to have changed with ARX300 though
> (again, AFAIK).
>
> A bit of lineage on these SoCs (initially these were developed by
> Infineon. Lantiq then started as an Infineon spin-off in 2009 and
> was then acquired by Intel in 2015):
> - Danube
> - ARX100 from 2008/2009
> - VRX200 from 2009/2010
> - ARX300 from 2014
> - GRX350 from 2015/2016
> - GRX550 from 2017
> - and now finally: LGM from 2020 (est.)
>
> The existing xway_nand driver supports the Danube, ARX100 and VRX200
> SoCs.
Lantiq upstreamed a driver for an older version of this IP core 8 years 
ago, see here:
https://elixir.bootlin.com/linux/v5.5.6/source/drivers/mtd/nand/raw/xway_nand.c 
It does not support DMA and ECC.
This upstream driver works with the xrx200, I do not know how well it 
works with other SoCs.

Regards
Vadivel
>
>
> Best regards,
> Martin

  reply	other threads:[~2020-04-16  9:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  2:24 [PATCH v1 0/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Ramuthevar,Vadivel MuruganX
2020-04-14  2:24 ` [PATCH v1 1/2] dt-bindings: mtd: Add YAML for Nand Flash Controller support Ramuthevar,Vadivel MuruganX
2020-04-14  7:04   ` Boris Brezillon
2020-04-15  1:51     ` Ramuthevar, Vadivel MuruganX
2020-04-14  2:24 ` [PATCH v1 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Ramuthevar,Vadivel MuruganX
2020-04-14  7:21   ` Boris Brezillon
2020-04-15  6:01     ` Ramuthevar, Vadivel MuruganX
2020-04-15 22:05   ` Martin Blumenstingl
2020-04-16  9:35     ` Ramuthevar, Vadivel MuruganX [this message]
2020-04-16  9:38       ` Boris Brezillon
2020-04-16  9:45         ` Ramuthevar, Vadivel MuruganX
2020-04-16 10:26           ` Boris Brezillon
2020-04-16 10:40             ` Ramuthevar, Vadivel MuruganX
2020-04-16 11:17               ` Boris Brezillon
2020-04-16 11:32                 ` Andy Shevchenko
2020-04-17  5:10                   ` Ramuthevar, Vadivel MuruganX
     [not found]                 ` <de9f50b8-9215-d294-9914-e49701552185@linux.intel.com>
2020-04-16 11:57                   ` Boris Brezillon
2020-04-16 12:26                     ` Andy Shevchenko
2020-04-16 12:40                       ` Boris Brezillon
2020-04-16 13:20                         ` Arnd Bergmann
2020-04-16 13:51                           ` John Crispin
2020-04-20  1:09                           ` Ramuthevar, Vadivel MuruganX
2020-04-16 18:08                     ` Martin Blumenstingl
2020-04-17  5:21                     ` Ramuthevar, Vadivel MuruganX
2020-04-17  7:02                       ` Boris Brezillon
2020-04-17  7:53                         ` 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=c33c8653-16a2-5bcd-97a9-511d958b755a@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=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.com \
    --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).