From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/4] ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND
Date: Mon, 05 Nov 2012 13:58:22 +0100 [thread overview]
Message-ID: <5097B7EE.3000508@gmail.com> (raw)
In-Reply-To: <518397C60809E147AF5323E0420B992E3E9DA81F@DBDE01.ent.ti.com>
On 05.11.2012 12:03, Philip, Avinash wrote:
> On Fri, Nov 02, 2012 at 20:55:56, Daniel Mack wrote:
>> This patch adds basic DT bindings for OMAP GPMC.
>>
>> The actual peripherals are instanciated from child nodes within the GPMC
>> node, and the only type of device that is currently supported is NAND.
>>
>> Code was added to parse the generic GPMC timing parameters and some
>> documentation with examples on how to use them.
>>
>> Successfully tested on an AM33xx board.
>>
>> Signed-off-by: Daniel Mack <zonque@gmail.com>
> [...]
>> +
>> + nand at 0,0 {
>> + reg = <0 0 0>; /* CS0, offset 0 */
>> + nand-bus-width = <16>;
>> + nand-ecc-mode = "none";
>> +
>> + gpmc,sync-clk = <0>;
>> + gpmc,cs-on = <0>;
>> + gpmc,cs-rd-off = <36>;
>> + gpmc,cs-wr-off = <36>;
>> + gpmc,adv-on = <6>;
>> + gpmc,adv-rd-off = <24>;
>> + gpmc,adv-wr-off = <36>;
>> + gpmc,we-off = <30>;
>> + gpmc,oe-off = <48>;
>> + gpmc,access = <54>;
>> + gpmc,rd-cycle = <72>;
>> + gpmc,wr-cycle = <72>;
>> + gpmc,wr-access = <30>;
>> + gpmc,wr-data-mux-bus = <0>;
>> +
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> +
>
> Can you take the timings (for example) from arago tree. The timings is tested in am335x-evm
> So the timings can be directly used to populate GPMC timings. Timings can found at
>
> http://arago-project.org/git/projects/?p=linux-am33x.git;a=commitdiff;
> h=66bfbd2c5b35dc81edce0c24843c476161ab5978;hp=370630359cb8db711cf0941cd2a242e28ccfb61e
>
> [...]
>> +static int gpmc_probe_dt(struct platform_device *pdev)
>
> Can you take care of the following section mismatch.
> WARNING: vmlinux.o(.text+0x1e2d0): Section mismatch in reference
> from the function gpmc_probe_dt() to the function .init.text:gpmc_nand_init().
Sore, both fixed for v4.
> [...]
>> +
>> + val = of_get_nand_ecc_mode(child);
>> + if (val >= 0)
>> + gpmc_nand_data->ecc_opt = val;
>
> This will fail for BCH. Index of "soft_bch" is 5 & also don't have selection
> option between for BCH4 & BCH8 also.
> Can you use the of_property_read_u32 (as done early) to pass the ecc selection
> from dt file. This will help selection of BCH4 & BCH8 ecc options.
Hmm. Shouldn't we rather teach of_get_nand_ecc_mode() that two modes and
bring the enum in sync?
Daniel
next prev parent reply other threads:[~2012-11-05 12:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 15:25 [PATCH v3 0/4] RFC: OMAP GPMC DT bindings Daniel Mack
2012-11-02 15:25 ` [PATCH v3 1/4] mtd: omap-nand: pass device_node in platform data Daniel Mack
2012-11-02 15:25 ` [PATCH v3 2/4] ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs Daniel Mack
2012-11-05 10:57 ` Philip, Avinash
2012-11-02 15:25 ` [PATCH v3 3/4] ARM: OMAP: gpmc: don't create devices from initcall on DT Daniel Mack
2012-11-02 15:25 ` [PATCH v3 4/4] ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND Daniel Mack
2012-11-05 11:03 ` Philip, Avinash
2012-11-05 12:58 ` Daniel Mack [this message]
2012-11-05 13:29 ` Philip, Avinash
2012-11-05 23:03 ` Murali Karicheri
2012-11-07 9:48 ` Daniel Mack
2012-11-07 15:37 ` Philip, Avinash
2012-11-10 18:56 ` Daniel Mack
2012-11-15 0:26 ` Daniel Mack
2012-11-19 6:06 ` Philip, Avinash
2012-11-20 15:59 ` Peter Korsgaard
2012-11-21 10:15 ` Daniel Mack
2012-11-23 10:43 ` Philip, Avinash
2012-11-27 14:00 ` Daniel Mack
2012-11-28 5:01 ` Philip, Avinash
2012-12-01 21:50 ` Ivan Djelic
2012-12-05 5:15 ` Philip, Avinash
2012-12-06 10:15 ` Ivan Djelic
2012-12-06 13:12 ` Philip, Avinash
2012-11-02 19:29 ` [PATCH v3 0/4] RFC: OMAP GPMC DT bindings Jon Hunter
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=5097B7EE.3000508@gmail.com \
--to=zonque@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).