From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ning Li <ning.li@intel.com>, Alan Cox <alan@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support
Date: Mon, 3 Nov 2014 13:01:31 +0200 [thread overview]
Message-ID: <1415012493-134561-1-git-send-email-mika.westerberg@linux.intel.com> (raw)
Hi,
This is second version of the patch series adding pinctrl/GPIO support
for Intel Braswell and Cherrryview. The previous version can be found here:
https://lkml.org/lkml/2014/10/27/118
I've dropped patches [2/4] and [3/4] as they are already applied to the
pinctrl tree.
Changes to the previous version:
[1/2] - Removed unnecessary cast and added Rafael's ACK.
[2/2] - Use Ohms instead of kOhms in pin configuration.
- Change chv_config_set_pull() to be not so convoluted.
- Remove locking when we just read single register. This is not needed.
- Use BIT() instead of (1 << something)
Mika Westerberg (2):
gpio / ACPI: Add knowledge about pin controllers to acpi_get_gpiod()
pinctrl: Add Intel Cherryview/Braswell pin controller support
drivers/gpio/gpiolib-acpi.c | 62 +-
drivers/pinctrl/intel/Kconfig | 12 +
drivers/pinctrl/intel/Makefile | 1 +
drivers/pinctrl/intel/pinctrl-cherryview.c | 1519 ++++++++++++++++++++++++++++
4 files changed, 1591 insertions(+), 3 deletions(-)
create mode 100644 drivers/pinctrl/intel/pinctrl-cherryview.c
--
2.1.1
next reply other threads:[~2014-11-03 11:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 11:01 Mika Westerberg [this message]
2014-11-03 11:01 ` [PATCH v2 1/2] gpio / ACPI: Add knowledge about pin controllers to acpi_get_gpiod() Mika Westerberg
2014-11-04 10:18 ` Linus Walleij
2014-11-03 11:01 ` [PATCH v2 2/2] pinctrl: Add Intel Cherryview/Braswell pin controller support Mika Westerberg
2014-11-04 10:23 ` Linus Walleij
2014-11-03 23:24 ` [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support Timur Tabi
2014-11-04 8:20 ` Mika Westerberg
2014-11-04 9:39 ` Mika Westerberg
2014-11-04 13:31 ` Rafael J. Wysocki
2014-11-04 13:48 ` Linus Walleij
2014-11-04 14:16 ` Rafael J. Wysocki
2014-11-04 14:12 ` Mika Westerberg
2014-11-04 16:37 ` Timur Tabi
2014-11-04 21:51 ` Timur Tabi
2014-11-04 22:47 ` Rafael J. Wysocki
2014-11-04 22:32 ` Timur Tabi
2014-11-04 22:39 ` Timur Tabi
2014-11-04 23:13 ` Rafael J. Wysocki
2014-11-04 22:56 ` Timur Tabi
2014-11-04 23:18 ` Timur Tabi
2014-11-05 21:04 ` Rafael J. Wysocki
2014-11-05 21:19 ` Rafael J. Wysocki
2014-11-04 23:00 ` Rafael J. Wysocki
2014-11-04 17:54 ` Timur Tabi
2014-11-04 19:04 ` Mika Westerberg
2014-11-06 19:30 ` Linus Walleij
2014-11-05 21:46 ` Grant Likely
2014-11-05 21:59 ` Timur Tabi
2014-11-05 22:15 ` Rafael J. Wysocki
2014-11-06 17:37 ` Grant Likely
2014-11-06 18:01 ` Timur Tabi
2014-11-07 23:12 ` Timur Tabi
2014-11-06 19:28 ` Linus Walleij
2014-11-05 21:44 ` Olof Johansson
2014-11-06 6:07 ` 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=1415012493-134561-1-git-send-email-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=ning.li@intel.com \
--cc=rjw@rjwysocki.net \
/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
all inboxes | Powered by JetHome®