devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Markus Mayer" <markus.mayer@linaro.org>
To: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Device Tree List <devicetree@vger.kernel.org>,
	Linaro Patches <patches@linaro.org>,
	Christian Daudt <csd@broadcom.com>,
	Tim Kryger <tim.kryger@linaro.org>,
	Matt Porter <matt.porter@linaro.org>,
	Markus Mayer <markus.mayer@linaro.org>,
	ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v5 0/3] ARM: bcm281xx: GPIO driver
Date: Wed, 28 Aug 2013 15:16:10 -0700	[thread overview]
Message-ID: <1377728173-30711-1-git-send-email-markus.mayer@linaro.org> (raw)

This patch series adds the GPIO driver, and its device tree bindings,
for the Broadcom bcm281xx family of chips.

Changes since v4:

- Added "brcm,bcm11351-gpio" to compatible value in device tree binding
- Added references to other device tree documentation
- Explicitly mention 1:1 mapping between GPIO banks and IRQs.
- Select driver in Kconfig, but don't depend on ARCH_BCM & don't default y
- Changed hex numbers to lower case
- Removed irq_base/irq_alloc_descs()/irq_free_descs()
- Added kona_gpio to struct bcm_kona_gpio_bank in lieu of reg_base, so
  interrupt handler can access irq_domain
- Removed bcm_kona_count_irq_resources() and switched to using
  of_irq_count()
- Switched interrupt handler to use irq_find_mapping() instead of
  gpio_to_irq()
- Print no error message if devm_kzalloc() fails
- Don't check return value of platform_get_resource()
- Check for maximum bank number
- Use devm_ioremap_resource() instead of devm_request_and_ioremap()
- Use bit operations rather than spelling out bit shifts
- Added a loop to interrupt handler, so it'll handle IRQs that happened
  during IRQ processing
- Some formatting clean-up

Markus Mayer (3):
  ARM: bcm281xx: Add GPIO driver
  ARM: bcm281xx: Enable GPIO driver
  ARM: bcm281xx: Add device node for the GPIO controller

 .../devicetree/bindings/gpio/gpio-bcm-kona.txt     |   52 ++
 arch/arm/boot/dts/bcm11351.dtsi                    |   16 +
 arch/arm/mach-bcm/Kconfig                          |    2 +-
 drivers/gpio/Kconfig                               |    5 +
 drivers/gpio/Makefile                              |    1 +
 drivers/gpio/gpio-bcm-kona.c                       |  631 ++++++++++++++++++++
 6 files changed, 706 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/gpio/gpio-bcm-kona.txt
 create mode 100644 drivers/gpio/gpio-bcm-kona.c

-- 
1.7.9.5

             reply	other threads:[~2013-08-28 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 22:16 Markus Mayer [this message]
2013-08-28 22:16 ` [PATCH v5 1/3] ARM: bcm281xx: Add GPIO driver Markus Mayer
2013-08-29 18:39   ` Linus Walleij
2013-08-28 22:16 ` [PATCH v5 2/3] ARM: bcm281xx: Enable " Markus Mayer
2013-08-29 18:40   ` Linus Walleij
2013-08-28 22:16 ` [PATCH v5 3/3] ARM: bcm281xx: Add device node for the GPIO controller Markus Mayer

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=1377728173-30711-1-git-send-email-markus.mayer@linaro.org \
    --to=markus.mayer@linaro.org \
    --cc=Sudeep.KarkadaNagesha@arm.com \
    --cc=csd@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=matt.porter@linaro.org \
    --cc=patches@linaro.org \
    --cc=swarren@wwwdotorg.org \
    --cc=tim.kryger@linaro.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;
as well as URLs for NNTP newsgroup(s).