From: Artem Bityutskiy <dedekind1@gmail.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Matthieu CASTET <matthieu.castet@parrot.com>,
Brian Norris <norris@broadcom.com>,
Maxime Bizon <mbizon@freebox.fr>
Subject: Re: [PATCH 3/3 v3] NAND: add support for reading ONFI parameters from NAND device
Date: Tue, 31 Aug 2010 14:46:59 +0300 [thread overview]
Message-ID: <1283255219.2018.35.camel@brekeke> (raw)
In-Reply-To: <201008301832.24672.florian@openwrt.org>
Hi,
I've added these to my l2-mtd-2.6 / dunno tree, but I have a comment: is
it possible/feasible to make the below block to be a separate function.
It is quite large, and difficult to read when it is embedded into the
function. Also, the indentation becomes more difficult because of too
much nesting.
Also, some stylistic nit-picks below.
On Mon, 2010-08-30 at 18:32 +0200, Florian Fainelli wrote:
> + /* try ONFI for unknow chip or LP */
> + chip->cmdfunc(mtd, NAND_CMD_READID, 0x20, -1);
> + if (chip->read_byte(mtd) == 'O' &&
> + chip->read_byte(mtd) == 'N' &&
> + chip->read_byte(mtd) == 'F' &&
> + chip->read_byte(mtd) == 'I') {
> +
> + struct nand_onfi_params *p = &chip->onfi_params;
> + int i;
> +
> + printk(KERN_INFO "ONFI flash detected\n");
> + chip->cmdfunc(mtd, NAND_CMD_PARAM, 0, -1);
> + for (i = 0; i < 3; i++) {
> + chip->read_buf(mtd, (uint8_t *)p, sizeof(*p));
> + if (onfi_crc16(ONFI_CRC_BASE, (uint8_t *)p, 254) ==
> + le16_to_cpu(p->crc))
> + {
> + printk(KERN_INFO "ONFI param page %d valid\n", i);
> + break;
> + }
I think { should me on the same line as if. Moving to a separate func
will help. Also, check the patch with scripts/checkpatch.pl.
> + }
> +
> + if (i < 3) {
> + /* check version */
> + int val = le16_to_cpu(p->revision);
> + if (val == 1 || val > (1 << 4))
> + printk(KERN_INFO "%s: unsupported ONFI version: %d\n",
> + __func__, val);
> + else {
> + if (val & (1 << 4))
> + chip->onfi_version = 22;
> + else if (val & (1 << 3))
> + chip->onfi_version = 21;
> + else if (val & (1 << 2))
> + chip->onfi_version = 20;
> + else
> + chip->onfi_version = 10;
> + }
> + }
> +
> + if (chip->onfi_version) {
> + sanitize_string(p->manufacturer, sizeof(p->manufacturer));
> + sanitize_string(p->model, sizeof(p->model));
> + if (!mtd->name)
> + mtd->name = p->model;
> + mtd->writesize = le32_to_cpu(p->byte_per_page);
> + mtd->erasesize = le32_to_cpu(p->pages_per_block)*mtd->writesize;
> + mtd->oobsize = le16_to_cpu(p->spare_bytes_per_page);
> + chip->chipsize = le32_to_cpu(p->blocks_per_lun) * mtd->erasesize;
You have whitespaces around '*' here, but 2 lines before you did not
have.
> + busw = 0;
> + if (le16_to_cpu(p->features) & 1)
> + busw = NAND_BUSWIDTH_16;
> +
> + chip->options &= ~NAND_CHIPOPTIONS_MSK;
> + chip->options |= (NAND_NO_READRDY |
> + NAND_NO_AUTOINCR) & NAND_CHIPOPTIONS_MSK;
> +
> + goto ident_done;
> +
> + }
> + }
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-08-31 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 16:32 [PATCH 3/3 v3] NAND: add support for reading ONFI parameters from NAND device Florian Fainelli
2010-08-31 11:46 ` Artem Bityutskiy [this message]
2010-08-31 12:02 ` Florian Fainelli
2010-10-21 16:52 ` Matthieu CASTET
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=1283255219.2018.35.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=florian@openwrt.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.com \
--cc=mbizon@freebox.fr \
--cc=norris@broadcom.com \
/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).