linux-kernel - Re: [PATCH] EDAC, altera: wrap edac pm with a CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5572174D.60804@opensource.altera.com>
Date:	Fri, 5 Jun 2015 16:40:29 -0500
From:	Thor Thayer <tthayer@...nsource.altera.com>
To:	Borislav Petkov <bp@...en8.de>, <dinguyen@...nsource.altera.com>
CC:	<dinh.linux@...il.com>, <atull@...nsource.altera.com>,
	<dougthompson@...ssion.com>, <mchehab@....samsung.com>,
	<linux-edac@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] EDAC, altera: wrap edac pm with a CONFIG_PM

Hi Boris,

On 06/05/2015 10:15 AM, Borislav Petkov wrote:
> On Fri, Jun 05, 2015 at 08:49:15AM -0500, dinguyen@...nsource.altera.com wrote:
>> From: Alan Tull <atull@...nsource.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/