From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Huang Shijie <b32955@freescale.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Gupta, Pekon" <pekon@ti.com>, "Balbi, Felipe" <balbi@ti.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] mtd: nand: auto-detection of NAND bus-width from ONFI param or nand_id[]
Date: Tue, 26 Nov 2013 09:45:45 -0300 [thread overview]
Message-ID: <20131126124544.GC2344@localhost> (raw)
In-Reply-To: <5294683B.6010704@freescale.com>
On Tue, Nov 26, 2013 at 05:22:03PM +0800, Huang Shijie wrote:
> (I am not sure whether we should remove the NAND_BUSWIDTH_AUTO, let
> Brian judge it)
>
Have you followed the past discussion around 16-bit ONFI detection
(currently broken, IIRC)?
We concluded that the auto-discovery (aka NAND_BUSWIDTH_AUTO) should be the default
behavior, since there's no other way to handle ONFI devices. Hence,
there's little point in keeping the macro.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-26 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 12:32 [PATCH] mtd: nand: auto-detection of NAND bus-width from ONFI param or nand_id[] Pekon Gupta
2013-11-25 12:56 ` Ezequiel Garcia
2013-11-25 13:26 ` Gupta, Pekon
2013-11-25 13:32 ` Gupta, Pekon
2013-11-25 14:52 ` Ezequiel Garcia
2013-11-26 7:59 ` Gupta, Pekon
2013-11-26 12:42 ` Ezequiel Garcia
2013-11-27 6:03 ` Gupta, Pekon
2013-11-26 7:31 ` Huang Shijie
2013-11-26 7:49 ` Gupta, Pekon
2013-11-26 9:22 ` Huang Shijie
2013-11-26 12:45 ` Ezequiel Garcia [this message]
2013-11-29 12:18 ` Ezequiel Garcia
2013-11-29 12:28 ` Gupta, Pekon
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=20131126124544.GC2344@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=b32955@freescale.com \
--cc=balbi@ti.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.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).