From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 4/7] board/ti/am335x: add support for beaglebone NOR Cape
Date: Wed, 16 Jul 2014 16:06:54 -0400 [thread overview]
Message-ID: <20140716200654.GO1847@bill-the-cat> (raw)
In-Reply-To: <1404500717-775-5-git-send-email-pekon@ti.com>
On Sat, Jul 05, 2014 at 12:35:14AM +0530, Pekon Gupta wrote:
> This patch updates pin-mux for beaglebone NOR cape [1]
> This cape has 128Mbits(16MBytes), x16, CFI compatible NOR Flash device.
>
> On Beaglebone, GPMC chip-select-0 is shared by both NAND and NOR capes,
> so only one of them can be enabled at a time from board profile configs.
>
> [1] http://elinux.org/Beagleboardtoys:BeagleBone_128Mb_16-Bit_NOR_Module
[snip]
> @@ -200,73 +200,46 @@ static struct module_pin_mux nand_pin_mux[] = {
> {OFFSET(gpmc_be0n_cle), (MODE(0) | PULLDOWN_EN)}, /* BE_CLE */
> {-1},
> };
> -#endif
> -#if defined(CONFIG_NOR) && !defined(CONFIG_NOR_BOOT)
> +#elif defined(CONFIG_NOR)
> static struct module_pin_mux bone_norcape_pin_mux[] = {
> - {OFFSET(lcd_data0), MODE(1) | PULLUDEN | RXACTIVE}, /* NOR_A0 */
It _looks_ like this is jsut whitespace only. Since that doesn't match
the rest of the file, please don't do that.
[snip]
> #endif
>
> #if defined(CONFIG_NOR_BOOT)
> -static struct module_pin_mux norboot_pin_mux[] = {
> - {OFFSET(lcd_data1), MODE(1) | PULLUDDIS},
> - {OFFSET(lcd_data2), MODE(1) | PULLUDDIS},
> - {OFFSET(lcd_data3), MODE(1) | PULLUDDIS},
> - {OFFSET(lcd_data4), MODE(1) | PULLUDDIS},
> - {OFFSET(lcd_data5), MODE(1) | PULLUDDIS},
> - {OFFSET(lcd_data6), MODE(1) | PULLUDDIS},
> - {OFFSET(lcd_data7), MODE(1) | PULLUDDIS},
> - {OFFSET(lcd_data8), MODE(1) | PULLUDDIS},
> - {OFFSET(lcd_data9), MODE(1) | PULLUDDIS},
> - {-1},
> -};
> -
> void enable_norboot_pin_mux(void)
> {
> - configure_module_pin_mux(norboot_pin_mux);
> + configure_module_pin_mux(bone_norcape_pin_mux);
Did you boot test this? The system requirements here are a bit strict
and I don't know if we can just do what you're doing here...
--
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/20140716/9fbcb2ab/attachment.pgp>
next prev parent reply other threads:[~2014-07-16 20:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 19:05 [U-Boot] [PATCH v1 0/7] TI: armv7: add parallel NAND support Pekon Gupta
2014-07-04 19:05 ` [U-Boot] [PATCH v1 1/7] TI: armv7: move board specific NAND configs out from ti_armv7_common.h and ti_am335x_common.h Pekon Gupta
2014-07-14 21:30 ` Tom Rini
2014-07-04 19:05 ` [U-Boot] [PATCH v1 2/7] board/ti/am335x: add support for beaglebone NAND cape Pekon Gupta
2014-07-16 20:02 ` Tom Rini
2014-07-21 6:12 ` Gupta, Pekon
2014-07-04 19:05 ` [U-Boot] [PATCH v1 3/7] arm: lib: continue board_init_r even if valid flash device is not detected Pekon Gupta
2014-07-16 20:07 ` Tom Rini
2014-07-04 19:05 ` [U-Boot] [PATCH v1 4/7] board/ti/am335x: add support for beaglebone NOR Cape Pekon Gupta
2014-07-16 20:06 ` Tom Rini [this message]
2014-07-21 10:27 ` Gupta, Pekon
2014-07-04 19:05 ` [U-Boot] [PATCH v1 5/7] board/ti/am335x: update configs for parallel NAND Pekon Gupta
2014-07-04 19:05 ` [U-Boot] [PATCH v1 6/7] board/ti/am43xx: add support " Pekon Gupta
2014-07-16 20:14 ` Tom Rini
2014-07-04 19:05 ` [U-Boot] [PATCH v1 7/7] board/ti/dra7xx: " Pekon Gupta
2014-07-16 20:20 ` Tom Rini
2014-07-17 10:59 ` Gupta, Pekon
2014-07-17 12:57 ` Tom Rini
2014-07-06 7:35 ` [U-Boot] [PATCH v1 0/7] TI: armv7: add parallel NAND support Igor Grinberg
2014-07-07 6:35 ` 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=20140716200654.GO1847@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