summaryrefslogtreecommitdiff
path: root/include/linux/mfd/stmpe.h
diff options
context:
space:
mode:
authorLinus Walleij <linus.walleij@linaro.org>2012-04-23 14:28:44 +0200
committerSamuel Ortiz <sameo@linux.intel.com>2012-05-09 17:20:29 +0200
commit1379f49ea91a28f5c023d041aab785c3de60c65d (patch)
treefe597bd8825913b294f25fb4271d685451a0f998 /include/linux/mfd/stmpe.h
parent887c8ec7219fc8eba78bb8f44a74c660934e9b98 (diff)
mfd: Allow for const stmpe keyboard data
Since it's not like we will re-arrange the keys at run-time, it seems proper to allow the keymap data to be const. This solves a compilation warning in ux500. Cc: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'include/linux/mfd/stmpe.h')
-rw-r--r--include/linux/mfd/stmpe.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/mfd/stmpe.h b/include/linux/mfd/stmpe.h
index 8516fd1eaabc..f8d5b4d5843f 100644
--- a/include/linux/mfd/stmpe.h
+++ b/include/linux/mfd/stmpe.h
@@ -117,7 +117,7 @@ struct matrix_keymap_data;
* @no_autorepeat: disable key autorepeat
*/
struct stmpe_keypad_platform_data {
- struct matrix_keymap_data *keymap_data;
+ const struct matrix_keymap_data *keymap_data;
unsigned int debounce_ms;
unsigned int scan_count;
bool no_autorepeat;