linux-kernel - Re: [RFC PATCH 6/7] gpio: omap: move pm runtime in irq_chip.irq_bus_lock/sync

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

Date:	Thu, 24 Sep 2015 15:35:30 -0700
From:	Grygorii Strashko <grygorii.strashko@...com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	Alexandre Courbot <gnurou@...il.com>,
	Santosh Shilimkar <ssantosh@...nel.org>,
	Kevin Hilman <khilman@...prootsystems.com>,
	Tony Lindgren <tony@...mide.com>,
	Javier Martinez Canillas <javier@...hile0.org>,
	Linux-OMAP <linux-omap@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	<linux-rt-users@...r.kernel.org>
Subject: Re: [RFC PATCH 6/7] gpio: omap: move pm runtime in
 irq_chip.irq_bus_lock/sync_unlock

On 09/24/2015 03:28 PM, Linus Walleij wrote:
> On Tue, Aug 18, 2015 at 4:10 AM, Grygorii Strashko
> <grygorii.strashko@...com> wrote:
>
>> The PM runtime API can't be used in atomic contex on -RT even if
>> it's configured as irqsafe. As result, below error report can
>> be seen when PM runtime API called from IRQ chip's callbacks
>> irq_startup/irq_shutdown/irq_set_type, because they are
>> protected by RAW spinlock:
>
> Grygorri I have a massive backlog of mail but if patch 6&7 are
> still applicable, can you rebase and send me these for the v4.3-rc2+
> tree?
>

sure.

Thanks.

-- 
regards,
-grygorii
--
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/