[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160518160601.GB5407@kroah.com>
Date: Wed, 18 May 2016 09:06:01 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Manfred Schlaegl <manfred.schlaegl@....at>
Cc: Thierry Reding <thierry.reding@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Manfred Schlaegl <manfred.schlaegl@...zinger.com>,
Luis de Bethencourt <luis@...ethencourt.com>,
Olivier Sobrie <olivier@...rie.be>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Input: pwm-beeper - fix: scheduling while atomic
On Wed, May 18, 2016 at 05:16:49PM +0200, Manfred Schlaegl wrote:
> Pwm config may sleep so defer it using a worker.
>
> Trigger:
> On a Freescale i.MX53 based board we ran into "BUG: scheduling while
> atomic" because input_inject_event locks interrupts, but
> imx_pwm_config_v2 sleeps.
>
> Tested on Freescale i.MX53 SoC with 4.6.0 and 4.1.24.
>
> Unmodified applicable to
> * 4.6 (stable)
> * 4.5.4 (stable)
> * 4.4.10 (longterm)
> * 4.1.24 (longterm)
>
> Modified applicable to
> * 3.18.33 (longterm)
What does this all mean? Have you read
Documentation/stable_kernel_rules.txt for how to mark things for stable
inclusion?
thanks,
greg k-h
Powered by blists - more mailing lists