From: Tom Rini <trini@konsulko.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: u-boot@lists.denx.de
Subject: Re: [u-boot][PATCH 0/3] Introduce TI GPMC memory controller driver
Date: Fri, 30 Sep 2022 08:44:33 -0400 [thread overview]
Message-ID: <20220930124433.GP3044094@bill-the-cat> (raw)
In-Reply-To: <a1b8f793-ea82-50f2-3d86-fbf73b63c045@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
On Fri, Sep 30, 2022 at 03:42:42PM +0300, Roger Quadros wrote:
> Hi Tom,
>
> On 29/09/2022 20:51, Tom Rini wrote:
> > On Wed, Sep 28, 2022 at 03:11:46PM +0300, Roger Quadros wrote:
> >
> >> Hi,
> >>
> >> The GPMC is a unified memory controller dedicated for interfacing
> >> with external memory devices like
> >> - Asynchronous SRAM-like memories and ASICs
> >> - Asynchronous, synchronous, and page mode burst NOR flash
> >> - NAND flash
> >> - Pseudo-SRAM devices
> >>
> >> This driver will take care of setting up the GPMC based on
> >> the settings specified in the Device tree and then
> >> probe its children.
> >
> > Does this mean we'll be seeing some updates to (or removal of) the
> > existing nand/gpmc code under arch/arm/mach-omap2 ?
> >
>
> My initial plan was to get AM64 NAND to work without requiring
> any arch specific code.
> This should eventually be usable for mach-omap2 as well.
>
> We can then get rid of /arch/arm/mach-omap2/mem-common.c
>
> I have an omap3-beagle with NAND support with me so I could at least
> get it working on that board.
>
> It should be pretty much the same for all mach-omap2 boards.
Sounds good, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-09-30 12:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 12:11 [u-boot][PATCH 0/3] Introduce TI GPMC memory controller driver Roger Quadros
2022-09-28 12:11 ` [u-boot][PATCH 1/3] scripts: Makefile.spl: Enable memory drivers to be built for SPL Roger Quadros
2022-09-28 16:27 ` Simon Glass
2022-09-29 7:02 ` Roger Quadros
2022-09-29 17:51 ` Tom Rini
2022-09-29 18:06 ` Simon Glass
2022-09-30 12:47 ` Roger Quadros
2022-09-30 13:28 ` Simon Glass
2022-09-30 14:00 ` Tom Rini
2022-09-30 20:17 ` Roger Quadros
2022-09-30 23:48 ` Simon Glass
2022-10-01 8:37 ` Roger Quadros
2022-10-03 1:10 ` Simon Glass
2022-09-28 12:11 ` [u-boot][PATCH 2/3] dt/bindings: memory: Add bindings for TI GPMC driver Roger Quadros
2022-09-28 12:11 ` [u-boot][PATCH 3/3] memory: Add " Roger Quadros
2022-09-29 17:51 ` [u-boot][PATCH 0/3] Introduce TI GPMC memory controller driver Tom Rini
2022-09-30 12:42 ` Roger Quadros
2022-09-30 12:44 ` Tom Rini [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=20220930124433.GP3044094@bill-the-cat \
--to=trini@konsulko.com \
--cc=rogerq@kernel.org \
--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