From: David Daney <ddaney.cavm@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>,
ralf@linux-mips.org, linux-mips@linux-mips.org,
Linus Walleij <linus.walleij@stericsson.com>,
Rob Herring <rob.herring@calxeda.com>,
devicetree-discuss@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, David Daney <david.daney@cavium.com>
Subject: [PATCH 0/2] gpio/MIPS/OCTEON: Add GPIO support for OCTEON.
Date: Thu, 12 Apr 2012 17:10:18 -0700 [thread overview]
Message-ID: <1334275820-7791-1-git-send-email-ddaney.cavm@gmail.com> (raw)
From: David Daney <david.daney@cavium.com>
There are two patches needed to add OCTEON GPIO support:
1) Select ARCH_REQUIRE_GPIOLIB. This allows standard I2C GPIO
expanders to function, as well as being a prerequisite for the driver
for the on-chip pins.
2) The on-chip pin driver.
I'm not sure the best way to merge these, they are part MIPS and part
GPIO. Via either maintainer is fine by me.
Thanks,
David Daney (2):
MIPS: OCTEON: Select ARCH_REQUIRE_GPIOLIB
gpio/MIPS/OCTEON: Add a driver for OCTEON's on-chip GPIO pins.
arch/mips/Kconfig | 1 +
arch/mips/include/asm/mach-cavium-octeon/gpio.h | 21 +++
drivers/gpio/Kconfig | 8 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-octeon.c | 166 +++++++++++++++++++++++
5 files changed, 197 insertions(+), 0 deletions(-)
create mode 100644 arch/mips/include/asm/mach-cavium-octeon/gpio.h
create mode 100644 drivers/gpio/gpio-octeon.c
--
1.7.2.3
next reply other threads:[~2012-04-13 0:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 0:10 David Daney [this message]
2012-04-13 0:10 ` [PATCH 1/2] MIPS: OCTEON: Select ARCH_REQUIRE_GPIOLIB David Daney
2012-04-13 0:10 ` [PATCH 2/2] gpio/MIPS/OCTEON: Add a driver for OCTEON's on-chip GPIO pins David Daney
2012-04-13 9:56 ` Florian Fainelli
2012-04-13 16:17 ` David Daney
2012-04-15 15:21 ` Florian Fainelli
2012-05-17 20:50 ` Grant Likely
2012-05-17 21:37 ` David Daney
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=1334275820-7791-1-git-send-email-ddaney.cavm@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=david.daney@cavium.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rob.herring@calxeda.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
Powered by JetHome