linux-kernel - [RFC PATCH 0/7] gpio: extend basic_mmio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1302088263-12714-1-git-send-email-jamie@jamieiles.com>
Date:	Wed,  6 Apr 2011 12:10:56 +0100
From:	Jamie Iles <jamie@...ieiles.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux@....linux.org.uk, tglx@...utronix.de, cbouatmailru@...il.com,
	grant.likely@...retlab.ca, arnd@...db.de, nico@...xnic.net,
	Jamie Iles <jamie@...ieiles.com>
Subject: [RFC PATCH 0/7] gpio: extend basic_mmio_gpio for different controllers

This patch series extends the basic_mmio_gpio driver to support
controllers with different register sets and number of GPIOs.  There are
also changes to configure more at probe time rather than runtime
evaluation.

I've tested this on an out-of-tree platform with a Synopsys DesignWare
GPIO controller.

Jamie Iles (7):
  basic_mmio_gpio: remove runtime width/endianness evaluation
  basic_mmio_gpio: convert to platform_{get,set}_drvdata()
  basic_mmio_gpio: allow overriding number of gpio
  basic_mmio_gpio: request register regions
  basic_mmio_gpio: detect output method at probe time
  basic_mmio_gpio: support different input/output registers
  basic_mmio_gpio: support direction registers

 drivers/gpio/basic_mmio_gpio.c  |  386 ++++++++++++++++++++++++++++++--------
 include/linux/basic_mmio_gpio.h |    1 +
 2 files changed, 305 insertions(+), 82 deletions(-)

-- 
1.7.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/