From: Boris BREZILLON <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-sunxi@googlegroups.com,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org,
Yassin Jaffer <yassinjaffer@gmail.com>
Subject: Re: [PATCH v2 1/2] mtd: nand: support ONFI timing mode retrieval for non-ONFI NANDs
Date: Mon, 22 Sep 2014 20:13:15 +0200 [thread overview]
Message-ID: <20140922201315.022fefea@bbrezillon> (raw)
In-Reply-To: <20140922175834.GM1193@ld-irv-0074>
On Mon, 22 Sep 2014 10:58:34 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
> On Mon, Sep 22, 2014 at 04:25:10PM +0200, Boris BREZILLON wrote:
> > Add an onfi_timing_mode_default field to nand_chip and nand_flash_dev in
> > order to support NAND timings definition for non-ONFI NAND.
> >
> > NAND that support better timings mode than the default one have to define
> > a new entry in the nand_ids table.
> >
> > The default timing mode should be deduced from timings description from
> > the datasheet and the ONFI specification
> > (www.onfi.org/~/media/ONFI/specs/onfi_3_1_spec.pdf, chapter 4.15
> > "Timing Parameters").
> > You should choose the closest mode that fit the timings requirements of
> > your NAND chip.
> >
> > Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
>
> You have some (new?) checkpatch warnings:
>
Sorry for that. I just sent a new version fixing those warnings.
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Boris BREZILLON <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com,
Yassin Jaffer <yassinjaffer@gmail.com>
Subject: Re: [PATCH v2 1/2] mtd: nand: support ONFI timing mode retrieval for non-ONFI NANDs
Date: Mon, 22 Sep 2014 20:13:15 +0200 [thread overview]
Message-ID: <20140922201315.022fefea@bbrezillon> (raw)
In-Reply-To: <20140922175834.GM1193@ld-irv-0074>
On Mon, 22 Sep 2014 10:58:34 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
> On Mon, Sep 22, 2014 at 04:25:10PM +0200, Boris BREZILLON wrote:
> > Add an onfi_timing_mode_default field to nand_chip and nand_flash_dev in
> > order to support NAND timings definition for non-ONFI NAND.
> >
> > NAND that support better timings mode than the default one have to define
> > a new entry in the nand_ids table.
> >
> > The default timing mode should be deduced from timings description from
> > the datasheet and the ONFI specification
> > (www.onfi.org/~/media/ONFI/specs/onfi_3_1_spec.pdf, chapter 4.15
> > "Timing Parameters").
> > You should choose the closest mode that fit the timings requirements of
> > your NAND chip.
> >
> > Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
>
> You have some (new?) checkpatch warnings:
>
Sorry for that. I just sent a new version fixing those warnings.
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-22 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 14:25 [PATCH v2 0/2] mtd: nand: support ONFI timings mode retrieval for non-ONFI NANDs Boris BREZILLON
2014-09-22 14:25 ` Boris BREZILLON
2014-09-22 14:25 ` [PATCH v2 1/2] mtd: nand: support ONFI timing " Boris BREZILLON
2014-09-22 14:25 ` Boris BREZILLON
2014-09-22 17:58 ` Brian Norris
2014-09-22 17:58 ` Brian Norris
2014-09-22 18:13 ` Boris BREZILLON [this message]
2014-09-22 18:13 ` Boris BREZILLON
2014-09-22 14:25 ` [PATCH v2 2/2] mtd: nand: add Hynix's H27UCG8T2ATR-BC to nand_ids table Boris BREZILLON
2014-09-22 14:25 ` Boris BREZILLON
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=20140922201315.022fefea@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sunxi@googlegroups.com \
--cc=yassinjaffer@gmail.com \
/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.