[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140325170102.GC30641@obsidianresearch.com>
Date: Tue, 25 Mar 2014 11:01:02 -0600
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Lee Jones <lee.jones@...aro.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
angus.clark@...com, kernel@...inux.com,
linux-mtd@...ts.infradead.org, pekon@...com,
computersforpeace@...il.com, dwmw2@...radead.org,
Boris BREZILLON <b.brezillon.dev@...il.com>
Subject: Re: [RFC 02/47] mtd: nand: add ONFI NAND Timing Mode Specifications
On Tue, Mar 25, 2014 at 08:19:19AM +0000, Lee Jones wrote:
> This patch adds a new structure, 'nand_timing_spec', to capture the A/C
> timing characteristics of NAND devices.
Boris BREZILLON <b.brezillon.dev@...il.com> has been working on a
similar patch for a time now, and I think has an implementation for
the sunxi driver.
> some of the major NAND manufacturers (e.g. Samsung, Toshiba). Here we
> have followed broadly the ONFI timing definitions.
Timing specifications that are not precisely defined are
useless.. I would stick entirely with the well defined ONFI ones
until a need arises..
> + * Note, 'tR' field (maximum page read time) is extracted from the ONFI
> + * parameter page during device probe.
> + */
> +struct nand_timing_spec nand_onfi_timing_specs[] = {
const?
> + /*
> + * ONFI Timing Mode '0' (supported on all ONFI compliant devices)
> + */
> + [0] = {
> + .tCLS = 50,
> + .tCS = 70,
> + .tALS = 50,
Use picoseconds, ns is already loosing precision at the higher timing
modes.
Cheers,
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists