linux-kernel - [PATCH v3 0/1] Pinctrl/gpio driver for Intel Baytrail platforms

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1371555182-12418-1-git-send-email-mathias.nyman@linux.intel.com>
Date:	Tue, 18 Jun 2013 14:33:01 +0300
From:	Mathias Nyman <mathias.nyman@...ux.intel.com>
To:	Linus <linus.walleij@...aro.org>
Cc:	<grant.likely@...retlab.ca>, <linux-kernel@...r.kernel.org>,
	Mathias Nyman <mathias.nyman@...ux.intel.com>
Subject: [PATCH v3 0/1] Pinctrl/gpio driver for Intel Baytrail platforms

This is the third version of the Intel baytrail GPIO driver, now moved to Pinctrl
subsystem.

As Linus W. pointed out the Intel Baytrail gpio looks more like a pin controller with
pad muxing and gpio-to-pad mappings than a pure gpio controller.
Even if firmware does its best to make sure we don't need to worry about the muxings
and other pinctrl features, there's a possibility these features might be useful in
the future and then pinctrl is easier to build on. 

Pinctrl also provides some generic gpio structures that are useful for this driver.        

This driver is built on top of linux-pinctrl tree and needs the 
"pinctrl: add pin list based GPIO ranges" patch by Christian Ruppert
(commit 2ff3477efd7086544b9e298fc63afab0645921b4)

Changes since v2:
- move driver from gpio/gpio-baytrail to drivers/pinctrl/pinctrl-baytrail
- use generic pinctrl_gpio_range structures from pinctrl instead of custom gpio_banks

Changes since v1:
- generic cleanups suggested by Andy S.
- removed text about pin muxing
- added missing 44:th pin to SUS controller
- added level triggering option
- prevent "forever loop" in case pin is stuck in "interrupt triggered" status,     

Mathias Nyman (1):
  pinctrl: add Intel BayTrail GPIO/pinctrl support

 drivers/pinctrl/Kconfig            |   12 +
 drivers/pinctrl/Makefile           |    1 +
 drivers/pinctrl/pinctrl-baytrail.c |  543 ++++++++++++++++++++++++++++++++++++
 3 files changed, 556 insertions(+), 0 deletions(-)
 create mode 100644 drivers/pinctrl/pinctrl-baytrail.c

-- 
1.7.4.1

--
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/