From: Roger Quadros <rogerq@kernel.org>
To: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com
Cc: kishon@ti.com, nm@ti.com, tony@atomide.com,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Roger Quadros <rogerq@kernel.org>
Subject: [PATCH 0/4] mtd: nand: omap2: Switch to exec_ops, support AM64 SoC
Date: Tue, 23 Nov 2021 12:36:05 +0200 [thread overview]
Message-ID: <20211123103609.14063-1-rogerq@kernel.org> (raw)
Hi,
This series gets rid of the Legacy ops and switches to exec_ops framework.
Also add driver support for TI's AM64 SoC which contains a GPMC NAND controller.
cheers,
-roger
Roger Quadros (4):
dt-bindings: mtd: ti,gpmc-nand: Add compatible for AM64 NAND
mtd: nand: omap2: Allow build on K3 platforms
mtd: nand: omap2: move to exec_op interface
mtd: nand: omap2: Add support for NAND Controller on AM64 SoC
.../devicetree/bindings/mtd/ti,gpmc-nand.yaml | 5 +-
drivers/mtd/nand/raw/Kconfig | 2 +-
drivers/mtd/nand/raw/omap2.c | 525 ++++++++----------
3 files changed, 251 insertions(+), 281 deletions(-)
--
2.17.1
next reply other threads:[~2021-11-23 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 10:36 Roger Quadros [this message]
2021-11-23 10:36 ` [PATCH 1/4] dt-bindings: mtd: ti,gpmc-nand: Add compatible for AM64 NAND Roger Quadros
2021-11-30 22:02 ` Rob Herring
2021-11-23 10:36 ` [PATCH 2/4] mtd: nand: omap2: Allow build on K3 platforms Roger Quadros
2021-11-23 10:36 ` [PATCH 3/4] mtd: nand: omap2: move to exec_op interface Roger Quadros
2021-11-23 10:36 ` [PATCH 4/4] mtd: nand: omap2: Add support for NAND Controller on AM64 SoC Roger Quadros
2021-11-24 12:15 ` Miquel Raynal
2021-11-25 14:12 ` Roger Quadros
2021-11-26 9:42 ` Miquel Raynal
2021-11-26 11:10 ` Roger Quadros
2021-11-29 4:36 ` Nishanth Menon
2021-12-08 14:45 ` Roger Quadros
2021-12-08 16:35 ` Nishanth Menon
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=20211123103609.14063-1-rogerq@kernel.org \
--to=rogerq@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=nm@ti.com \
--cc=richard@nod.at \
--cc=tony@atomide.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