public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 0/5] mtd: pxa3xx_nand: add support for Armada 8k
Date: Mon, 26 Oct 2020 10:36:49 +0100	[thread overview]
Message-ID: <20201026103649.39ff097c@xps13> (raw)
In-Reply-To: <056dc383-66e0-65b1-c20c-18f143bd120f@denx.de>

Hi Stefan,

Stefan Roese <sr@denx.de> wrote on Tue, 20 Oct 2020 10:29:52 +0200:

> Hi Baruch,
> Hi Chris,
> 
> On 19.10.20 07:24, Baruch Siach wrote:
> > Hi Chris,
> > 
> > On Sun, Oct 18 2020, Chris Packham wrote:  
> >> On Mon, Oct 19, 2020 at 1:59 AM Baruch Siach <baruch@tkos.co.il> wrote:  
> >>>
> >>> This series adds NAND flash support to Aramda 8k systems. Patches make the
> >>> necessary changes to the pxa3xx_nand driver and DT files.
> >>>
> >>> v2:
> >>>    Rebase on current master. Fixes conflict with commit 661c98121d4 ("mtd: nand:
> >>>    pxa3xx: Fix not calling dev_xxx with a device")  
> >>
> >> Is it worth looking at bringing in the newer marvell_nand driver from
> >> Linux? I suspect that it will be easier to keep in sync with changes
> >> for the Armada 8K. I have considered it in the past but it kind of
> >> fell off my radar.  
> > 
> > The kernel raw nand API has seen some significant changes recently. It
> > looks like the kernel marvell_nand driver relies on newer API. I'm not
> > sure how easy would be syncing the drivers to a degree that makes
> > porting of changes trivial. It would probably require many other changes
> > in generic U-Boot raw NAND code.  
> 
> I agree that without a re-sync with a more recent Linux MTD (NAND) core
> code, this task might prove complex and failure prone. And sync'ing the
> MTD core is also a pretty complex task which needs to be done very
> carefully, to not break any existing platforms. FWICT, nobody is working
> on it right now and we can't wait for this to happen and stall the
> development here. So from my point of view, I'm okay with updates to
> the current PXA NAND driver. Testing of these patches on other platforms
> would be very welcome though.
> 
> > Maybe Miquel can shed some light on that.

Yes, the "new" marvell_nand.c driver is using the ->exec_op() interface
which is the one that must be ported to U-Boot. Many changes have been
brought to the raw NAND core but everything has been carefully patched
to be easily ported (besides the huge number of potential
dependencies that have not been brought to U-Boot already). Bringing-in 
this new interface does not affect the other controller drivers though,
as the ->cmdfunc() and ->cmd_ctrl() interfaces are still functional.

Thanks,
Miqu?l

      parent reply	other threads:[~2020-10-26  9:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-18 12:56 [PATCH v2 0/5] mtd: pxa3xx_nand: add support for Armada 8k Baruch Siach
2020-10-18 12:56 ` [PATCH v2 1/5] arm: dts: armada-cp110-slave: add missing cps_nand Baruch Siach
2020-10-28 11:13   ` Stefan Roese
2020-10-18 12:56 ` [PATCH v2 2/5] arm: dts: armada-cp110-master: update nand-controller Baruch Siach
2020-10-28 11:13   ` Stefan Roese
2020-10-18 12:56 ` [PATCH v2 3/5] mtd: pxa3xx_nand: port to use driver model Baruch Siach
2020-10-28 11:16   ` Stefan Roese
2020-10-18 12:56 ` [PATCH v2 4/5] mtd: pxa3xx_nand: remove dead code Baruch Siach
2020-10-28 11:16   ` Stefan Roese
2020-10-18 12:56 ` [PATCH v2 5/5] mtd: nand: pxa3xx: enable NAND controller if the SoC needs it Baruch Siach
2020-10-28 11:17   ` Stefan Roese
2020-10-18 20:17 ` [PATCH v2 0/5] mtd: pxa3xx_nand: add support for Armada 8k Chris Packham
2020-10-19  5:24   ` Baruch Siach
2020-10-20  8:29     ` Stefan Roese
2020-10-20  9:19       ` Baruch Siach
2020-10-26  9:36       ` Miquel Raynal [this message]

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=20201026103649.39ff097c@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=u-boot@lists.denx.de \
    /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