From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Antoine Tenart <antoine.tenart@free-electrons.com>
Cc: sebastian.hesselbarth@gmail.com,
ezequiel.garcia@free-electrons.com, dwmw2@infradead.org,
computersforpeace@gmail.com, zmxu@marvell.com,
jszhang@marvell.com, linux-arm-kernel@lists.infradead.org,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup
Date: Sun, 25 Oct 2015 21:53:15 +0100 [thread overview]
Message-ID: <877fmallfo.fsf@belgarion.home> (raw)
In-Reply-To: <1445416144-9194-1-git-send-email-antoine.tenart@free-electrons.com> (Antoine Tenart's message of "Wed, 21 Oct 2015 10:28:59 +0200")
Antoine Tenart <antoine.tenart@free-electrons.com> writes:
> Hello,
>
> Let's try one more time to get this merged.
>
> This series was part of a bigger one[1], which was split into smaller
> ones as asked by Ezequiel[2]. When we take this into account this is
> v9; with a v1 sent in January, 9 months ago.
>
> Another series, introducing the Berlin nand support, depends on this.
>
> The aim here is to use the nand framework to setup the timings,
> while keeping the old in-driver way of configuration timings for
> compatibility reasons.
>
> You can find the series at:
> https://github.com/atenart/linux.git berlin/4.3/nand-timings
Hi Antoine,
I tested this serie once on my zylonite board, with both keep_config and no
keep_config setups. Both do work fine.
Cheers.
--
Robert
WARNING: multiple messages have this Message-ID (diff)
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup
Date: Sun, 25 Oct 2015 21:53:15 +0100 [thread overview]
Message-ID: <877fmallfo.fsf@belgarion.home> (raw)
In-Reply-To: <1445416144-9194-1-git-send-email-antoine.tenart@free-electrons.com> (Antoine Tenart's message of "Wed, 21 Oct 2015 10:28:59 +0200")
Antoine Tenart <antoine.tenart@free-electrons.com> writes:
> Hello,
>
> Let's try one more time to get this merged.
>
> This series was part of a bigger one[1], which was split into smaller
> ones as asked by Ezequiel[2]. When we take this into account this is
> v9; with a v1 sent in January, 9 months ago.
>
> Another series, introducing the Berlin nand support, depends on this.
>
> The aim here is to use the nand framework to setup the timings,
> while keeping the old in-driver way of configuration timings for
> compatibility reasons.
>
> You can find the series at:
> https://github.com/atenart/linux.git berlin/4.3/nand-timings
Hi Antoine,
I tested this serie once on my zylonite board, with both keep_config and no
keep_config setups. Both do work fine.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-10-25 21:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 8:28 [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup Antoine Tenart
2015-10-21 8:28 ` Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 1/5] mtd: pxa3xx: prepare allowing compile test Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 2/5] mtd: nand: allow compile test of MTD_NAND_PXA3xx Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-26 18:34 ` Brian Norris
2015-10-26 18:34 ` Brian Norris
2015-10-21 8:29 ` [PATCH v4 3/5] mtd: pxa3xx_nand: add helpers to setup the timings Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 4/5] mtd: pxa3xx_nand: rework flash detection and timing setup Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-21 8:29 ` [PATCH v4 5/5] mtd: pxa3xx_nand: clean up the pxa3xx timings Antoine Tenart
2015-10-21 8:29 ` Antoine Tenart
2015-10-22 15:12 ` [PATCH v4 0/5] mtd: pxa3xx_nand: rework the timing setup Thomas Petazzoni
2015-10-22 15:12 ` Thomas Petazzoni
2015-10-22 15:22 ` Ezequiel Garcia
2015-10-22 15:22 ` Ezequiel Garcia
2015-10-22 15:42 ` Thomas Petazzoni
2015-10-22 15:42 ` Thomas Petazzoni
2015-11-02 15:49 ` Ezequiel Garcia
2015-11-02 15:49 ` Ezequiel Garcia
2015-10-25 20:53 ` Robert Jarzmik [this message]
2015-10-25 20:53 ` Robert Jarzmik
2015-10-26 13:50 ` Ezequiel Garcia
2015-10-26 13:50 ` Ezequiel Garcia
2015-10-26 18:38 ` Brian Norris
2015-10-26 18:38 ` Brian Norris
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=877fmallfo.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=antoine.tenart@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=zmxu@marvell.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.