From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] Update ts72xx to use generic platform nand driver
Date: Wed, 7 Oct 2009 09:16:19 +0100 [thread overview]
Message-ID: <jbvtp6-i58.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: BD79186B4FD85F4B8E60E381CAEE190901DB7967@mi8nycmail19.Mi8.com
Hi,
In gmane.linux.drivers.mtd H Hartley Sweeten <hartleys@visionengravers.com> wrote:
>
> Update the ts72xx platform's nand driver support.
>
> This changes the ts72xx platform from using a custom nand driver
> (ts7250.c) to the generic platform nand driver (plat_nand.c).
>
> Tested on TS-7250 with 32MB NAND.
>
> [snipped]
>
> +static const char *ts72xx_nand_part_probes[] = { "cmdlinepart", NULL };
> +
> +#define TS72XX_BOOTROM_PART_SIZE (SZ_16K)
> +#define TS72XX_REDBOOT_PART_SIZE (SZ_2M + SZ_1M)
> +
> +static struct mtd_partition ts72xx_part_info32[] = {
> {
> - .virtual = TS72XX_NAND_DATA_VIRT_BASE,
> - .pfn = __phys_to_pfn(TS72XX_NAND1_DATA_PHYS_BASE),
> - .length = TS72XX_NAND_DATA_SIZE,
> - .type = MT_DEVICE,
> + .name = "TS-BOOTROM",
> + .offset = 0,
> + .size = TS72XX_BOOTROM_PART_SIZE,
> }, {
> - .virtual = TS72XX_NAND_CONTROL_VIRT_BASE,
> - .pfn = __phys_to_pfn(TS72XX_NAND1_CONTROL_PHYS_BASE),
> - .length = TS72XX_NAND_CONTROL_SIZE,
> - .type = MT_DEVICE,
> + .name = "Linux",
> + .offset = MTDPART_OFS_APPEND,
> + .size = SZ_32M - TS72XX_REDBOOT_PART_SIZE,
> }, {
> - .virtual = TS72XX_NAND_BUSY_VIRT_BASE,
> - .pfn = __phys_to_pfn(TS72XX_NAND1_BUSY_PHYS_BASE),
> - .length = TS72XX_NAND_BUSY_SIZE,
> - .type = MT_DEVICE,
> - }
> + .name = "RedBoot",
> + .offset = MTDPART_OFS_APPEND,
> + .size = MTDPART_SIZ_FULL,
> + },
> };
>
> -static struct map_desc ts72xx_alternate_nand_io_desc[] __initdata = {
> +static struct mtd_partition ts72xx_part_info128[] = {
> {
> - .virtual = TS72XX_NAND_DATA_VIRT_BASE,
> - .pfn = __phys_to_pfn(TS72XX_NAND2_DATA_PHYS_BASE),
> - .length = TS72XX_NAND_DATA_SIZE,
> - .type = MT_DEVICE,
> + .name = "TS-BOOTROM",
> + .offset = 0,
> + .size = TS72XX_BOOTROM_PART_SIZE,
> }, {
> - .virtual = TS72XX_NAND_CONTROL_VIRT_BASE,
> - .pfn = __phys_to_pfn(TS72XX_NAND2_CONTROL_PHYS_BASE),
> - .length = TS72XX_NAND_CONTROL_SIZE,
> - .type = MT_DEVICE,
> + .name = "Linux",
> + .offset = MTDPART_OFS_APPEND,
> + .size = SZ_128M - TS72XX_REDBOOT_PART_SIZE,
> }, {
> - .virtual = TS72XX_NAND_BUSY_VIRT_BASE,
> - .pfn = __phys_to_pfn(TS72XX_NAND2_BUSY_PHYS_BASE),
> - .length = TS72XX_NAND_BUSY_SIZE,
> - .type = MT_DEVICE,
> - }
> + .name = "RedBoot",
> + .offset = MTDPART_OFS_APPEND,
> + .size = MTDPART_SIZ_FULL,
> + },
> };
>
These struct's are almost identical so could you not...
> -static void __init ts72xx_map_io(void)
> +static void ts72xx_nand_set_parts(uint64_t size,
> + struct platform_nand_chip *chip)
> {
> - ep93xx_map_io();
> - iotable_init(ts72xx_io_desc, ARRAY_SIZE(ts72xx_io_desc));
> -
> - /*
> - * The TS-7200 has NOR flash, the other models have NAND flash.
> - */
> - if (!board_is_ts7200()) {
> - if (is_ts9420_installed()) {
> - iotable_init(ts72xx_alternate_nand_io_desc,
> - ARRAY_SIZE(ts72xx_alternate_nand_io_desc));
> - } else {
> - iotable_init(ts72xx_nand_io_desc,
> - ARRAY_SIZE(ts72xx_nand_io_desc));
> - }
> + switch (size) {
> + case SZ_32M:
> + chip->partitions = ts72xx_part_info32;
> + chip->nr_partitions = ARRAY_SIZE(ts72xx_part_info32);
> + break;
> + case SZ_128M:
> + chip->partitions = ts72xx_part_info128;
> + chip->nr_partitions = ARRAY_SIZE(ts72xx_part_info128);
> + break;
> + default:
> + pr_warning("ts72xx: Unknown nand disk size:%lluMB\n", size >> 20);
> + break;
> }
> }
>
-----------
static struct mtd_partition ts72xx_part_info[] = {
{
/* gut feeling for *Joe Public* is to go MTD_WRITABLE */
.name = "TS-BOOTROM",
.offset = 0,
.size = TS72XX_BOOTROM_PART_SIZE,
}, {
.name = "Linux",
.offset = MTDPART_OFS_APPEND,
/* to be filled in later */
.size = 0,
}, {
/* mask MTD_WRITABLE here too? */
.name = "Redboot",
.offset = MTDPART_OFS_APPEND,
.size = MTDPART_SIZ_FULL,
}
};
static void ts72xx_nand_set_parts(....)
{
....
/* or I guess you could just bailout... */
if (size != SZ_32M && size != SZ_128M)
pr_warning("ts72xx: Unknown nand disk size:%lluMB\n", size >> 20);
chip->partitions = ts72xx_part_info;
chip->nr_partitions = ARRAY_SIZE(ts72xx_part_info);
ts72xx_part_info[1].size = size - TS72XX_REDBOOT_PART_SIZE;
}
---------
Cheers
--
Alexander Clouter
.sigmonster says: Life's too short to dance with ugly women.
next prev parent reply other threads:[~2009-10-07 8:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 22:19 [PATCH 1/2] Update ts72xx to use generic platform nand driver H Hartley Sweeten
2009-10-07 8:16 ` Alexander Clouter [this message]
2009-10-07 17:09 ` H Hartley Sweeten
2009-10-07 17:31 ` H Hartley Sweeten
2009-10-11 11:30 ` Artem Bityutskiy
2009-10-11 21:11 ` H Hartley Sweeten
2009-10-11 21:19 ` H Hartley Sweeten
2009-10-14 8:42 ` Artem Bityutskiy
2009-10-14 17:05 ` H Hartley Sweeten
2009-10-16 6:38 ` Artem Bityutskiy
2009-10-16 17:09 ` H Hartley Sweeten
2009-10-16 17:20 ` David Woodhouse
2009-10-16 17:32 ` H Hartley Sweeten
2009-10-16 17:36 ` David Woodhouse
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=jbvtp6-i58.ln1@chipmunk.wormnet.eu \
--to=alex@digriz.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).