linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini@gnudd.com>
To: linux-kernel@vger.kernel.org
Cc: Giancarlo Asnaghi <giancarlo.asnaghi@st.com>,
	Alan Cox <alan@linux.intel.com>,
	sameo@linux.intel.com, grant.likely@secretlab.ca,
	linus.walleij@stericsson.com
Subject: [PATCH V3 0/2] MFD and GPIO for STA2X11
Date: Thu, 12 Apr 2012 10:48:32 +0200	[thread overview]
Message-ID: <cover.1334219873.git.rubini@gnudd.com> (raw)

These two patches introduce the multi-function device and GPIO support for
the STA2X11 I/O Hub.  Core PCI support is already in linux-next.

V1: sent on Jan 26th as RFC and got no comments back

V2: sent on Feb 16th, fixed a number of minor details, got comments from
Linus Walleij and Samuel Ortiz.

V3: accepted all suggestions.  I delayed this resending a while because
I hoped the base STA2X11 patches to be accepted, but despite the positive
comments I got on those patches, they are not in linux-next as of today

This set, thus, refers to CONFIG_STA2X11 which is not yet upstream.linux-next.

Like in V2, I Cc'd both patches to all interested parties, because
the MFD patch must be fore the GPIO one, so they're better merged to
the same tree.

Alessandro Rubini (2):
  mfd: Add driver for STA2X11 MFD block
  gpio: add STA2X11 GPIO block

 arch/x86/include/asm/sta2x11.h  |   12 +
 drivers/gpio/Kconfig            |    8 +
 drivers/gpio/Makefile           |    1 +
 drivers/gpio/gpio-sta2x11.c     |  435 ++++++++++++++++++++++++++++++++++++
 drivers/mfd/Kconfig             |    6 +
 drivers/mfd/Makefile            |    1 +
 drivers/mfd/sta2x11-mfd.c       |  467 +++++++++++++++++++++++++++++++++++++++
 include/linux/mfd/sta2x11-mfd.h |  324 +++++++++++++++++++++++++++
 8 files changed, 1254 insertions(+), 0 deletions(-)
 create mode 100644 arch/x86/include/asm/sta2x11.h
 create mode 100644 drivers/gpio/gpio-sta2x11.c
 create mode 100644 drivers/mfd/sta2x11-mfd.c
 create mode 100644 include/linux/mfd/sta2x11-mfd.h

-- 
1.7.7.2

             reply	other threads:[~2012-04-12  8:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  8:48 Alessandro Rubini [this message]
2012-04-12  8:48 ` [PATCH V3 1/2] mfd: Add driver for STA2X11 MFD block Alessandro Rubini
2012-04-16 18:05   ` Samuel Ortiz
2012-04-16 18:11   ` Alessandro Rubini
2012-05-09 13:37   ` Samuel Ortiz
2012-04-12  8:48 ` [PATCH V3 2/2] gpio: add STA2X11 GPIO block Alessandro Rubini
2012-04-12 15:05   ` Linus Walleij
2012-04-13 11:44   ` Alessandro Rubini
2012-04-13 12:32     ` Linus Walleij
2012-04-13 16:34   ` Linus Walleij
2012-05-09 13:40   ` Samuel Ortiz
2012-05-11 23:34   ` Grant Likely
2012-05-14  7:25   ` Alessandro Rubini
2012-05-14  9:47     ` Mark Brown
2012-05-14  9:51     ` Alessandro Rubini
2012-05-14  9:58       ` Mark Brown
2012-05-14 10:06       ` Alessandro Rubini
2012-05-14 10:08         ` Mark Brown
2012-05-18  9:10     ` Samuel Ortiz
2012-04-16 17:55 ` [PATCH V3 0/2] MFD and GPIO for STA2X11 Samuel Ortiz

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=cover.1334219873.git.rubini@gnudd.com \
    --to=rubini@gnudd.com \
    --cc=alan@linux.intel.com \
    --cc=giancarlo.asnaghi@st.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /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).