summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorMichal Simek <monstr@monstr.eu>2009-10-29 09:12:59 (GMT)
committerMichal Simek <monstr@monstr.eu>2009-12-14 07:44:56 (GMT)
commit67bf87665466c4ea93e2c54d66dfd4cdac011a4b (patch)
treebd5379b9eec17b2b6555d2ea9efb1dbb4f8a5593 /arch
parent753758304019fc7c2ef3af674f52a193b1606d15 (diff)
downloadlinux-67bf87665466c4ea93e2c54d66dfd4cdac011a4b.tar.xz
microblaze: Support both levels for reset
Till this patch reset always perform writen to 1. Now we can use negative logic and perform reset write to 0. It is opposite level than is currently read from that pin Signed-off-by: Michal Simek <monstr@monstr.eu>
Diffstat (limited to 'arch')
-rw-r--r--arch/microblaze/kernel/reset.c10
1 files changed, 6 insertions, 4 deletions
diff --git a/arch/microblaze/kernel/reset.c b/arch/microblaze/kernel/reset.c
index 789af93..a1721a3 100644
--- a/arch/microblaze/kernel/reset.c
+++ b/arch/microblaze/kernel/reset.c
@@ -17,6 +17,7 @@
#include <linux/of_gpio.h>
static int handle; /* reset pin handle */
+static unsigned int reset_val;
static int of_reset_gpio_handle(void)
{
@@ -75,9 +76,9 @@ void of_platform_reset_gpio_probe(void)
}
/* get current setup value */
- ret = gpio_get_value(handle);
+ reset_val = gpio_get_value(handle);
/* FIXME maybe worth to perform any action */
- pr_debug("Reset: Gpio output state: 0x%x\n", ret);
+ pr_debug("Reset: Gpio output state: 0x%x\n", reset_val);
/* Setup GPIO as output */
ret = gpio_direction_output(handle, 0);
@@ -87,7 +88,8 @@ void of_platform_reset_gpio_probe(void)
/* Setup output direction */
gpio_set_value(handle, 0);
- printk(KERN_INFO "RESET: Registered gpio device: %d\n", handle);
+ printk(KERN_INFO "RESET: Registered gpio device: %d, current val: %d\n",
+ handle, reset_val);
return;
err:
gpio_free(handle);
@@ -97,7 +99,7 @@ err:
static void gpio_system_reset(void)
{
- gpio_set_value(handle, 1);
+ gpio_set_value(handle, 1 - reset_val);
}
#else
#define gpio_system_reset() do {} while (0)