[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=MfmaW7QX6Q8JFi2-32E_JvE=z6EspnpiHD+4JjeNGFT4g@mail.gmail.com>
Date: Mon, 18 Apr 2022 21:47:43 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Caleb Connolly <kc@...tmarketos.org>
Cc: Rob Herring <robh+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>,
Linus Walleij <linus.walleij@...aro.org>,
devicetree <devicetree@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
~postmarketos/upstreaming@...ts.sr.ht, martijn@...xit.nl,
Arnaud Ferraris <arnaud.ferraris@...labora.com>
Subject: Re: [PATCH 3/4] gpio/rockchip: handle deferring input-enable pinconfs
On Mon, Mar 28, 2022 at 2:50 AM Caleb Connolly <kc@...tmarketos.org> wrote:
>
> Add support for deferred PIN_CONFIG_INPUT_ENABLE handling.
>
> Signed-off-by: Caleb Connolly <kc@...tmarketos.org>
> ---
> drivers/gpio/gpio-rockchip.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpio/gpio-rockchip.c b/drivers/gpio/gpio-rockchip.c
> index bcf5214e3586..e342a6dc4c6c 100644
> --- a/drivers/gpio/gpio-rockchip.c
> +++ b/drivers/gpio/gpio-rockchip.c
> @@ -760,6 +760,11 @@ static int rockchip_gpio_probe(struct platform_device *pdev)
> dev_warn(dev, "setting output pin %u to %u failed\n", cfg->pin,
> cfg->arg);
> break;
> + case PIN_CONFIG_INPUT_ENABLE:
> + ret = rockchip_gpio_direction_input(&bank->gpio_chip, cfg->pin);
> + if (ret)
> + dev_warn(dev, "setting input pin %u failed\n", cfg->pin);
> + break;
> default:
> dev_warn(dev, "unknown deferred config param %d\n", cfg->param);
> break;
> --
> 2.35.1
>
Does this depend on patches 1 & 2 or does patch 4 depend on this one? If so:
Acked-by: Bartosz Golaszewski <brgl@...ev.pl>
Otherwise I can take it through the GPIO tree.
Bart
Powered by blists - more mailing lists