public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Guillaume LECERF <glecerf@gmail.com>
Cc: Matthias Buecher / Germany <mail@maddes.net>,
	linux-mtd@lists.infradead.org,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v4 1/2] mtd: cfi_cmdset_0002: add support for Samsung K8D6x16UxM NOR chips
Date: Tue, 14 Dec 2010 18:30:47 +0200	[thread overview]
Message-ID: <1292344247.2538.84.camel@localhost> (raw)
In-Reply-To: <20101209140410.26049.51539.stgit@dev.siriade.com>

On Thu, 2010-12-09 at 15:04 +0100, Guillaume LECERF wrote:
> These chips report CFI v0.0 [1], so extend cfi_fixup_major_minor()
> to patch all Samsung chips from 0.0 to 1.0.
> Discussed and tested by the OpenWRT people [2].
> 
> [1] http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/NORFlash/64Mbit/K8D6316UTM/ds_K8D6x16UxM_rev16.pdf
> [2] https://dev.openwrt.org/ticket/7348
> 
> Signed-off-by: Guillaume LECERF <glecerf@gmail.com>
> ---
>  drivers/mtd/chips/cfi_cmdset_0002.c |   14 +++++++++++---
>  1 files changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/mtd/chips/cfi_cmdset_0002.c b/drivers/mtd/chips/cfi_cmdset_0002.c
> index 9d68ab9..bf457a4 100644
> --- a/drivers/mtd/chips/cfi_cmdset_0002.c
> +++ b/drivers/mtd/chips/cfi_cmdset_0002.c
> @@ -392,9 +392,17 @@ static struct cfi_fixup fixup_table[] = {
>  static void cfi_fixup_major_minor(struct cfi_private *cfi,
>  				  struct cfi_pri_amdstd *extp)
>  {
> -	if (cfi->mfr == CFI_MFR_SAMSUNG && cfi->id == 0x257e &&
> -	    extp->MajorVersion == '0')
> -		extp->MajorVersion = '1';
> +	if (cfi->mfr == CFI_MFR_SAMSUNG) {
> +		if (extp->MajorVersion == '0' && extp->MinorVersion == '0') {
> +			/*
> +			 * Samsung K8P2815UQB and K8D6x16UxM chips report major=0 / minor=0
> +			 */
> +			printk(KERN_NOTICE "  Fixed Samsung's Amd/Fujitsu Extended Query version from 0.0 to 1.0\n");
> +
> +			extp->MajorVersion = '1';
> +		}

I'm sorry for this nit-pick, but could you please make checkpatch.pl
happy:

WARNING: line over 80 characters
#97: FILE: drivers/mtd/chips/cfi_cmdset_0002.c:398:
+                        * Samsung K8P2815UQB and K8D6x16UxM chips
report major=0 / minor=0

Also, I do not see any reason for a newline between printk() and
extp->MajorVersion = '1' - it only makes code unnecessary sparse.
Newlines ar good between logically independent things, but not between 2
things which are about the same - print about X and then do X.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      parent reply	other threads:[~2010-12-14 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 14:04 [PATCH v4 1/2] mtd: cfi_cmdset_0002: add support for Samsung K8D6x16UxM NOR chips Guillaume LECERF
2010-12-09 14:04 ` [PATCH v4 2/2] mtd: cfi_cmdset_0002: add support for Samsung K8D3x16UxC " Guillaume LECERF
2010-12-14 16:31   ` Artem Bityutskiy
2010-12-09 14:30 ` [PATCH v4 1/2] mtd: cfi_cmdset_0002: add support for Samsung K8D6x16UxM " Wolfram Sang
2010-12-14 16:30 ` Artem Bityutskiy [this message]

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=1292344247.2538.84.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=glecerf@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mail@maddes.net \
    /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