From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Chen-Yu Tsai <wens@csie.org>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-gpio@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] pinctrl: sunxi: Allow to configure pull-up / pull-down from GPIO flags
Date: Thu, 14 Mar 2019 20:32:49 +0100 [thread overview]
Message-ID: <cover.66d6a9a379de8ebf176e4c25a8542152dc09f366.1552591798.git-series.maxime.ripard@bootlin.com> (raw)
Hi,
Here is a series that addresses one of the issues we've had for some time
with our pinctrl driver, which is that while we should have had the strict
mode enabled, we didn't and now we have to deal with all the DT having GPIO
and pinctrl nodes for the same pins.
This was partially due to cargo cult (which has been addressed since), but
also due to technical limitations of the GPIO DT bindings at the time which
didn't allow to specify the pull-up and pull-down resistors, and the drive
strength of the pins.
Now that the former are supported, we can remove those users, and we will
deal with the latter eventually.
Let me know what you think,
Maxime
Maxime Ripard (6):
gpio: Set proper argument value to set_config
pinctrl: sunxi: implement pin_config_set
pinctrl: sunxi: Fix variable assignment syntax
pinctrl: sunxi: Declare set_config on the GPIO chip
ARM: dts: sunxi: Remove pinctrl groups setting bias
ARM: dts: sunxi: Remove useless pinctrl nodes
arch/arm/boot/dts/sun4i-a10-chuwi-v7-cw0825.dts | 20 +---
arch/arm/boot/dts/sun4i-a10-cubieboard.dts | 10 +--
arch/arm/boot/dts/sun4i-a10-dserve-dsrv9703c.dts | 20 +---
arch/arm/boot/dts/sun4i-a10-hyundai-a7hd.dts | 20 +---
arch/arm/boot/dts/sun4i-a10-inet1.dts | 20 +---
arch/arm/boot/dts/sun4i-a10-inet97fv2.dts | 20 +---
arch/arm/boot/dts/sun4i-a10-inet9f-rev03.dts | 72 +++--------
arch/arm/boot/dts/sun4i-a10-marsboard.dts | 12 +--
arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts | 18 +---
arch/arm/boot/dts/sun4i-a10-pcduino.dts | 12 +--
arch/arm/boot/dts/sun4i-a10-pov-protab2-ips9.dts | 19 +---
arch/arm/boot/dts/sun5i-a10s-auxtek-t004.dts | 10 +--
arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts | 10 +--
arch/arm/boot/dts/sun5i-a13-empire-electronix-d709.dts | 20 +---
arch/arm/boot/dts/sun5i-a13-hsg-h702.dts | 12 +--
arch/arm/boot/dts/sun5i-a13-olinuxino-micro.dts | 18 +---
arch/arm/boot/dts/sun5i-a13-olinuxino.dts | 18 +---
arch/arm/boot/dts/sun5i-a13-utoo-p66.dts | 14 +--
arch/arm/boot/dts/sun5i-r8-chip.dts | 12 +--
arch/arm/boot/dts/sun5i-reference-design-tablet.dtsi | 20 +---
arch/arm/boot/dts/sun6i-a31-colombus.dts | 14 +--
arch/arm/boot/dts/sun6i-reference-design-tablet.dtsi | 12 +--
arch/arm/boot/dts/sun7i-a20-bananapi.dts | 10 +--
arch/arm/boot/dts/sun7i-a20-cubieboard2.dts | 12 +--
arch/arm/boot/dts/sun7i-a20-lamobo-r1.dts | 12 +--
arch/arm/boot/dts/sun7i-a20-olinuxino-lime.dts | 18 +---
arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts | 18 +---
arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts | 18 +---
arch/arm/boot/dts/sun7i-a20-orangepi-mini.dts | 12 +--
arch/arm/boot/dts/sun7i-a20-orangepi.dts | 12 +--
arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts | 12 +--
arch/arm/boot/dts/sun7i-a20-pcduino3.dts | 12 +--
arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts | 12 +--
arch/arm/boot/dts/sun7i-a20-wits-pro-a20-dkt.dts | 12 +--
arch/arm/boot/dts/sun8i-h3-nanopi.dtsi | 23 +----
arch/arm/boot/dts/sun8i-h3-orangepi-2.dts | 30 +-----
arch/arm/boot/dts/sun8i-h3-orangepi-lite.dts | 23 +----
arch/arm/boot/dts/sun8i-h3-orangepi-one.dts | 23 +----
arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts | 23 +----
arch/arm/boot/dts/sun8i-h3-orangepi-plus.dts | 9 +-
arch/arm/boot/dts/sun8i-r16-parrot.dts | 12 +--
arch/arm/boot/dts/sun8i-reference-design-tablet.dtsi | 12 +--
drivers/gpio/gpiolib.c | 14 +-
drivers/pinctrl/sunxi/pinctrl-sunxi.c | 40 +++---
44 files changed, 110 insertions(+), 662 deletions(-)
base-commit: cf08baa29613dd899954089e7cc7dba1d478b365
--
git-series 0.9.1
next reply other threads:[~2019-03-14 19:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 19:32 Maxime Ripard [this message]
2019-03-14 19:32 ` [PATCH 1/6] gpio: Set proper argument value to set_config Maxime Ripard
2019-04-03 16:41 ` Linus Walleij
2019-04-03 18:36 ` Maxime Ripard
2019-04-04 4:56 ` Linus Walleij
2019-03-14 19:32 ` [PATCH 2/6] pinctrl: sunxi: implement pin_config_set Maxime Ripard
2019-04-04 1:56 ` Linus Walleij
2019-03-14 19:32 ` [PATCH 3/6] pinctrl: sunxi: Fix variable assignment syntax Maxime Ripard
2019-04-04 1:57 ` Linus Walleij
2019-03-14 19:32 ` [PATCH 4/6] pinctrl: sunxi: Declare set_config on the GPIO chip Maxime Ripard
2019-04-04 3:27 ` Linus Walleij
2019-03-14 19:32 ` [PATCH 5/6] ARM: dts: sunxi: Remove pinctrl groups setting bias Maxime Ripard
2019-04-04 3:29 ` Linus Walleij
2019-03-14 19:32 ` [PATCH 6/6] ARM: dts: sunxi: Remove useless pinctrl nodes Maxime Ripard
2019-04-04 3:30 ` Linus Walleij
2019-03-15 2:57 ` [PATCH 0/6] pinctrl: sunxi: Allow to configure pull-up / pull-down from GPIO flags Chen-Yu Tsai
2019-04-02 13:22 ` Maxime Ripard
2019-04-04 7:26 ` Maxime Ripard
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=cover.66d6a9a379de8ebf176e4c25a8542152dc09f366.1552591798.git-series.maxime.ripard@bootlin.com \
--to=maxime.ripard@bootlin.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wens@csie.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).