On Tue, Mar 11, 2025 at 3:20 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > From: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> > > Some drivers as well as the character device and sysfs code check > whether the line actually is in output mode before allowing the user to > set a value. > > However, GPIO value setters now return integer values and can indicate > failures. This allows us to move these checks into the core code. > > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> Makes sense, if there are regressions let's smoke them out in linux-next. Reviewed-by: Linus Walleij <linus.walleij@xxxxxxxxxx> Yours, Linus Walleij
Re: [PATCH] gpiolib: don't allow setting values on input lines
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] gpiolib: don't allow setting values on input lines
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Fri, 14 Mar 2025 11:33:06 +0100
- In-reply-to: <20250311-gpio-set-check-output-v1-1-d971bca9e6fa@linaro.org>
- References: <20250311-gpio-set-check-output-v1-1-d971bca9e6fa@linaro.org>
- Follow-Ups:
- Re: [PATCH] gpiolib: don't allow setting values on input lines
- From: Bartosz Golaszewski
- Re: [PATCH] gpiolib: don't allow setting values on input lines
- References:
- [PATCH] gpiolib: don't allow setting values on input lines
- From: Bartosz Golaszewski
- [PATCH] gpiolib: don't allow setting values on input lines
- Prev by Date: Re: [PATCH 5/5] dt-bindings: pmic: mediatek: Add pmic documents
- Next by Date: Re: [PATCH next] pinctrl: amd: isp411: Fix IS_ERR() vs NULL check in probe()
- Previous by thread: [PATCH] gpiolib: don't allow setting values on input lines
- Next by thread: Re: [PATCH] gpiolib: don't allow setting values on input lines
- Index(es):
 |