Hammer LED Class Driver - Revision history

Jsujjava: Change to Category TCT-Hammer

2011-05-14T16:47:48Z

Change to Category TCT-Hammer

Jsujjava: Add Category Hammer

2011-05-13T17:50:27Z

Add Category Hammer

Pat123: /* Adding New LEDS */

2009-06-10T23:43:39Z

‎Adding New LEDS

Pat123: /* Adding New LEDS */

2009-06-10T23:42:44Z

‎Adding New LEDS

Pat123: /* Adding New LEDS */

2009-06-10T23:40:54Z

‎Adding New LEDS

Prpplague at 20:37, 16 June 2008

2008-06-16T20:37:13Z

Prpplague at 19:58, 16 June 2008

2008-06-16T19:58:40Z

Prpplague at 15:20, 12 May 2008

2008-05-12T15:20:59Z

Prpplague: Hammer LED Driver moved to Hammer LED Class Driver: this information is geared towards the LED Class driver

2008-05-12T15:16:24Z

Hammer LED Driver moved to Hammer LED Class Driver: this information is geared towards the LED Class driver

Prpplague at 15:17, 29 January 2008

2008-01-29T15:17:10Z

← Older revision		Revision as of 16:47, 14 May 2011
Line 157:		Line 157:
	</pre>		</pre>

−	[[Category:Hammer]]	+	[[Category:TCT-Hammer]]

← Older revision		Revision as of 17:50, 13 May 2011
Line 156:		Line 156:

	</pre>		</pre>
		+
		+	[[Category:Hammer]]

@@ Line 57: / Line 57: @@
 </pre>
-Reflash Kernel
+Now you can reflash the Kernel.
 this uses the standard LEDS class in the main kernel tree. for additional information see the linux-2.6.xx/Documentation/leds-class.txt file.

← Older revision		Revision as of 23:42, 10 June 2009
Line 57:		Line 57:
	</pre>		</pre>

		+	Reflash Kernel
	this uses the standard LEDS class in the main kernel tree. for additional information see the linux-2.6.xx/Documentation/leds-class.txt file.		this uses the standard LEDS class in the main kernel tree. for additional information see the linux-2.6.xx/Documentation/leds-class.txt file.

@@ Line 18: / Line 18: @@
 == Adding New LEDS ==
-a new LED connected via a GPIO can be defined in the linux-2.6.xx/arch/arm/mach-s3c2410/mach-tct_hammer.c file. each LED will need to include some platform data and a platform device definition:
+a new LED connected via a GPIO can be defined in the linux-2.6.xx/arch/arm/mach-s3c2410/mach-tct_hammer.c file. each LED will need to include some platform data and a platform device definition. Make sure the platform data and the platform device are above the platform declaration:
 <pre>
@@ Line 37: / Line 37: @@
 </pre>
 == Nail Board LED's ==

@@ Line 105: / Line 105: @@
 	platform_add_devices(tct_hammer_devices, ARRAY_SIZE(tct_hammer_devices));
+}
 </pre>

← Older revision		Revision as of 19:58, 16 June 2008
Line 38:		Line 38:
	</pre>		</pre>
	this uses the standard LEDS class in the main kernel tree. for additional information see the linux-2.6.xx/Documentation/leds-class.txt file.		this uses the standard LEDS class in the main kernel tree. for additional information see the linux-2.6.xx/Documentation/leds-class.txt file.
		+
		+
		+	== Nail Board LED's ==
		+
		+	<pre>
		+	static struct s3c24xx_led_platdata tct_hammer_pdata_led1 = {
		+	.gpio = S3C2410_GPH0,
		+	.flags = S3C24XX_LEDF_ACTLOW \| S3C24XX_LEDF_TRISTATE,
		+	.name = "led1",
		+	.def_trigger = "timer",
		+	};
		+
		+	static struct s3c24xx_led_platdata tct_hammer_pdata_led2 = {
		+	.gpio = S3C2410_GPH1,
		+	.flags = S3C24XX_LEDF_ACTLOW \| S3C24XX_LEDF_TRISTATE,
		+	.name = "led2",
		+	.def_trigger = "timer",
		+	};
		+
		+
		+	static struct platform_device tct_hammer_led1 = {
		+	.name = "s3c24xx_led",
		+	.id = 1,
		+	.dev = {
		+	.platform_data = &tct_hammer_pdata_led1,
		+	},
		+	};
		+
		+	static struct platform_device tct_hammer_led2 = {
		+	.name = "s3c24xx_led",
		+	.id = 2,
		+	.dev = {
		+	.platform_data = &tct_hammer_pdata_led2,
		+	},
		+	};
		+	</pre>
		+
		+	you will also need to add some gpio setup in the machine init function:
		+
		+	<pre>
		+	static void __init tct_hammer_init(void)
		+	{
		+
		+	s3c2410_gpio_cfgpin(S3C2410_GPF0, S3C2410_GPIO_OUTPUT);
		+	s3c2410_gpio_setpin(S3C2410_GPF0, 1);
		+
		+	/* add these lines to setup the leds on the nail board */
		+	s3c2410_gpio_cfgpin(S3C2410_GPH0, S3C2410_GPIO_OUTPUT);
		+	s3c2410_gpio_setpin(S3C2410_GPH0, 1);
		+	s3c2410_gpio_cfgpin(S3C2410_GPH1, S3C2410_GPIO_OUTPUT);
		+	s3c2410_gpio_setpin(S3C2410_GPH1, 1);
		+
		+	s3c2410_gpio_cfgpin(S3C2410_GPC12, S3C2410_GPIO_OUTPUT);
		+	s3c2410_gpio_setpin(S3C2410_GPC12, 1);
		+
		+	/uncomment these these to enable the second serial port /
		+	/*
		+	s3c2410_gpio_cfgpin(S3C2410_GPH6, S3C2410_GPH6_TXD0);
		+	s3c2410_gpio_pullup(S3C2410_GPH6, 1);
		+	s3c2410_gpio_cfgpin(S3C2410_GPH7, S3C2410_GPH7_RXD0);
		+	s3c2410_gpio_pullup(S3C2410_GPH7, 1);
		+	*/
		+	#ifdef CONFIG_FB_S3C2410
		+	s3c24xx_fb_set_platdata(&tct_hammer_lcd_info);
		+	#endif
		+	platform_add_devices(tct_hammer_devices, ARRAY_SIZE(tct_hammer_devices));
		+	}
		+
		+	</pre>

← Older revision		Revision as of 15:20, 12 May 2008
Line 38:		Line 38:
	</pre>		</pre>
	this uses the standard LEDS class in the main kernel tree. for additional information see the linux-2.6.xx/Documentation/leds-class.txt file.		this uses the standard LEDS class in the main kernel tree. for additional information see the linux-2.6.xx/Documentation/leds-class.txt file.
−
−
−	~~== LED Hardware ==~~
−
−	~~the most common way of operating a LED via a gpio is to use an active low configuration:~~
−
−	~~[[Image:led-example.jpg]]~~

@@ Line 2: / Line 2: @@
 the LED onboard the hammer as well as the LED on the carrier board can be accessed from userspace via the sysfs interface. example interfaces are in /sys/devices/platform/s3c24xx_led.0/leds:led0/ and /sys/devices/platform/s3c24xx_led.1/leds:led1/. both directories include a file entry "brightness". to turn a LED on, echo a non zero value to the brightness file entry:
+<pre>
 echo 1 > /sys/devices/platform/s3c24xx_led.0/leds:led0/brightness
+</pre>
 to turn a LED off, echo a zero to the the brightness file entry:
+<pre>
 echo 0 > /sys/devices/platform/s3c24xx_led.0/leds:led0/brightness
+</pre>
 you can also check the current status of the LED by using cat on the brightness file entry:
+<pre>
 cat /sys/devices/platform/s3c24xx_led.0/leds:led0/brightness
+</pre>