From: krzk@kernel.org (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] pinctrl: samsung: Stuff for v4.18
Date: Sat, 19 May 2018 17:55:47 +0200 [thread overview]
Message-ID: <20180519155547.6678-1-krzk@kernel.org> (raw)
Hi Linus,
Few patches for next cycle.
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
for you to fetch changes up to 0ca0557e3727951bdc44ea47bc6135b37f90338c:
pinctrl: samsung: Remove support for Exynos5440 (2018-05-02 19:08:55 +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).
----------------------------------------------------------------
Krzysztof Kozlowski (1):
pinctrl: samsung: Remove support for Exynos5440
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-exynos5440.c | 1005 ------------------------
5 files changed, 50 insertions(+), 1016 deletions(-)
delete mode 100644 drivers/pinctrl/samsung/pinctrl-exynos5440.c
reply other threads:[~2018-05-19 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180519155547.6678-1-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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