From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, Caleb Connolly <kc@postmarketos.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Heiko Stuebner <heiko@sntech.de>,
Arnaud Ferraris <arnaud.ferraris@collabora.com>,
~postmarketos/upstreaming@lists.sr.ht, martijn@brixit.nl
Subject: Re: (subset) [PATCH 0/4] rockchip: support configuring pins as input
Date: Sat, 30 Apr 2022 16:05:52 +0200 [thread overview]
Message-ID: <165132754299.647302.2972320978462383968.b4-ty@sntech.de> (raw)
In-Reply-To: <20220328005005.72492-1-kc@postmarketos.org>
On Mon, 28 Mar 2022 01:50:01 +0100, Caleb Connolly wrote:
> Add support for configuring pins as input to the rockchip pinctrl
> driver. This is required for example for devices which use non-standard
> configurations for gpio interrupts, specifically for the light/proximity
> sensor on the RK3399 powered PinePhone Pro (which will be coming
> upstream in a future patch series).
>
> Due to the complicated layout of the RK pinctrl/gpio drivers, some extra
> work is required to handle deferring the GPIO configuration. On RK3399
> the pinctrl driver always probes before the GPIO controller driver, so
> the PIN_CONFIG_OUTPUT and PIN_CONFIG_INPUT_ENABLE params both have to be
> deferred, this series also reworks the deferred pin handling to be
> generic and support any param rather than only the PIN_CONFIG_OUTPUT
> param.
Applied, thanks!
[4/4] arm64: dts: rockchip: rk3399: add an input enable pinconf
commit: ec48c3e82ca36a66ae37ba8b1fdb9a7561dcab14
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, Caleb Connolly <kc@postmarketos.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Heiko Stuebner <heiko@sntech.de>,
Arnaud Ferraris <arnaud.ferraris@collabora.com>,
~postmarketos/upstreaming@lists.sr.ht, martijn@brixit.nl
Subject: Re: (subset) [PATCH 0/4] rockchip: support configuring pins as input
Date: Sat, 30 Apr 2022 16:05:52 +0200 [thread overview]
Message-ID: <165132754299.647302.2972320978462383968.b4-ty@sntech.de> (raw)
In-Reply-To: <20220328005005.72492-1-kc@postmarketos.org>
On Mon, 28 Mar 2022 01:50:01 +0100, Caleb Connolly wrote:
> Add support for configuring pins as input to the rockchip pinctrl
> driver. This is required for example for devices which use non-standard
> configurations for gpio interrupts, specifically for the light/proximity
> sensor on the RK3399 powered PinePhone Pro (which will be coming
> upstream in a future patch series).
>
> Due to the complicated layout of the RK pinctrl/gpio drivers, some extra
> work is required to handle deferring the GPIO configuration. On RK3399
> the pinctrl driver always probes before the GPIO controller driver, so
> the PIN_CONFIG_OUTPUT and PIN_CONFIG_INPUT_ENABLE params both have to be
> deferred, this series also reworks the deferred pin handling to be
> generic and support any param rather than only the PIN_CONFIG_OUTPUT
> param.
Applied, thanks!
[4/4] arm64: dts: rockchip: rk3399: add an input enable pinconf
commit: ec48c3e82ca36a66ae37ba8b1fdb9a7561dcab14
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, Caleb Connolly <kc@postmarketos.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Heiko Stuebner <heiko@sntech.de>,
Arnaud Ferraris <arnaud.ferraris@collabora.com>,
~postmarketos/upstreaming@lists.sr.ht, martijn@brixit.nl
Subject: Re: (subset) [PATCH 0/4] rockchip: support configuring pins as input
Date: Sat, 30 Apr 2022 16:05:52 +0200 [thread overview]
Message-ID: <165132754299.647302.2972320978462383968.b4-ty@sntech.de> (raw)
In-Reply-To: <20220328005005.72492-1-kc@postmarketos.org>
On Mon, 28 Mar 2022 01:50:01 +0100, Caleb Connolly wrote:
> Add support for configuring pins as input to the rockchip pinctrl
> driver. This is required for example for devices which use non-standard
> configurations for gpio interrupts, specifically for the light/proximity
> sensor on the RK3399 powered PinePhone Pro (which will be coming
> upstream in a future patch series).
>
> Due to the complicated layout of the RK pinctrl/gpio drivers, some extra
> work is required to handle deferring the GPIO configuration. On RK3399
> the pinctrl driver always probes before the GPIO controller driver, so
> the PIN_CONFIG_OUTPUT and PIN_CONFIG_INPUT_ENABLE params both have to be
> deferred, this series also reworks the deferred pin handling to be
> generic and support any param rather than only the PIN_CONFIG_OUTPUT
> param.
Applied, thanks!
[4/4] arm64: dts: rockchip: rk3399: add an input enable pinconf
commit: ec48c3e82ca36a66ae37ba8b1fdb9a7561dcab14
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
_______________________________________________
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-30 14:06 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
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 ` Heiko Stuebner [this message]
2022-04-30 14:05 ` (subset) " 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=165132754299.647302.2972320978462383968.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=arnaud.ferraris@collabora.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--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.