From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v1, 3/3] ARM: omap: merge GPMC initialization code for all platform
Date: Fri, 23 May 2014 19:52:05 -0400 [thread overview]
Message-ID: <20140523235205.GW1752@bill-the-cat> (raw)
In-Reply-To: <1399565627-27770-4-git-send-email-pekon@ti.com>
On Thu, May 08, 2014 at 09:43:47PM +0530, pekon gupta wrote:
> GPMC controller on TI's OMAP SoC is general purpose controller to interface
> with different types of external devices like;
> - parallel NOR flash
> - parallel NAND flash
> - OneNand flash
> - SDR RAM
> - Ethernet Devices like LAN9220
>
> Though GPMC configurations may be different for each platform depending on
> clock-frequency and external device interfacing with controller. But
> initialization sequence remains common across all platfoms.
>
> Thus this patch merges gpmc_init() scattered in different arch-xx/mem.c
> files into single omap-common/mem-common.c
>
> However, actual platforms specific register config values are still sourced
> from corresponding platform specific headers like;
> AM33xx: arch/arm/include/asm/arch-am33xx/mem.h
> OMAP3: arch/arm/include/asm/arch-omap3/mem.h
> OMAP4: arch/arm/include/asm/arch-omap4/mem.h
> OMAP4: arch/arm/include/asm/arch-omap5/mem.h
>
> Also, CONFIG_xx passed by board-profile decide config for which set of macros
> need to be used for initialization
> CONFIG_NAND: initialize GPMC for NAND device
> CONFIG_NOR: initialize GPMC for NOR device
> CONFIG_ONENAND: initialize GPMC for ONENAND device
>
> Signed-off-by: Pekon Gupta <pekon@ti.com>
After adding GPMC_SIZE_256M to omap3/mem.h, applied to u-boot-ti/master,
thanks!
And note that git detect renames got a bit too agressive here so I had
to apply it kinda by hand, but I think I did everything right.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140523/c80fd16f/attachment.pgp>
next prev parent reply other threads:[~2014-05-23 23:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 16:13 [U-Boot] [PATCH v1 0/3] ARM: omap: add support for GPMC and ELM controllers on OMAP4 and OMAP5 platforms Pekon Gupta
2014-05-08 16:13 ` [U-Boot] [PATCH v1 1/3] ARM: omap4: add platform specific info for GPMC and ELM controllers Pekon Gupta
2014-05-23 23:49 ` [U-Boot] [U-Boot, v1, " Tom Rini
2014-05-08 16:13 ` [U-Boot] [PATCH v1 2/3] ARM: omap5: " Pekon Gupta
2014-05-23 23:49 ` [U-Boot] [U-Boot, v1, " Tom Rini
2014-05-08 16:13 ` [U-Boot] [PATCH v1 3/3] ARM: omap: merge GPMC initialization code for all platform Pekon Gupta
2014-05-23 23:52 ` Tom Rini [this message]
2014-05-27 4:47 ` [U-Boot] [U-Boot, v1, " Gupta, Pekon
2014-05-30 21:59 ` Ash Charles
2014-06-06 18:27 ` [U-Boot] [PATCH] omap: Don't enable GPMC CS0 with nothing attached Ash Charles
2014-06-19 22:01 ` [U-Boot] " Tom Rini
2014-06-19 22:02 ` Ash Charles
2014-07-08 6:19 ` [U-Boot] [U-Boot, v1, 3/3] ARM: omap: merge GPMC initialization code for all platform Gupta, Pekon
2014-07-08 23:49 ` Ash Charles
2014-07-09 18:16 ` Gupta, Pekon
2014-05-08 18:00 ` [U-Boot] [PATCH v1 0/3] ARM: omap: add support for GPMC and ELM controllers on OMAP4 and OMAP5 platforms Gupta, Pekon
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=20140523235205.GW1752@bill-the-cat \
--to=trini@ti.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