From: Jan Weitzel <J.Weitzel@phytec.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: dedekind@infradead.org, tglx@linutronix.de,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mdt nand: omap2+ use platform options
Date: Thu, 01 Dec 2011 09:21:11 +0100 [thread overview]
Message-ID: <1322727671.4543.28.camel@lws-weitzel> (raw)
In-Reply-To: <CAN8TOE-uO2rzPt64ubwzTkh6Wz2wBnH88d3RdsGdJJSpCHsdeg@mail.gmail.com>
Am Mittwoch, den 30.11.2011, 12:31 -0800 schrieb Brian Norris:
> On Tue, Nov 29, 2011 at 1:00 AM, Jan Weitzel <j.weitzel@phytec.de> wrote:
> > 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
>
> Just to clarify, were the pdata->options ever used before? And does
> struct omap_nand_platform_data even have such a field?
No not used, but field exists. There is also a devsize field which is
used to provide NAND_BUSWIDTH_16 to info->nand.options
(drivers/mtd/nand/omap2.c)
Jan
> Brian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-01 8:21 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 ` [PATCH] mdt nand: omap2+ use platform options Jan Weitzel
2011-11-30 20:31 ` Brian Norris
2011-12-01 8:21 ` Jan Weitzel [this message]
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=1322727671.4543.28.camel@lws-weitzel \
--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