On Mon, Jul 25, 2022 at 12:35 PM Marek Vasut <marex@xxxxxxx> wrote: > The irqchip callbacks in gpio-mxc perform register read-modify-write operations > without locking, which may lead to a race condition. Add the missing locking. > > In case the GPIO is used as IRQ, make sure it is configured as input. Changes look good to me: Reviewed-by: Linus Walleij <linus.walleij@xxxxxxxxxx> Yours, Linus Walleij
Re: [PATCH v5 0/2] gpio: mxc: Locking and direction input fix
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v5 0/2] gpio: mxc: Locking and direction input fix
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Fri, 26 Aug 2022 10:40:35 +0200
- In-reply-to: <20220725103445.88674-1-marex@denx.de>
- References: <20220725103445.88674-1-marex@denx.de>
- References:
- [PATCH v5 0/2] gpio: mxc: Locking and direction input fix
- From: Marek Vasut
- [PATCH v5 0/2] gpio: mxc: Locking and direction input fix
- Prev by Date: Re: [PATCH] pinctrl: sunxi: Fix name for A100 R_PIO
- Next by Date: Re: [PATCH 2/2] gpio/rockchip: Toggle edge trigger mode after acking
- Previous by thread: Re: [PATCH v5 0/2] gpio: mxc: Locking and direction input fix
- Next by thread: Re: [PATCH] pinctrl:Missing a blank line after declarations.
- Index(es):
 |