linux-kernel - Re: [PATCH] pinctrl: mediatek: fix suspend/resume timing issue

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>] [day] [month] [year] [list]

Date:	Wed, 8 Jun 2016 10:10:19 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	hongkun.cao@...iatek.com
Cc:	Rob Herring <robh+dt@...nel.org>,
	Paweł Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	Matthias Brugger <matthias.bgg@...il.com>,
	Erin Lo <erin.lo@...iatek.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	srv_heupstream@...iatek.com,
	Hongzhou Yang <hongzhou.yang@...iatek.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"moderated list:ARM/Mediatek SoC support" 
	<linux-mediatek@...ts.infradead.org>,
	Yingjoe Chen <yingjoe.chen@...iatek.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Sudeep Holla <sudeep.holla@....com>
Subject: Re: [PATCH] pinctrl: mediatek: fix suspend/resume timing issue

On Fri, Jun 3, 2016 at 5:28 AM,  <hongkun.cao@...iatek.com> wrote:

> From: "hongkun.cao" <hongkun.cao@...iatek.com>
>
> An irq which is a wake up source maybe masked unexpectedly if the wake
> up source irq was triggered after pinctrl irqchip suspend and before
> suspend_device_irqs finished.
> Use *_noirq callbacks to guarantee pinctrl irqchip suspend would be
> called after suspend_devices_irqs.
>
> Signed-off-by: hongkun.cao <hongkun.cao@...iatek.com>

No rreaction from the other maintainers but it looks correct to me
so patch applied.

Yours,
Linus Walleij