[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbgvVzv0YVmt7CQ6uwnsAtLnNoFJs6a8vopngb6CQVFqQ@mail.gmail.com>
Date: Fri, 4 Nov 2016 16:15:59 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Christian Steiner <christian.steiner@...look.de>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] pinctrl: cherryview: Serialize register access in
suspend and resume hooks
On Fri, Nov 4, 2016 at 4:12 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
> On Mon, Oct 31, 2016 at 3:57 PM, Mika Westerberg
> <mika.westerberg@...ux.intel.com> wrote:
>
>> If async suspend is enabled, the driver may access registers concurrently
>> with another instance which may fail because of the bug in Cherryview GPIO
>> hardware. Prevent this by taking the shared lock while accessing the
>> hardware in suspend and resume hooks.
>>
>> Signed-off-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
>
> Patch applied.
Mika should this and patch 2/3 be tagged for stable?
Yours,
Linus Walleij
Powered by blists - more mailing lists