Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: David Mosberger <davidm@egauge.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: fix byte addressing on 16-bit wide devices
Date: Fri, 21 Mar 2014 15:05:47 -0300	[thread overview]
Message-ID: <20140321180547.GA11793@arch.cereza> (raw)
In-Reply-To: <CALnQHM3PJCzB86S65TmKE14_HY7DxwVgtXAOcphrGcCJ4t24GQ@mail.gmail.com>

Hi David,

On Mar 21, David Mosberger wrote:
> This is a revised version of a patch that I submitted a while ago.
> It's relative to linux-mtd.
> Please apply.
> 
> Thanks!
> 
>   --david
> -- 
> eGauge Systems LLC, http://egauge.net/, 1.877-EGAUGE1, fax 720.545.9768

> mtd: nand: fix byte adressing on 16-bit wide devices
> 
> Some commands (READID, GET_FEATURES, and SET_FEATURES) require
> byte-addresses even when the databus is 16 bits wide.  Without this
> patch, 16-bit wide devices are unable to detect ONFI.
> 

I haven't looked at your patch, but I think this is already fixed.
You can take a look at these commits:

bd9c6e99b58255b9de1982711ac9487c9a2f18be
3dad2344e92c6e1aeae42df1c4824f307c51bcc7

AFAIK, the READID command data is now issued as 8-bit, disregarding of
NAND_BUSWIDTH_16.

Maybe you can re-test this building a kernel from linux-next.git and
report if your issues are now fixed?

Thanks!
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2014-03-21 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 17:42 [PATCH] mtd: nand: fix byte addressing on 16-bit wide devices David Mosberger
2014-03-21 18:05 ` Ezequiel Garcia [this message]
     [not found]   ` <CACwUX0PQP21PuSbQn6AvisaZuug9=JTwM3QoG5mXy54r6-tXCg@mail.gmail.com>
2014-03-21 18:19     ` Fwd: " David Mosberger-Tang
2014-03-21 18:54     ` Ezequiel Garcia
2014-03-21 19:43       ` David Mosberger
2014-03-22  2:01         ` Brian Norris
2014-03-22  1:59       ` 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=20140321180547.GA11793@arch.cereza \
    --to=ezequiel.garcia@free-electrons.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