From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/3] pinctrl: Add support for Intel Cannon Lake PCH
Date: Mon, 5 Jun 2017 15:56:47 +0300 [thread overview]
Message-ID: <20170605125650.64188-1-mika.westerberg@linux.intel.com> (raw)
Hi,
This series adds support for the pinctrl and GPIO hardware found on the
next generation Intel Cannon Lake CPUs. We also update the Intel core
pinctrl driver with a concept of hardware pad groups that are needed by the
new driver and make it possible to specify mode per pin instead of the
whole group.
Mika Westerberg (3):
pinctrl: intel: Add support for variable size pad groups
pinctrl: intel: Make it possible to specify mode per pin in a group
pinctrl: intel: Add Intel Cannon Lake PCH pin controller support
drivers/pinctrl/intel/Kconfig | 8 +
drivers/pinctrl/intel/Makefile | 1 +
drivers/pinctrl/intel/pinctrl-cannonlake.c | 442 +++++++++++++++++++++++++++
drivers/pinctrl/intel/pinctrl-intel.c | 195 ++++++++----
drivers/pinctrl/intel/pinctrl-intel.h | 64 +++-
drivers/pinctrl/intel/pinctrl-sunrisepoint.c | 1 +
6 files changed, 647 insertions(+), 64 deletions(-)
create mode 100644 drivers/pinctrl/intel/pinctrl-cannonlake.c
--
2.11.0
next reply other threads:[~2017-06-05 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 12:56 Mika Westerberg [this message]
2017-06-05 12:56 ` [PATCH 1/3] pinctrl: intel: Add support for variable size pad groups Mika Westerberg
2017-06-05 15:11 ` Andy Shevchenko
2017-06-05 12:56 ` [PATCH 2/3] pinctrl: intel: Make it possible to specify mode per pin in a group Mika Westerberg
2017-06-05 12:56 ` [PATCH 3/3] pinctrl: intel: Add Intel Cannon Lake PCH pin controller support Mika Westerberg
2017-06-05 15:20 ` [PATCH 0/3] pinctrl: Add support for Intel Cannon Lake PCH Andy Shevchenko
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=20170605125650.64188-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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