From: Jan Weitzel <j.weitzel@phytec.de>
To: linux-mtd@lists.infradead.org
Cc: dedekind@infradead.org, Jan Weitzel <j.weitzel@phytec.de>,
tglx@linutronix.de, computersforpeace@gmail.com,
linux-omap@vger.kernel.org
Subject: [PATCH] mdt nand: omap2+ use platform options
Date: Tue, 29 Nov 2011 10:00:13 +0100 [thread overview]
Message-ID: <1322557213-23565-1-git-send-email-j.weitzel@phytec.de> (raw)
In-Reply-To: <CAN8TOE9=ux=suwcQMwJY1XUhp_mnD_DL613ffF1-HTL1OVB2PQ@mail.gmail.com>
Options from struct omap_nand_platform_data are not used.
Apply options after nand_scan_ident to avoid overwrite due to
NAND_CHIPOPTIONS_MSK.
So you can pass options from platformcode
Signed-off-by: Jan Weitzel <j.weitzel@phytec.de>
---
drivers/mtd/nand/omap2.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index f745f00..7de4c0e 100644
--- a/drivers/mtd/nand/omap2.c
+++ b/drivers/mtd/nand/omap2.c
@@ -1075,6 +1075,8 @@ static int __devinit omap_nand_probe(struct platform_device *pdev)
}
}
+ info->nand.options |= pdata->options;
+
/* rom code layout */
if (pdata->ecc_opt == OMAP_ECC_HAMMING_CODE_HW_ROMCODE) {
--
1.7.0.4
next prev parent reply other threads:[~2011-11-29 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 14:20 [RFC] mtd/nand: modify NAND_CHIPOPTIONS_MSK Jan Weitzel
2011-11-28 18:34 ` Brian Norris
2011-11-29 9:00 ` Jan Weitzel [this message]
2011-11-30 20:31 ` [PATCH] mdt nand: omap2+ use platform options Brian Norris
2011-12-01 8:21 ` Jan Weitzel
2011-12-01 8:42 ` Artem Bityutskiy
2011-12-02 10:20 ` Grazvydas Ignotas
2011-12-02 11:10 ` Artem Bityutskiy
2011-12-02 17:28 ` Brian Norris
2011-12-04 14:29 ` Artem Bityutskiy
2011-12-05 8:11 ` Jan Weitzel
2011-12-05 10:32 ` Grazvydas Ignotas
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=1322557213-23565-1-git-send-email-j.weitzel@phytec.de \
--to=j.weitzel@phytec.de \
--cc=computersforpeace@gmail.com \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tglx@linutronix.de \
/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