On Mon, Oct 31, 2016 at 3:57 PM, Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx> Patch applied. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/3] pinctrl: cherryview: Serialize register access in suspend and resume hooks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 1/3] pinctrl: cherryview: Serialize register access in suspend and resume hooks
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Fri, 4 Nov 2016 16:12:14 +0100
- In-reply-to: <20161031145734.193016-1-mika.westerberg@linux.intel.com>
- References: <20161031145734.193016-1-mika.westerberg@linux.intel.com>
- Follow-Ups:
- References:
- [PATCH 1/3] pinctrl: cherryview: Serialize register access in suspend and resume hooks
- From: Mika Westerberg
- [PATCH 1/3] pinctrl: cherryview: Serialize register access in suspend and resume hooks
- Prev by Date: Re: [PATCH 4/9] pinctrl: meson: allow gpio to request irq
- Next by Date: Re: [PATCH 2/3] pinctrl: cherryview: Prevent possible interrupt storm on resume
- Previous by thread: Re: [PATCH 2/3] pinctrl: cherryview: Prevent possible interrupt storm on resume
- Next by thread: Re: [PATCH 1/3] pinctrl: cherryview: Serialize register access in suspend and resume hooks
- Index(es):
 |