linux-kernel - [PATCH v4 0/3] implement pinmux for arch-mmp

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: <1325643995-20745-1-git-send-email-haojian.zhuang@marvell.com>
Date:	Wed,  4 Jan 2012 10:26:32 +0800
From:	Haojian Zhuang <haojian.zhuang@...vell.com>
To:	linus.walleij@...aro.org, swarren@...dia.com,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	eric.y.miao@...il.com, linux@....linux.org.uk, arnd@...db.de
Subject: [PATCH v4 0/3] implement pinmux for arch-mmp

#1 & #2 patch are based on pinctrl/for-next branch.
#3 patch is based on arm-soc/for-next branch since it replies the new pxa-gpio
driver.

Changelog v4->v3:
1. Rename PINMUX_* to PINCTRL_*.
2. Remove the CONFIG_PINMUX in pxa-gpio driver.

Changelog v3->v2:
1. Avoid to use number in groups definition. Use macro instead.
2. Replace func array with mux array. There's a risk of align func array
and group array. Both pin and mux are defined in new mux array.
3. Support gpio again in gpio-pxa.
4. If multiple pins can be configured to same GPIO pin, define new specific
gpio group.

Changelog v1->v2:
1. Split pxa3xx pinmux driver to more pieces.
2. Add PXA168/PXA910/PXA930/MMP2 silicon support.
3. Now only enable it in arch-mmp.
4. Now all predefined pins are enabled by default. Although some devices
are not used, they would be declared in arch-pxa. It would result define
unnecessary pins in platform.
5. Remove gpio support since it's depend on some gpio-pxa patches in
arm-soc trees.

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