mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 0/4] pinctrl: Intel Cherryview/Braswell support
Date: Mon, 27 Oct 2014 10:08:28 +0200	[thread overview]
Message-ID: <1414397312-94609-1-git-send-email-mika.westerberg@linux.intel.com> (raw)

[The previous series never reached LKML to misconfiguration in my mailer.
 Resending the whole series with LKML included.]

Hi,

This is a complete rewrite of the GPIO driver patch I sent previously. The
mail thread can be found here:

	http://marc.info/?l=linux-gpio&m=141079024403000&w=2

Outcome of that discussion was that instead of GPIO driver, we should have
a combined pinctrl/GPIO driver.

This patch series implements pinctrl/GPIO driver for Intel
Cherryview/Braswell. While there we decided to put all Intel pinctrl
drivers under drivers/pinctrl/intel/* and add an entry to MAINTAINERS. We
are expecting to have more pinctrl drivers in future for Intel hardware.

Mika Westerberg (4):
  gpio / ACPI: Add knowledge about pin controllers to acpi_get_gpiod()
  pinctrl: Move Intel Baytrail pinctrl driver under intel directory
  MAINTAINERS: Add entry for Intel pin controller drivers
  pinctrl: Add Intel Cherryview/Braswell pin controller support

 MAINTAINERS                                    |    6 +
 drivers/gpio/gpiolib-acpi.c                    |   62 +-
 drivers/pinctrl/Kconfig                        |   13 +-
 drivers/pinctrl/Makefile                       |    2 +-
 drivers/pinctrl/intel/Kconfig                  |   27 +
 drivers/pinctrl/intel/Makefile                 |    4 +
 drivers/pinctrl/{ => intel}/pinctrl-baytrail.c |    0
 drivers/pinctrl/intel/pinctrl-cherryview.c     | 1507 ++++++++++++++++++++++++
 8 files changed, 1605 insertions(+), 16 deletions(-)
 create mode 100644 drivers/pinctrl/intel/Kconfig
 create mode 100644 drivers/pinctrl/intel/Makefile
 rename drivers/pinctrl/{ => intel}/pinctrl-baytrail.c (100%)
 create mode 100644 drivers/pinctrl/intel/pinctrl-cherryview.c

-- 
2.1.1


             reply	other threads:[~2014-10-27  8:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  8:08 Mika Westerberg [this message]
2014-10-27  8:08 ` [PATCH 1/4] gpio / ACPI: Add knowledge about pin controllers to acpi_get_gpiod() Mika Westerberg
2014-10-29 22:11   ` Rafael J. Wysocki
2014-10-30 10:12     ` Mika Westerberg
2014-10-27  8:08 ` [PATCH 2/4] pinctrl: Move Intel Baytrail pinctrl driver under intel directory Mika Westerberg
2014-10-27  8:08 ` [PATCH 3/4] MAINTAINERS: Add entry for Intel pin controller drivers Mika Westerberg
2014-10-27  8:08 ` [PATCH 4/4] pinctrl: Add Intel Cherryview/Braswell 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=1414397312-94609-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

Powered by JetHome