From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Sebastian Reichel <sre@kernel.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Jean-Jacques Hiblot <jjhiblot@traphandler.com>,
Linux PM list <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/2] ARM: at91: properly handle LPDDR poweroff
Date: Wed, 19 Oct 2016 16:30:55 +0200 [thread overview]
Message-ID: <585ae249-07ef-5299-17aa-2bcf79a09f24@atmel.com> (raw)
In-Reply-To: <CAMuHMdUnoHPOQeO=oSRkNWbfLGDzZbBZvPFr3dS7TOKPQFcUxQ@mail.gmail.com>
Le 19/10/2016 à 16:07, Geert Uytterhoeven a écrit :
> On Wed, Oct 19, 2016 at 1:44 PM, Alexandre Belloni
> <alexandre.belloni@free-electrons.com> wrote:
>> LPDDR memories can only handle up to 400 uncontrolled power offs in their
>> life. The proper power off sequence has to be applied before shutting down the
>> SoC.
>
> Interesting. How many boards have been killed during kernelci.org
> operation?
The reason given above is usually the one that prevent manufacturers
from using LPDDR on "evaluation" boards. So all Atmel boards use
SDRAM/DDR2/DDR3 not the LP variants.
Final products (and internal validation boards, obviously) though use
these type of RAM so we must be prepared to handle them.
Best regards,
--
Nicolas Ferre
prev parent reply other threads:[~2016-10-19 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 11:44 [PATCH v2 0/2] ARM: at91: properly handle LPDDR poweroff Alexandre Belloni
2016-10-19 11:44 ` [PATCH v2 1/2] ARM: at91: define LPDDR types Alexandre Belloni
2016-10-19 11:44 ` [PATCH v2 2/2] power/reset: at91-poweroff: timely shutdown LPDDR memories Alexandre Belloni
2016-10-19 14:07 ` [PATCH v2 0/2] ARM: at91: properly handle LPDDR poweroff Geert Uytterhoeven
2016-10-19 14:30 ` Nicolas Ferre [this message]
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=585ae249-07ef-5299-17aa-2bcf79a09f24@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=dbaryshkov@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jjhiblot@traphandler.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.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