From: Christopher Harvey <charvey@matrox.com>
To: linux-omap@vger.kernel.org
Cc: linux-mtd@lists.infradead.org
Subject: [PATCH v2] 16 bit NAND fix, request for testers
Date: Fri, 26 Oct 2012 15:34:10 -0400 [thread overview]
Message-ID: <20121026193410.GA21474@harvey-pc.matrox.com> (raw)
just a small patch to access GPMC NAND registers with 16 bits when the
NAND is in 16 bit mode. I tested this on a 2.6.37 kernel, and noticed
it was still unpatched in the latest kernel. I don't have the hardware
setup or defconfigs to test this patch out, and even if I did I don't
have the logic analyzer setup to completely reproduce it on other
hardware with the latest kernel. It would be nice to get a tested-by
on this patch.
(CC'd mtd list this time)
Thanks.
Christopher Harvey (1):
mtd: omap: nand: Remove 0xFF's that prefixed 16bit NAND commands
drivers/mtd/nand/omap2.c | 14 +++++++++-----
1 files changed, 9 insertions(+), 5 deletions(-)
--
1.7.8.6
next reply other threads:[~2012-10-26 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 19:34 Christopher Harvey [this message]
2012-10-26 19:36 ` [PATCH v2] mtd: omap: nand: Remove 0xFF's that prefixed 16bit NAND commands Christopher Harvey
2012-10-29 13:49 ` Ivan Djelic
2012-10-29 17:04 ` Christopher Harvey
2012-10-29 19:51 ` [PATCH v3] mtd: omap: nand: Remove 0xFF's that prefixed 16bit NAND addresses Christopher Harvey
2012-10-29 19:51 ` Christopher Harvey
2012-11-15 11:02 ` Artem Bityutskiy
2012-11-15 11:02 ` Artem Bityutskiy
2012-11-15 14:48 ` Christopher Harvey
2012-11-15 14:48 ` Christopher Harvey
2012-11-15 15:18 ` Artem Bityutskiy
2012-11-15 15:18 ` Artem Bityutskiy
2012-11-15 15:38 ` Christopher Harvey
2012-11-15 15:38 ` Christopher Harvey
2012-11-15 16:29 ` Ivan Djelic
2012-11-15 16:29 ` Ivan Djelic
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=20121026193410.GA21474@harvey-pc.matrox.com \
--to=charvey@matrox.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.