public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: David Mosberger <davidm@egauge.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd: nand: fix GET/SET_FEATURES address on 16-bit devices
Date: Fri, 21 Mar 2014 17:20:07 -0700	[thread overview]
Message-ID: <20140322002007.GA29542@ld-irv-0074> (raw)
In-Reply-To: <1395439510-18860-1-git-send-email-davidm@egauge.net>

Hi David,

(BTW, it's nice if $SUBJECT begins with the text '[PATCH]'. I actually
filter mail based on this!)

On Fri, Mar 21, 2014 at 04:05:10PM -0600, David Mosberger wrote:
> linux-next almost works out of the box for us except that GET_FEATURES
> and SET_FEATURES also need byte-addressing.

Thanks a lot for testing linux-next for this! Our recent fixes for x16
buswidths really haven't gotten wide testing.

> With the attached patch,
> our board boots fine (save for on-die ECC patch, which I'll submit
> separately).  The only oddity is that the devices is reported as being
> SLC, when it's most definitely not:
> 
> nand: 512MiB, SLC, page size: 2048, OOB size: 64

Hmm. What's the part number + vendor? (And the ID bytes, if possible?)

>    --david
> 
> 
> 
> GET_FEATURES and SET_FEATURES also need byte-addressing on 16-bit devices.
> 
> Signed-off-by: David Mosberger <davidm@egauge.net>
> 
> diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
> index 0747fef..29a23bb 100644
> --- a/include/linux/mtd/nand.h
> +++ b/include/linux/mtd/nand.h
> @@ -925,7 +929,16 @@ static inline bool nand_is_slc(struct nand_chip *chip)
>   */
>  static inline int nand_opcode_8bits(unsigned int command)
>  {
> -	return command == NAND_CMD_READID || command == NAND_CMD_PARAM;
> +	switch (command) {
> +	case NAND_CMD_READID:
> +	case NAND_CMD_PARAM:
> +	case NAND_CMD_GET_FEATURES:
> +	case NAND_CMD_SET_FEATURES:
> +		return 1;
> +	default:
> +		break;
> +	}
> +	return 0;
>  }
>  
>  /* return the supported JEDEC features. */
> 

Patch looks good. I'll come back to this to test and apply for 3.15, I
hope (feel free to bug me if I don't reply back by 3.15-rc1). But:

Acked-by: Brian Norris <computersforpeace@gmail.com>

Brian

  reply	other threads:[~2014-03-22  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 22:05 mtd: nand: fix GET/SET_FEATURES address on 16-bit devices David Mosberger
2014-03-22  0:20 ` Brian Norris [this message]
2014-03-26  6:33 ` Brian Norris

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=20140322002007.GA29542@ld-irv-0074 \
    --to=computersforpeace@gmail.com \
    --cc=davidm@egauge.net \
    --cc=linux-mtd@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