GPIO keys - Revision history

FabienM: /* Introduction */

2017-06-21T14:52:25Z

Introduction

← Older revision		Revision as of 16:52, 21 June 2017
Line 7:		Line 7:
	* APF28: PINID_GPMI_CE1N (Bank 0 - bit 17)		* APF28: PINID_GPMI_CE1N (Bank 0 - bit 17)
	* APF51: GPIO1_3		* APF51: GPIO1_3
			* OPOS6ULDEV: GPIO2_11

	==Configuration==		==Configuration==

SebastienSz: /* With device tree */

2013-12-03T13:38:37Z

With device tree

← Older revision		Revision as of 15:38, 3 December 2013
Line 98:		Line 98:
	fsl,pinmux-ids = <		fsl,pinmux-ids = <
	...		...
	0x0113 /* MX28_PAD_GPMI_CE1N__GPIO_0_17 - the user ~~botton~~ on the apf28dev */		0x0113 /* MX28_PAD_GPMI_CE1N__GPIO_0_17 - the user button on the apf28dev */
	...		...
	>;		>;

SebastienSz at 13:38, 3 December 2013

2013-12-03T13:38:07Z

← Older revision		Revision as of 15:38, 3 December 2013
Line 78:		Line 78:
	left-key {		left-key {
	label = "Left key";		label = "Left key";
	gpios = <&~~gpio1 18~~ 0>;		gpios = <&gpio0 17 0>;
	linux,code = <69>; /* KEY_LEFT */		linux,code = <69>; /* KEY_LEFT */
	};		};
Line 98:		Line 98:
	fsl,pinmux-ids = <		fsl,pinmux-ids = <
	...		...
	~~0x1123~~ /* ~~MX28_PAD_LCD_D18__GPIO_1_18~~ */		0x0113 /* MX28_PAD_GPMI_CE1N__GPIO_0_17 - the user botton on the apf28dev */
	...		...
	>;		>;

GwenhaelG: /* With device tree */

2013-02-02T15:40:14Z

With device tree

← Older revision		Revision as of 17:40, 2 February 2013
Line 69:		Line 69:

	=== With device tree ===		=== With device tree ===
	This description is based to the APF28dev board.		This description is based to the APF28dev board and the modifications must be done into buildroot/output/build/linux-xxx/arch/arm/boot/dts/imx28-apf28dev.dts.

	To define gpio-keys, you need to add a node and a sub-node after all peripheral nodes :		To define gpio-keys, you need to add a node and a sub-node after all peripheral nodes :

GwenhaelG at 18:17, 29 January 2013

2013-01-29T18:17:29Z

@@ Line 20: / Line 20: @@
 </pre>
 Then, in your ''apfXX-dev.c'', you would need to define your GPIO button <b>before</b> the variable ''platform_devices[]'' and also include gpio_keys.h and input.h. his code is already implemented for the APF27, APF28 and APF51 so the source code hereafter (for the APF27) is only present as a reference sample to understand how to activate a GPIO KEY driver.
@@ Line 66: / Line 67: @@
 };
 </source>
 ==Usage==

Jorasse at 21:49, 16 May 2012

2012-05-16T21:49:26Z

← Older revision		Revision as of 23:49, 16 May 2012
Line 67:		Line 67:
	</source>		</source>

	==~~Test~~==		==Usage==
	<pre class="apf">		<pre class="apf">
	# cat /dev/input/event0		# cat /dev/input/event0
Line 102:		Line 102:

	</pre>		</pre>

			==Links==
			http://www.kernel.org/doc/Documentation/input/

	[[Category:UserInput]]		[[Category:UserInput]]

Jorasse at 21:44, 16 May 2012

2012-05-16T21:44:26Z

@@ Line 8: / Line 8: @@
 * APF51: GPIO1_3
-==Test==
+==Configuration==
 First, you need to enable the gpio_keys in your kernel.
@@ Line 56: / Line 20: @@
 </pre>
-Then, in your ''apf27-dev.c'', you need to define your GPIO button <b>before</b> the variable ''platform_devices[]'' and also include gpio_keys.h and input.h.
+Then, in your ''apfXX-dev.c'', you would need to define your GPIO button <b>before</b> the variable ''platform_devices[]'' and also include gpio_keys.h and input.h. his code is already implemented for the APF27, APF28 and APF51 so the source code hereafter (for the APF27) is only present as a reference sample to understand how to activate a GPIO KEY driver.
 <source lang="c">
@@ Line 102: / Line 66: @@
 };
 </source>
 [[Category:UserInput]]

Jorasse: /* For APF27 */

2012-05-14T18:14:19Z

For APF27

← Older revision		Revision as of 20:14, 14 May 2012
Line 65:		Line 65:
	<source lang="c">		<source lang="c">
	/* GPIO KEYS */		/* GPIO KEYS */
	#if 1		#if defined(CONFIG_KEYBOARD_GPIO) \|\| defined(CONFIG_KEYBOARD_GPIO_MODULE)
			static struct gpio_keys_button apf27dev_gpio_keys[] = {
	~~/* PORTA_6 used as gpio_keys~~ (~~GPIO used as input event~~) */
	static struct gpio_keys_button ~~apf27_gpio_keys~~[] = {
	{		{
	.code = ~~EV_PWR~~, /* See include/linux/input.h ~~for more event code~~ */		.code = BTN_EXTRA, /* See include/linux/input.h */
	.gpio = (~~GPIO_PORTA~~ \| 6), /* GPIO number */		.gpio = (GPIO_PORTF \| 13), /* GPIO number */
	.active_low = 0,		.active_low = 1,
	.desc = "~~Notification when the AC is deconnected~~", /* Button description*/		.desc = "s1", /* Button description*/
	.~~type~~ = 0, ~~/* See include/linux/input.h for more type code */~~		.wakeup = 0,
	},		},
	};		};

	static struct gpio_keys_platform_data ~~apf27_gpio_keys_data~~ = {		static struct gpio_keys_platform_data apf27dev_gpio_keys_data = {
	.buttons = ~~apf27_gpio_keys~~,		.buttons = apf27dev_gpio_keys,
	.nbuttons = ARRAY_SIZE(~~apf27_gpio_keys~~),		.nbuttons = ARRAY_SIZE(apf27dev_gpio_keys),
	};		};

	static struct platform_device ~~apf27_gpio_keys_device~~ = {		static struct platform_device apf27dev_gpio_keys_device = {
	.name = "gpio-keys",		.name = "gpio-keys",
	.id = 0,		.id = -1,
	.dev = {		.dev = {
	.platform_data = &~~apf27_gpio_keys_data~~,		.platform_data = &apf27dev_gpio_keys_data,
	},		},
	};		};
	# ~~define GPIO_KEYS &apf27_gpio_keys_device,~~		#endif /* CONFIG_KEYBOARD_GPIO */
	~~#else~~
	~~# define GPIO_KEYS~~
	~~#endif~~
	</source>		</source>

Line 100:		Line 96:
	<source lang="c">		<source lang="c">
	static struct platform_device *platform_devices[] __initdata = {		static struct platform_device *platform_devices[] __initdata = {
			#if defined(CONFIG_KEYBOARD_GPIO) \|\| defined(CONFIG_KEYBOARD_GPIO_MODULE)
			&apf27dev_gpio_keys_device,
			#endif
	ALSA_SOUND		ALSA_SOUND
	~~GPIO_KEYS~~
	};		};
	</source>		</source>

	[[Category:UserInput]]		[[Category:UserInput]]

Jorasse at 18:01, 14 May 2012

2012-05-14T18:01:08Z

← Older revision		Revision as of 20:01, 14 May 2012
Line 1:		Line 1:

	==Introduction==		==Introduction==

Line 6:		Line 5:
	Here are the GPIO used for the user button/switch for each APF board:		Here are the GPIO used for the user button/switch for each APF board:
	* APF27: GPIO_PORTF \| 13		* APF27: GPIO_PORTF \| 13
	* APF28: PINID_GPMI_CE1N		* APF28: PINID_GPMI_CE1N (Bank 0 - bit 17)
	* APF51: GPIO1_3		* APF51: GPIO1_3

Jorasse: generalize to the APF27, 28 and 51 boards

2012-05-14T17:05:19Z

generalize to the APF27, 28 and 51 boards

← Older revision		Revision as of 19:05, 14 May 2012
Line 1:		Line 1:
	~~How to use gpio-keys driver to read states of the user switch of your Armadeus board (APF51)~~

	==Introduction==		==Introduction==

	Your APF51 board ~~features~~ a user switch connected to a GPIO pin ~~(GPIO1_3)~~. The driver gpio-keys translates GPIO events in key/button events.		How to use gpio-keys driver to read states of the user switch of your Armadeus board.
			Your APF51\|APF27\|APF28 development board feature a user switch connected to a GPIO pin. The driver gpio-keys translates GPIO events in key/button events.
			Here are the GPIO used for the user button/switch for each APF board:
			* APF27: GPIO_PORTF \| 13
			* APF28: PINID_GPMI_CE1N
			* APF51: GPIO1_3

	==Test==		==Test==