[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1436862596-27730-1-git-send-email-tomeu.vizoso@collabora.com>
Date: Tue, 14 Jul 2015 10:29:53 +0200
From: Tomeu Vizoso <tomeu.vizoso@...labora.com>
To: linux-kernel@...r.kernel.org
Cc: linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org,
Tomeu Vizoso <tomeu.vizoso@...labora.com>,
Thierry Reding <thierry.reding@...il.com>,
Russell King <linux@....linux.org.uk>,
Linus Walleij <linus.walleij@...aro.org>,
Kumar Gala <galak@...eaurora.org>,
Stephen Warren <swarren@...dotorg.org>,
Grant Likely <grant.likely@...aro.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Alexandre Courbot <gnurou@...il.com>,
linux-arm-kernel@...ts.infradead.org
Subject: [PATCH v2 0/3] Have Tegra's GPIO chip depend explicitly on the pinctrl device
Hello,
these three patches make sure that there's an explicit dependency from
the GPIO chip in Tegra SoCs to the corresponding pinctrl device, without
having duplicated gpio ranges.
By having an explicit dependency, we can do things such as probing the
pinctrl device before the GPIO chip device to avoid deferred probes.
Thanks,
Tomeu
Changes in v2:
- Don't defer probe if the pinctrl node is disabled
- Remove outdated comment from the commit changelog
Tomeu Vizoso (3):
gpio: defer probe if pinctrl cannot be found
pinctrl: tegra: Only set the gpio range if needed
ARM: tegra: Add gpio-ranges property
arch/arm/boot/dts/tegra114.dtsi | 1 +
arch/arm/boot/dts/tegra124.dtsi | 1 +
arch/arm/boot/dts/tegra20.dtsi | 1 +
arch/arm/boot/dts/tegra30.dtsi | 1 +
drivers/gpio/gpiolib-of.c | 27 ++++++++++++++++++---------
drivers/gpio/gpiolib.c | 5 ++++-
drivers/pinctrl/pinctrl-tegra.c | 19 ++++++++++++++++++-
include/linux/of_gpio.h | 4 ++--
8 files changed, 46 insertions(+), 13 deletions(-)
--
2.4.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists