Hi Linus, This is updated pull request with one additional patch from Marek. I saw you did not pull my previous pull request for v4.18 so I hope this update should not be a problem. Anyway it is on top of previous request (no rebase) so it can be also applied incrementally. Best regards, Krzysztof The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) are available in the git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/samsung.git tags/samsung-pinctrl-4.18-2 for you to fetch changes up to 7c24e71c8a6423dfa5a7f19b253726b23af0c507: pinctrl: samsung: Fix suspend/resume for Exynos5433 GPF1..5 banks (2018-05-23 21:23:19 +0200) ---------------------------------------------------------------- Samsung pinctrl drivers changes for v4.18 1. Driver expects specific order of GPIO interrupt banks. For S5Pv220 and Exynos5410 this order was not preserved so fix and document it. 2. Remove support for Exynos5440 (tree-wide, support is dropped because there are no real users of this platform, it also did not get testing since long time). 3. Fix lost state of GPF1..5 pins on Exynos5433 during system suspend. ---------------------------------------------------------------- Krzysztof Kozlowski (1): pinctrl: samsung: Remove support for Exynos5440 Marek Szyprowski (1): pinctrl: samsung: Fix suspend/resume for Exynos5433 GPF1..5 banks Paweł Chmiel (2): pinctrl: samsung: Correct EINTG banks order pinctrl: samsung: Document required order of banks drivers/pinctrl/samsung/Kconfig | 10 +- drivers/pinctrl/samsung/Makefile | 1 - drivers/pinctrl/samsung/pinctrl-exynos-arm.c | 30 +- drivers/pinctrl/samsung/pinctrl-exynos-arm64.c | 20 + drivers/pinctrl/samsung/pinctrl-exynos.h | 2 +- drivers/pinctrl/samsung/pinctrl-exynos5440.c | 1005 ------------------------ 6 files changed, 51 insertions(+), 1017 deletions(-) delete mode 100644 drivers/pinctrl/samsung/pinctrl-exynos5440.c -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html