linux-kernel - [RFC PATCH 0/3] GPIO switch framework

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: <1237557050-13742-1-git-send-email-ext-jani.1.nikula@nokia.com>
Date:	Fri, 20 Mar 2009 15:50:47 +0200
From:	Jani Nikula <ext-jani.1.nikula@...ia.com>
To:	david-b@...bell.net
Cc:	linux-kernel@...r.kernel.org, juha.yrjola@...idboot.com,
	ext-jani.1.nikula@...ia.com
Subject: [RFC PATCH 0/3] GPIO switch framework


Hi -

This RFC patchset is a pretty straightforward adaptation of OMAP GPIO
switch framework for mainline integration.

The GPIO switch framework allows reporting and changing GPIO switches
via sysfs, with debouncing and sysfs/in-kernel notifications for input
switches.

The switches are added as /sys/class/gpio/switch-<switch name> under
the gpiolib sysfs structure.


BR,
Jani.


Jani Nikula (3):
      GPIOLIB: Add new gpio_device_create function
      GPIO-SWITCH: Adaptation of GPIO switch framework for mainline
      GPIO-SWITCH: Kconfig and Makefile

 drivers/gpio/Kconfig        |   10 +
 drivers/gpio/Makefile       |    2 +
 drivers/gpio/gpio-switch.c  |  534 +++++++++++++++++++++++++++++++++++++++++++
 drivers/gpio/gpiolib.c      |   52 +++++
 include/asm-generic/gpio.h  |   12 +
 include/linux/gpio-switch.h |   74 ++++++
 6 files changed, 684 insertions(+), 0 deletions(-)
 create mode 100644 drivers/gpio/gpio-switch.c
 create mode 100644 include/linux/gpio-switch.h
--
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/