From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] [OneNAND] Flex-OneNAND driver support
Date: Thu, 5 Nov 2009 16:59:06 -0600 [thread overview]
Message-ID: <20091105225906.GA13402@loki.buserror.net> (raw)
In-Reply-To: <ACCABDCF2D504FED9D44EF0EB29228FD@sisodomain.com>
On Wed, Nov 04, 2009 at 10:37:17AM +0530, Amul Kumar Saha wrote:
> This patch adds support for Flex-OneNAND devices.
>
> Signed-off-by: Rohit Hagargundgi <h.rohit@samsung.com>
> Signed-off-by: Amul Kumar Saha <amul.saha@samsung.com>
A couple 64-bit offset nits...
> +static void flexonenand_get_size(struct mtd_info *mtd)
> +{
> + struct onenand_chip *this = mtd->priv;
> + int die, ofs, i, eraseshift, density;
[snip]
> + for (; die < this->dies; die++) {
> + if (!die || this->boundary[die-1] != maxbdry) {
> + i++;
> + mtd->eraseregions[i].offset = ofs;
> + mtd->eraseregions[i].erasesize = 1 << eraseshift;
> + mtd->eraseregions[i].numblocks =
> + this->boundary[die] + 1;
> + ofs += mtd->eraseregions[i].numblocks << eraseshift;
"ofs" should be loff_t.
> + printk(KERN_INFO "Device has %d eraseregions\n", mtd->numeraseregions);
> + for (i = 0; i < mtd->numeraseregions; i++)
> + printk(KERN_INFO "[offset: 0x%08x, erasesize: 0x%05x,"
> + " numblocks: %04u]\n", mtd->eraseregions[i].offset,
> + mtd->eraseregions[i].erasesize,
> + mtd->eraseregions[i].numblocks);
offset is uint64_t, so use %08llx. This gives a warning...
If you want, I can just fix these up -- but give it a retest afterward.
-Scott
next prev parent reply other threads:[~2009-11-05 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 6:13 [U-Boot] [PATCH 1/3] [OneNAND] Flex-OneNAND driver support Amul Kumar Saha
2009-09-28 20:02 ` Scott Wood
2009-11-04 5:00 ` Amul Kumar Saha
2009-11-04 12:54 ` Kyungmin Park
2009-11-04 5:07 ` Amul Kumar Saha
2009-11-05 22:59 ` Scott Wood [this message]
2009-11-06 11:42 ` Amul Kumar Saha
2009-11-06 11:45 ` Amul Kumar Saha
2009-11-09 20:05 ` Scott Wood
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=20091105225906.GA13402@loki.buserror.net \
--to=scottwood@freescale.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