From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"David E . Box" <david.e.box@linux.intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: [PATCH v2 0/6] pinctrl: Fixes and updates to Intel drivers
Date: Tue, 10 Jan 2017 17:31:55 +0300 [thread overview]
Message-ID: <20170110143201.53539-1-mika.westerberg@linux.intel.com> (raw)
This series fixes one issue found on Broxton, updates the core driver to
use devm_gpiochip_add_data() and finally add support for the next
generation Intel GPIO hardware available starting from Intel Gemini Lake SoC.
The Gemini Lake SoC brings hardware debouncer per-pad and 1k additional
pull-down. In order to configure the hardware debouncer, this series adds a
new function to pinctrl core; pinctrl_gpio_set_config(). This function can
be used by gpiolib-based GPIO drivers to ask the backing pinctrl driver to
apply certain configuration, like setting debounce time.
Changes from v1:
* Added Reviewed-by from Andy
* Use goto exit_unlock in intel_config_set_debounce()
* Features are now prefixed with PINCTRL_FEATURE_*
Mika Westerberg (6):
pinctrl: broxton: Use correct PADCFGLOCK offset
pinctrl: intel: Convert to use devm_gpiochip_add_data()
pinctrl: Add a possibility to configure pins from a gpiolib based drivers
pinctrl: intel: Add support for hardware debouncer
pinctrl: intel: Add support for 1k additional pull-down
pinctrl: intel: Add Intel Gemini Lake pin controller support
drivers/pinctrl/core.c | 28 ++
drivers/pinctrl/intel/Kconfig | 8 +
drivers/pinctrl/intel/Makefile | 1 +
drivers/pinctrl/intel/pinctrl-broxton.c | 3 +-
drivers/pinctrl/intel/pinctrl-geminilake.c | 512 +++++++++++++++++++++++++++
drivers/pinctrl/intel/pinctrl-intel.c | 178 ++++++++--
drivers/pinctrl/intel/pinctrl-intel.h | 8 +-
drivers/pinctrl/intel/pinctrl-sunrisepoint.c | 1 -
drivers/pinctrl/pinconf.c | 12 +
drivers/pinctrl/pinconf.h | 10 +
include/linux/pinctrl/consumer.h | 8 +
11 files changed, 744 insertions(+), 25 deletions(-)
create mode 100644 drivers/pinctrl/intel/pinctrl-geminilake.c
--
2.11.0
next reply other threads:[~2017-01-10 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:31 Mika Westerberg [this message]
2017-01-10 14:31 ` [PATCH v2 1/6] pinctrl: broxton: Use correct PADCFGLOCK offset Mika Westerberg
2017-01-11 12:47 ` Linus Walleij
2017-01-10 14:31 ` [PATCH v2 2/6] pinctrl: intel: Convert to use devm_gpiochip_add_data() Mika Westerberg
2017-01-11 12:53 ` Linus Walleij
2017-01-10 14:31 ` [PATCH v2 3/6] pinctrl: Add a possibility to configure pins from a gpiolib based drivers Mika Westerberg
2017-01-11 13:06 ` Linus Walleij
2017-01-11 13:33 ` Mika Westerberg
2017-01-12 9:22 ` Mika Westerberg
2017-01-13 15:36 ` Linus Walleij
2017-01-13 16:33 ` Mika Westerberg
2017-01-18 9:26 ` Linus Walleij
2017-01-10 14:31 ` [PATCH v2 4/6] pinctrl: intel: Add support for hardware debouncer Mika Westerberg
2017-01-10 14:32 ` [PATCH v2 5/6] pinctrl: intel: Add support for 1k additional pull-down Mika Westerberg
2017-01-10 14:32 ` [PATCH v2 6/6] pinctrl: intel: Add Intel Gemini Lake pin controller support Mika Westerberg
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=20170110143201.53539-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=david.e.box@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;
as well as URLs for NNTP newsgroup(s).