mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Semen Protsenko <semen.protsenko@globallogic.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>
Cc: Grant Likely <grant.likely@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, Marc Zyngier <maz@misterjones.org>,
	Grygorii Strashko <grygorii.strashko@globallogic.com>,
	Illia Smyrnov <illia.smyrnov@globallogic.com>
Subject: [PATCH 0/4] gpio: max732x: Update MAX732X driver to use modern kernel API
Date: Tue, 13 Jan 2015 15:41:41 +0200	[thread overview]
Message-ID: <1421156505-16600-1-git-send-email-semen.protsenko@globallogic.com> (raw)

This patch series updates driver for MAX732X I/O expander to use modern kernel
API (like Device Tree). Basically, I was needed this driver to work with
kernel 3.8 on our ARM-based board, but it was in obsolete state (supporting
only platform data from board-file). First patch makes driver work with
data taken from device tree file (old platform data support also kept in place
for compatibility reasons).

After adding device tree support it came to me that current approach to
implement interrupt controller is to use irq-domain framework. Hence the second
patch (only affects the code for generating interrupts on level change on
expander's GPIO input lines).

Once driver became fully functional (using data from device tree), another
issue showed up: lockdep validator revealed possible dead-lock in driver code.
Third patch fixes this problem.

Finally, fourth patch adds binding documentation showing how to describe MAX732X
driver in device tree file.

Semen Protsenko (4):
  gpio: max732x: Add device tree support
  gpio: max732x: Rewrite IRQ code to use irq_domain API
  gpio: max732x: Fix possible deadlock
  gpio: max732x: Add DT binding documentation

 .../devicetree/bindings/gpio/gpio-max732x.txt      |   59 +++++++
 drivers/gpio/Kconfig                               |    1 +
 drivers/gpio/gpio-max732x.c                        |  174 ++++++++++++++------
 3 files changed, 187 insertions(+), 47 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/gpio/gpio-max732x.txt

-- 
1.7.9.5


             reply	other threads:[~2015-01-13 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 13:41 Semen Protsenko [this message]
2015-01-13 13:41 ` [PATCH 1/4] gpio: max732x: Add device tree support Semen Protsenko
2015-01-15 16:52   ` Linus Walleij
2015-01-13 13:41 ` [PATCH 2/4] gpio: max732x: Rewrite IRQ code to use irq_domain API Semen Protsenko
2015-01-15 17:03   ` Linus Walleij
2015-01-13 13:41 ` [PATCH 3/4] gpio: max732x: Fix possible deadlock Semen Protsenko
2015-01-15 17:04   ` Linus Walleij
2015-01-13 13:41 ` [PATCH 4/4] gpio: max732x: Add DT binding documentation Semen Protsenko
2015-01-15 17:19   ` 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=1421156505-16600-1-git-send-email-semen.protsenko@globallogic.com \
    --to=semen.protsenko@globallogic.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gnurou@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=grygorii.strashko@globallogic.com \
    --cc=illia.smyrnov@globallogic.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@misterjones.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®