From: Jan Kotas <jank@cadence.com>
To: <linus.walleij@linaro.org>, <bgolaszewski@baylibre.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>
Cc: <linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Jan Kotas <jank@cadence.com>
Subject: [PATCH v2 0/2] gpio: Add a driver for Cadence GPIO controller
Date: Mon, 17 Dec 2018 15:36:50 +0000 [thread overview]
Message-ID: <20181217153652.20056-1-jank@cadence.com> (raw)
This patchset adds a driver support for Cadence GPIO controller.
Number of supported lines is configurable.
The driver initializes all pins as inputs in probe().
Currently it only supports level-sensitive interrupts.
The interrupts controller was tested with I2C and SPI IPs
acting as interrupt sources.
Changes since V1:
Switched to generic GPIO infrastructure.
Redesigned interrupts, now uses chained irqchip.
Drop support for edge-sensitive interrupts.
Restore bypass settings at unexport/remove.
Jan Kotas (2):
dt-bindings: gpio: Add bindings for Cadence GPIO
gpio: Add Cadence GPIO driver
.../devicetree/bindings/gpio/cdns,gpio.txt | 44 ++++
drivers/gpio/Kconfig | 8 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-cadence.c | 275 +++++++++++++++++++++
4 files changed, 328 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/cdns,gpio.txt
create mode 100644 drivers/gpio/gpio-cadence.c
--
2.15.0
next reply other threads:[~2018-12-17 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 15:36 Jan Kotas [this message]
2018-12-17 15:36 ` [PATCH v2 1/2] dt-bindings: gpio: Add bindings for Cadence GPIO Jan Kotas
2018-12-18 17:33 ` Rob Herring
2018-12-17 15:36 ` [PATCH v2 2/2] gpio: Add Cadence GPIO driver Jan Kotas
2018-12-17 15:51 ` Bartosz Golaszewski
2018-12-17 22:21 ` Linus Walleij
2018-12-18 12:50 ` Bartosz Golaszewski
2018-12-18 13:54 ` Janek Kotas
2018-12-18 14:06 ` Bartosz Golaszewski
2018-12-21 10:37 ` Linus Walleij
2018-12-21 10:34 ` Linus Walleij
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=20181217153652.20056-1-jank@cadence.com \
--to=jank@cadence.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--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®