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
| ||
|
Date: Mon, 14 Sep 2015 10:43:53 -0700 From: Florian Fainelli <f.fainelli@...il.com> To: Brian Norris <computersforpeace@...il.com>, Florian Fainelli <f.fainelli@...il.com> CC: Gregory Fong <gregory.0xf0@...il.com>, Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>, Mark Rutland <mark.rutland@....com>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Kumar Gala <galak@...eaurora.org>, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, bcm-kernel-feedback-list@...adcom.com Subject: Re: [PATCH 6/7] ARM: brcmstb: mask GIC IRQs on suspend On 14/09/15 10:42, Brian Norris wrote: > One more thing: > > On Sat, Sep 12, 2015 at 12:53:32PM -0700, Florian Fainelli wrote: >> Le 06/18/15 17:11, Brian Norris a écrit : >>> Lazily-masked IRQs can cause system suspend problems (e.g., spurious >>> wakeups from WFI), so we need to be sure non-wakeup GIC interrupts get >>> masked, not just disabled, during system suspend. >>> >>> Signed-off-by: Brian Norris <computersforpeace@...il.com> >> >> Dropped this patch, no longer needed as of 4.3-rc0 with >> aec89ef72ba6c94420f599dcb684ed66937cdacf ("irqchip/gic: Enable >> SKIP_SET_WAKE and MASK_ON_SUSPEND") > > With this patch dropped, then we really don't need > arch/arm/mach-bcm/brcmstb.c any more, AFAICT. Unless you have more plans > for this file, I can send a patch... I am in the process of cleaning up the BIU control register setup for the memory controller write-pairing support to get that submitted, and that needs to be initialized before SMP, so we will still need an entry point in the machine code to do that. Thanks! -- Florian -- 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/
Powered by blists - more mailing lists