From: Boris Brezillon <boris.brezillon@collabora.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Richard Weinberger <richard@nod.at>, Sekhar Nori <nsekhar@ti.com>,
"open list:MEMORY TECHNOLOGY..." <linux-mtd@lists.infradead.org>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH 0/5] mtd: rawnand: davinci: Convert to exec_op()
Date: Mon, 4 May 2020 22:06:30 +0200 [thread overview]
Message-ID: <20200504220630.716d328f@collabora.com> (raw)
In-Reply-To: <CAMpxmJXmPcwo6uomrrwbcFe9gkhxvYVw0Y6o1n5uSGBwPKd5_A@mail.gmail.com>
On Mon, 4 May 2020 18:34:55 +0200
Bartosz Golaszewski <bgolaszewski@baylibre.com> wrote:
> pt., 1 maj 2020 o 12:07 Boris Brezillon
> <boris.brezillon@collabora.com> napisał(a):
> >
> > Hello,
> >
> > A bit of context to explain the motivation behind those conversions
> > I've been sending for the last couple of weeks. The raw NAND subsystem
> > carries a lot of history which makes any rework not only painful, but
> > also subject to regressions which we only detect when someone dares to
> > update its kernel on one of those ancient HW. While carrying drivers
> > for old HW is not a problem per se, carrying ancient and unmaintained
> > drivers that are not converted to new APIs is a maintenance burden,
> > hence this massive conversion attempt I'm conducting here.
> >
> > So here is a series converting the Davinci NAND controller driver to
> > exec_op(), plus a bunch of minor improvements done along the way.
> >
> > Regards,
> >
> > Boris
> >
> > Boris Brezillon (5):
> > mtd: rawnand: davinci: Inherit from nand_controller
> > mtd: rawnand: davinci: Stop using nand_chip.legacy.IO_ADDR_{R,W}
> > mtd: rawnand: davinci: Implement exec_op()
> > mtd: rawnand: davinci: Get rid of the legacy interface implementation
> > mtd: rawnand: davinci: Change the {read,write}_buf prototypes
> >
> > drivers/mtd/nand/raw/davinci_nand.c | 161 +++++++++++++++-------------
> > 1 file changed, 85 insertions(+), 76 deletions(-)
> >
> > --
> > 2.25.3
> >
>
> Hi Boris,
>
> Thanks for doing this. Unfortunately this breaks NAND on da850-lcdk
> with the following error message:
>
> nand: No NAND device found
>
> I'm super busy this week and so I don't have the time to investigate
> further, I can get back to it next week hopefully.
No worries. And let me know if you need any help to debug that.
Thanks!
Boris
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-05-04 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 10:07 [PATCH 0/5] mtd: rawnand: davinci: Convert to exec_op() Boris Brezillon
2020-05-01 10:07 ` [PATCH 1/5] mtd: rawnand: davinci: Inherit from nand_controller Boris Brezillon
2020-05-10 21:35 ` Miquel Raynal
2020-05-01 10:07 ` [PATCH 2/5] mtd: rawnand: davinci: Stop using nand_chip.legacy.IO_ADDR_{R, W} Boris Brezillon
2020-05-10 21:37 ` [PATCH 2/5] mtd: rawnand: davinci: Stop using nand_chip.legacy.IO_ADDR_{R,W} Miquel Raynal
2020-05-01 10:07 ` [PATCH 3/5] mtd: rawnand: davinci: Implement exec_op() Boris Brezillon
2020-05-01 10:07 ` [PATCH 4/5] mtd: rawnand: davinci: Get rid of the legacy interface implementation Boris Brezillon
2020-05-10 21:38 ` Miquel Raynal
2020-05-01 10:07 ` [PATCH 5/5] mtd: rawnand: davinci: Change the {read, write}_buf prototypes Boris Brezillon
2020-05-10 21:39 ` [PATCH 5/5] mtd: rawnand: davinci: Change the {read,write}_buf prototypes Miquel Raynal
2020-05-04 16:34 ` [PATCH 0/5] mtd: rawnand: davinci: Convert to exec_op() Bartosz Golaszewski
2020-05-04 20:06 ` Boris Brezillon [this message]
2020-05-09 14:13 ` Boris Brezillon
2020-05-12 8:40 ` Bartosz Golaszewski
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=20200504220630.716d328f@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=bgolaszewski@baylibre.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=nsekhar@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--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).