From: David Daney <ddaney@caviumnetworks.com>
To: David Daney <ddaney.cavm@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: David Daney <david.daney@cavium.com>
Subject: Re: [PATCH 0/3] GPIO: Add driver for ThunderX and OCTEON-TX SoCs
Date: Fri, 6 Jan 2017 15:24:50 -0800 [thread overview]
Message-ID: <82a012d5-1035-91ec-8152-d7b6b5c6e197@caviumnetworks.com> (raw)
In-Reply-To: <1483491334-167095-1-git-send-email-ddaney.cavm@gmail.com>
This version is obsolete. v2 has been sent.
Thanks,
David Daney
On 01/03/2017 04:55 PM, David Daney wrote:
> From: David Daney <david.daney@cavium.com>
>
> The subject says it all. The Cavium ThunderX and OCTEON-TX family of
> SoCs have on-chip GPIO lines. This patch set adds a driver for these.
>
> David Daney (3):
> dt-bindings: gpio: Add binding documentation for gpio-thunderx
> gpio: Add gpio driver support for ThunderX and OCTEON-TX
> MAINTAINERS: Add entry for THUNDERX GPIO Driver.
>
> .../devicetree/bindings/gpio/gpio-thunderx.txt | 33 ++
> MAINTAINERS | 5 +
> drivers/gpio/Kconfig | 7 +
> drivers/gpio/Makefile | 1 +
> drivers/gpio/gpio-thunderx.c | 467 +++++++++++++++++++++
> 5 files changed, 513 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-thunderx.txt
> create mode 100644 drivers/gpio/gpio-thunderx.c
>
prev parent reply other threads:[~2017-01-06 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 0:55 David Daney
2017-01-04 0:55 ` [PATCH 1/3] dt-bindings: gpio: Add binding documentation for gpio-thunderx David Daney
2017-01-04 14:33 ` Rob Herring
2017-01-06 23:26 ` David Daney
2017-01-04 0:55 ` [PATCH 2/3] gpio: Add gpio driver support for ThunderX and OCTEON-TX David Daney
2017-01-04 0:55 ` [PATCH 3/3] MAINTAINERS: Add entry for THUNDERX GPIO Driver David Daney
2017-01-06 23:24 ` David Daney [this message]
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=82a012d5-1035-91ec-8152-d7b6b5c6e197@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®