From: Tony Lindgren <tony@atomide.com>
To: pekon <pekon@pek-sem.com>
Cc: Roger Quadros <rogerq@ti.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/6] OMAP2+: GPMC: NAND fixes for 3.17
Date: Thu, 4 Sep 2014 12:40:28 -0700 [thread overview]
Message-ID: <20140904194027.GA14698@atomide.com> (raw)
In-Reply-To: <5408B6E0.2090806@pek-sem.com>
* pekon <pekon@pek-sem.com> [140904 12:01]:
> Hi Tony,
>
> On Thursday 04 September 2014 03:12 AM, Tony Lindgren wrote:
> >* Tony Lindgren <tony@atomide.com> [140903 14:41]:
> >>* Roger Quadros <rogerq@ti.com> [140902 06:57]:
> >>>Hi Tony,
> >>>
> >>>These are some of the issues I found while testing v3.17-rc3.
> >>>
> >>>- Wrong ECC scheme used for am43x GP and EPOS evm. We need to use
> >>>BCH16 instead of BCH8.
> >>>
> >>>- Wrong read/write wait pin monitoring setting used for NAND
> >>>resulting in "L3 application error" debug message on console.
> >>>
> >>>- Pin conflict issue on am43x EPOS evm with QSPI and NAND.
> >>
> >>Thanks applying into omap-for-v3.17/fixes-v2.
> >
> >Sorry replied to the wrong thread, this series still seems
> >to have some pending comments so not applying this one.
> >
> Only [Patch 3/6] had some pending comments, but after Roger's
> clarification there are no further comments from me. So for
> entire series ..
>
> Reviewed-by: Pekon Gupta <pekon@pek-sem.com>
OK thanks will apply all into omap-for-v3.17/fixes-v2.
Regards,
Tony
next prev parent reply other threads:[~2014-09-04 19:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 13:57 [PATCH 0/6] OMAP2+: GPMC: NAND fixes for 3.17 Roger Quadros
2014-09-02 13:57 ` [PATCH 1/6] ARM: dts: am43x-epos-evm: Use BCH16 ECC scheme instead of BCH8 Roger Quadros
2014-09-02 18:29 ` pekon
2014-09-02 13:57 ` [PATCH 2/6] ARM: dts: am437x-gp-evm: " Roger Quadros
2014-09-02 18:30 ` pekon
2014-09-02 13:57 ` [PATCH 3/6] ARM: dts: am437x-gp-evm: Don't use read/write wait monitoring Roger Quadros
2014-09-02 19:02 ` pekon
2014-09-03 8:32 ` Roger Quadros
2014-09-03 17:29 ` pekon
[not found] ` <540834F9.8080902@ti.com>
2014-09-04 18:57 ` pekon
2014-09-02 13:57 ` [PATCH 4/6] ARM: dts: am43xx-epos-evm: " Roger Quadros
2014-09-02 13:57 ` [PATCH 5/6] ARM: OMAP2+: gpmc: Don't complain if wait pin is used without r/w monitoring Roger Quadros
2014-09-02 19:12 ` pekon
2014-09-03 8:34 ` Roger Quadros
2014-09-02 13:57 ` [PATCH 6/6] ARM: dts: am43x-epos-evm: Disable QSPI to prevent conflict with GPMC-NAND Roger Quadros
2014-09-02 18:09 ` [PATCH 0/6] OMAP2+: GPMC: NAND fixes for 3.17 pekon
2014-09-03 21:40 ` Tony Lindgren
2014-09-03 21:42 ` Tony Lindgren
2014-09-04 19:00 ` pekon
2014-09-04 19:40 ` Tony Lindgren [this message]
2014-09-05 7:57 ` Roger Quadros
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=20140904194027.GA14698@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@pek-sem.com \
--cc=rogerq@ti.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 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).