[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165132754299.647302.2972320978462383968.b4-ty@sntech.de>
Date: Sat, 30 Apr 2022 16:05:52 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
linux-gpio@...r.kernel.org, Caleb Connolly <kc@...tmarketos.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Rob Herring <robh+dt@...nel.org>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org
Cc: Heiko Stuebner <heiko@...ech.de>,
Arnaud Ferraris <arnaud.ferraris@...labora.com>,
~postmarketos/upstreaming@...ts.sr.ht, martijn@...xit.nl
Subject: Re: (subset) [PATCH 0/4] rockchip: support configuring pins as input
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@...ech.de>
Powered by blists - more mailing lists