From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Caleb Connolly <kc@postmarketos.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Linus Walleij <linus.walleij@linaro.org>,
devicetree <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
~postmarketos/upstreaming@lists.sr.ht, martijn@brixit.nl,
Arnaud Ferraris <arnaud.ferraris@collabora.com>
Subject: Re: [PATCH 3/4] gpio/rockchip: handle deferring input-enable pinconfs
Date: Mon, 18 Apr 2022 21:47:43 +0200 [thread overview]
Message-ID: <CAMRc=MfmaW7QX6Q8JFi2-32E_JvE=z6EspnpiHD+4JjeNGFT4g@mail.gmail.com> (raw)
In-Reply-To: <20220328005005.72492-4-kc@postmarketos.org>
On Mon, Mar 28, 2022 at 2:50 AM Caleb Connolly <kc@postmarketos.org> wrote:
>
> Add support for deferred PIN_CONFIG_INPUT_ENABLE handling.
>
> Signed-off-by: Caleb Connolly <kc@postmarketos.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@bgdev.pl>
Otherwise I can take it through the GPIO tree.
Bart
WARNING: multiple messages have this Message-ID
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Caleb Connolly <kc@postmarketos.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Linus Walleij <linus.walleij@linaro.org>,
devicetree <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
~postmarketos/upstreaming@lists.sr.ht, martijn@brixit.nl,
Arnaud Ferraris <arnaud.ferraris@collabora.com>
Subject: Re: [PATCH 3/4] gpio/rockchip: handle deferring input-enable pinconfs
Date: Mon, 18 Apr 2022 21:47:43 +0200 [thread overview]
Message-ID: <CAMRc=MfmaW7QX6Q8JFi2-32E_JvE=z6EspnpiHD+4JjeNGFT4g@mail.gmail.com> (raw)
In-Reply-To: <20220328005005.72492-4-kc@postmarketos.org>
On Mon, Mar 28, 2022 at 2:50 AM Caleb Connolly <kc@postmarketos.org> wrote:
>
> Add support for deferred PIN_CONFIG_INPUT_ENABLE handling.
>
> Signed-off-by: Caleb Connolly <kc@postmarketos.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@bgdev.pl>
Otherwise I can take it through the GPIO tree.
Bart
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Caleb Connolly <kc@postmarketos.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Linus Walleij <linus.walleij@linaro.org>,
devicetree <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
~postmarketos/upstreaming@lists.sr.ht, martijn@brixit.nl,
Arnaud Ferraris <arnaud.ferraris@collabora.com>
Subject: Re: [PATCH 3/4] gpio/rockchip: handle deferring input-enable pinconfs
Date: Mon, 18 Apr 2022 21:47:43 +0200 [thread overview]
Message-ID: <CAMRc=MfmaW7QX6Q8JFi2-32E_JvE=z6EspnpiHD+4JjeNGFT4g@mail.gmail.com> (raw)
In-Reply-To: <20220328005005.72492-4-kc@postmarketos.org>
On Mon, Mar 28, 2022 at 2:50 AM Caleb Connolly <kc@postmarketos.org> wrote:
>
> Add support for deferred PIN_CONFIG_INPUT_ENABLE handling.
>
> Signed-off-by: Caleb Connolly <kc@postmarketos.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@bgdev.pl>
Otherwise I can take it through the GPIO tree.
Bart
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-18 19:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 0:50 [PATCH 0/4] rockchip: support configuring pins as input Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-03-28 0:50 ` [PATCH 1/4] pinctrl/rockchip: support deferring other gpio params Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-03-28 0:50 ` [PATCH 2/4] pinctrl/rockchip: support setting input-enable param Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-03-28 0:50 ` [PATCH 3/4] gpio/rockchip: handle deferring input-enable pinconfs Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-04-18 19:47 ` Bartosz Golaszewski [this message]
2022-04-18 19:47 ` Bartosz Golaszewski
2022-04-18 19:47 ` Bartosz Golaszewski
2022-03-28 0:50 ` [PATCH 4/4] arm64: dts: rockchip: rk3399: add an input enable pinconf Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-03-28 0:50 ` Caleb Connolly
2022-04-19 22:37 ` [PATCH 0/4] rockchip: support configuring pins as input Linus Walleij
2022-04-19 22:37 ` Linus Walleij
2022-04-19 22:37 ` Linus Walleij
2022-04-30 14:05 ` (subset) " Heiko Stuebner
2022-04-30 14:05 ` Heiko Stuebner
2022-04-30 14:05 ` Heiko Stuebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMRc=MfmaW7QX6Q8JFi2-32E_JvE=z6EspnpiHD+4JjeNGFT4g@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=arnaud.ferraris@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kc@postmarketos.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=martijn@brixit.nl \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.