Commit 9747e78b authored by Magnus Damm's avatar Magnus Damm Committed by Paul Mundt

sh: use in-soc KEYSC on se7724

This patch updates the Solution Engine 7724 board code to use
in-SoC KEYSC resources for the keyboard platform device. Using
the in-SoC key scan controller fixes a crash-during-resume issue.

Without this patch the KEYSC hardware block located in the board
specific FPGA is used together with an external IRQ which is
routed through the FPGA and handled by some board specific demux
code. This board specific FPGA interrupt code does not implement
desc->set_wake() so the enable_irq_wake() call in the sh_keysc
driver will fail at suspend-to-ram time and the disable_irq_wake()
will bomb out when resuming.

Changing the platform data to use the in-SoC KEYSC hardware makes
the se7724 board support code less special which is a good thing.
Also, the board specific KEYSC pin setup code selects in-SoC pin
functions already which makes the current FPGA platform device data
look like a typo.
Signed-off-by: default avatarMagnus Damm <damm@igel.co.jp>
Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
parent f6431732
...@@ -238,7 +238,7 @@ static struct platform_device ceu1_device = { ...@@ -238,7 +238,7 @@ static struct platform_device ceu1_device = {
}, },
}; };
/* KEYSC */ /* KEYSC in SoC (Needs SW33-2 set to ON) */
static struct sh_keysc_info keysc_info = { static struct sh_keysc_info keysc_info = {
.mode = SH_KEYSC_MODE_1, .mode = SH_KEYSC_MODE_1,
.scan_timing = 10, .scan_timing = 10,
...@@ -255,12 +255,13 @@ static struct sh_keysc_info keysc_info = { ...@@ -255,12 +255,13 @@ static struct sh_keysc_info keysc_info = {
static struct resource keysc_resources[] = { static struct resource keysc_resources[] = {
[0] = { [0] = {
.start = 0x1a204000, .name = "KEYSC",
.end = 0x1a20400f, .start = 0x044b0000,
.end = 0x044b000f,
.flags = IORESOURCE_MEM, .flags = IORESOURCE_MEM,
}, },
[1] = { [1] = {
.start = IRQ0_KEY, .start = 79,
.flags = IORESOURCE_IRQ, .flags = IORESOURCE_IRQ,
}, },
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment