From: Thor Thayer <tthayer@opensource.altera.com>
To: Borislav Petkov <bp@alien8.de>, <dinguyen@opensource.altera.com>
Cc: <dinh.linux@gmail.com>, <atull@opensource.altera.com>,
<dougthompson@xmission.com>, <mchehab@osg.samsung.com>,
<linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] EDAC, altera: wrap edac pm with a CONFIG_PM
Date: Fri, 5 Jun 2015 16:40:29 -0500 [thread overview]
Message-ID: <5572174D.60804@opensource.altera.com> (raw)
In-Reply-To: <20150605151559.GK3679@pd.tnic>
Hi Boris,
On 06/05/2015 10:15 AM, Borislav Petkov wrote:
> On Fri, Jun 05, 2015 at 08:49:15AM -0500, dinguyen@opensource.altera.com wrote:
>> From: Alan Tull <atull@opensource.altera.com>
>>
>> Suspend-to-RAM and EDAC support are mutually exclusive on
>> SOCFPGA. If the EDAC is enabled, it will prevent the
>> platform from going into suspend.
>
> Btw, what is exactly the problem with EDAC being enabled and not being
> able to suspend? Is it a hardware issue?
>
> Because if it is sw one, we probably could change the EDAC core to
> accomodate power management. On x86 we don't need to do anything special
> to EDAC wrt PM though - we simply suspend.
>
> Thanks.
>
Yes, in our case, it is a hardware issue but I'm still gathering
information.
The IRQ vectors for OCRAM reside on DDR and in Suspend-to-RAM mode we're
executing out of OCRAM. If an ECC error occurs, we can't handle it so it
was decided to make them mutually exclusive.
Thor
next prev parent reply other threads:[~2015-06-05 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 13:49 [PATCH] EDAC, altera: wrap edac pm with a CONFIG_PM dinguyen
2015-06-05 15:15 ` Borislav Petkov
2015-06-05 21:40 ` Thor Thayer [this message]
2015-06-06 8:01 ` Borislav Petkov
2015-06-08 0:46 ` atull
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=5572174D.60804@opensource.altera.com \
--to=tthayer@opensource.altera.com \
--cc=atull@opensource.altera.com \
--cc=bp@alien8.de \
--cc=dinguyen@opensource.altera.com \
--cc=dinh.linux@gmail.com \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.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.