History log of /drivers/misc/vexpress-syscfg.c
Revision Date Author Comments
f222447ea1b70a651ec280bfb4a2fde4cbeae983 20-Jul-2014 Wei Yongjun <yongjun_wei@trendmicro.com.cn> misc: vexpress: Fix sparse non static symbol warnings

Fixes the following sparse warnings:

drivers/misc/vexpress-syscfg.c:133:22: warning:
symbol 'vexpress_syscfg_regmap_config' was not declared. Should it be static?
drivers/misc/vexpress-syscfg.c:279:5: warning:
symbol 'vexpress_syscfg_probe' was not declared. Should it be static?

Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
b86e1926be37c77deeb176466d98678feab04066 11-Jun-2014 Dan Carpenter <dan.carpenter@oracle.com> mfd: vexpress: fix error handling vexpress_syscfg_regmap_init()

This function should be returning an ERR_PTR() on failure instead of
NULL. Also there is a use after free bug if regmap_init() fails because
we free "func" and then dereference doing the return.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Pawel Moll <pawel.moll@arm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fc96e661a57d5e4de01503d460116cce7ced7e70 11-Jun-2014 Dan Carpenter <dan.carpenter@oracle.com> misc: vexpress: fix error handling vexpress_syscfg_regmap_init()

This function should be returning an ERR_PTR() on failure instead of
NULL. Also there is a use after free bug if regmap_init() fails because
we free "func" and then dereference doing the return.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Pawel Moll <pawel.moll@arm.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
974cc7b93441a0e78f030495436d1be7eb7c208d 23-Apr-2014 Pawel Moll <pawel.moll@arm.com> mfd: vexpress: Define the device as MFD cells

This patch - finally, after over 6 months! :-( - addresses
Samuel's request to split the vexpress-sysreg driver into
smaller portions and define the device in a form of MFD
cells:

* LEDs code has been completely removed and replaced with
"gpio-leds" nodes in the tree (referencing dedicated
GPIO subnodes in sysreg - bindings documentation updated);
this also better fits the reality as some variants of the
motherboard don't have all the LEDs populated

* syscfg bridge code has been extracted into a separate
driver (placed in drivers/misc for no better place)

* all the ID & MISC registers are defined as sysconf
making them available for other drivers should they need
to use them (and also to the user via /sys/kernel/debug/regmap
which can be helpful in platform debugging)

Signed-off-by: Pawel Moll <pawel.moll@arm.com>
Acked-by: Lee Jones <lee.jones@linaro.org>