On Wed, Dec 4, 2019 at 3:41 PM Alexandre Torgue <alexandre.torgue@xxxxxx> wrote:
> This commit adds a check on ops pointer to avoid a kernel panic when
> ops->strict is used. Indeed, on some pinctrl driver (at least for
> pinctrl-stmfx) the pinmux ops is not implemented. Let's assume than gpio
> can be used in this case.
>
> Fixes: 472a61e777fe ("pinctrl/gpio: Take MUX usage into account")
> Signed-off-by: Alexandre Torgue <alexandre.torgue@xxxxxx>
Patch applied for fixes.
Yours,
Linus Walleij
Re: [PATCH] pinctrl: pinmux: fix a possible null pointer in pinmux_can_be_used_for_gpio
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] pinctrl: pinmux: fix a possible null pointer in pinmux_can_be_used_for_gpio
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Fri, 13 Dec 2019 10:57:53 +0100
- In-reply-to: <20191204144106.10876-1-alexandre.torgue@st.com>
- References: <20191204144106.10876-1-alexandre.torgue@st.com>
- References:
- [PATCH] pinctrl: pinmux: fix a possible null pointer in pinmux_can_be_used_for_gpio
- From: Alexandre Torgue
- [PATCH] pinctrl: pinmux: fix a possible null pointer in pinmux_can_be_used_for_gpio
- Prev by Date: Re: [PATCH 0/5] Add pinctrl support for dwapb gpio driver
- Next by Date: Re: [GIT PULL] intel-pinctrl for 5.5-2
- Previous by thread: [PATCH] pinctrl: pinmux: fix a possible null pointer in pinmux_can_be_used_for_gpio
- Next by thread: [PATCH v2 00/11] gpiolib: add an ioctl() for monitoring line status changes
- Index(es):
 |