N900 Hardware LED - Revision history

imported_>joerg_rw: /* Software */ show sysfs ls -l

2022-12-15T16:00:25Z

Software: show sysfs ls -l

@@ Line 35: / Line 35: @@
 ==Software==
+ IroN900:/sys/class/i2c-adapter/i2c-2/2-0032# echo load >engine1_mode
 == References ==

90.180.214.199: /* Hardware */

2014-01-07T09:43:14Z

Hardware

← Older revision		Revision as of 09:43, 7 January 2014
Line 7:		Line 7:
	* <code>disabled</code>: The channel is disabled - not running		* <code>disabled</code>: The channel is disabled - not running
	* <code>load</code>: In that state, there are two more files in that directory:		* <code>load</code>: In that state, there are two more files in that directory:
	** engine1_LEDs is in the form "~~0000rgb00~~" (9 digits, "1" or "0"), where rgb control which LEDs should participate. The 6 "0" in the above pattern correspond to the 6 kbd white LEDs controlled by MCE via engine3, so readout of engine3_leds gives 111100011 ;-)		** engine1_LEDs is in the form "0000bgr00" (9 digits, "1" or "0"), where rgb control which LEDs should participate. The 6 "0" in the above pattern correspond to the 6 kbd white LEDs controlled by MCE via engine3, so readout of engine3_leds gives 111100011 ;-)
	** engine1_load accepts a string as specified above (e.g. 9d804000427f0d7f7f007f0042000000). LP5523 has an absolute storage of 96 steps a 16bits, which can dynamically partitioned between the three engines. (Supports 32-96 steps per engine, dynamically-assigned, alas the lp5523.ko driver is braindamaged and doesn't support more than 16 instructions per engine)		** engine1_load accepts a string as specified above (e.g. 9d804000427f0d7f7f007f0042000000). LP5523 has an absolute storage of 96 steps a 16bits, which can dynamically partitioned between the three engines. (Supports 32-96 steps per engine, dynamically-assigned, alas the lp5523.ko driver is braindamaged and doesn't support more than 16 instructions per engine)
	After that, when the state is changed to "run", the program will be ran by the controller.		After that, when the state is changed to "run", the program will be ran by the controller.

90.180.214.199: Yes, sysfs is stable, no, you do not need to wait between accessing /sys. Driver takes care of delays.

2014-01-06T13:32:49Z

Yes, sysfs is stable, no, you do not need to wait between accessing /sys. Driver takes care of delays.

← Older revision		Revision as of 13:32, 6 January 2014
Line 3:		Line 3:
	The [[Nokia N900\|N900]] has LP5523 <ref name="lp5523-spec">http://www.national.com/pf/LP/LP5523.html</ref> <ref name="leds-lp5523-driver">http://mxr.maemo.org/fremantle/source/kernel/drivers/leds/leds-lp5523.c</ref>, which has 3 engines like LP5521 (compatible though augmented instruction set) but can drive 9 LEDs via a multiplexer which maps each LED to one of the 3 engines. A LED also can be unassigned to any engine, in which case you can control it by writing to the corresponding brightness sysnode) which handles the keyboard and notification LED. (not the [[N900 Hardware Flash Torch\|flash LEDs]] and red indicator light next to those, and also not the Infrared-LED used for CIR)		The [[Nokia N900\|N900]] has LP5523 <ref name="lp5523-spec">http://www.national.com/pf/LP/LP5523.html</ref> <ref name="leds-lp5523-driver">http://mxr.maemo.org/fremantle/source/kernel/drivers/leds/leds-lp5523.c</ref>, which has 3 engines like LP5521 (compatible though augmented instruction set) but can drive 9 LEDs via a multiplexer which maps each LED to one of the 3 engines. A LED also can be unassigned to any engine, in which case you can control it by writing to the corresponding brightness sysnode) which handles the keyboard and notification LED. (not the [[N900 Hardware Flash Torch\|flash LEDs]] and red indicator light next to those, and also not the Infrared-LED used for CIR)

	The controller can be programmed via "/sys/class/i2c-adapter/i2c-2/2-0032" ~~(FIXME: is this stable?)~~. In that directory there are three files corresponding to the three channels: <code>engine1_mode</code>, <code>engine2_mode</code> and <code>engine3_mode</code>. Each file "stores" one of <code>run</code>, <code>load</code>, <code>disabled</code> (it seems that there is another mode "direct" but it doesn't work)(direct mode requires explicit writes to PWM, current and multiplexing registers, which may not be supported in the code...):		The controller can be programmed via "/sys/class/i2c-adapter/i2c-2/2-0032". In that directory there are three files corresponding to the three channels: <code>engine1_mode</code>, <code>engine2_mode</code> and <code>engine3_mode</code>. Each file "stores" one of <code>run</code>, <code>load</code>, <code>disabled</code> (it seems that there is another mode "direct" but it doesn't work)(direct mode requires explicit writes to PWM, current and multiplexing registers, which may not be supported in the code...):
	* <code>run</code>: The program runs		* <code>run</code>: The program runs
	* <code>disabled</code>: The channel is disabled - not running		* <code>disabled</code>: The channel is disabled - not running
Line 18:		Line 18:
	</source>		</source>
	suggesting different, the units in there are 0.1 mA (100 µA per step is correct). So the driver init default "50" for all LEDs is 5 mA, and mce seems to set current to 0.2 mA (value 2 in the led_current sysnode) for B and G, and either to 0.2 mA or 0.8 mA for R. Probably settings as high as 100 for 10 mA are safe for the RGB LED, higher values might destroy the LED. (yes, correct, the RGB could be damaged from heat if set to more than 10 mA on all 3 LEDs)		suggesting different, the units in there are 0.1 mA (100 µA per step is correct). So the driver init default "50" for all LEDs is 5 mA, and mce seems to set current to 0.2 mA (value 2 in the led_current sysnode) for B and G, and either to 0.2 mA or 0.8 mA for R. Probably settings as high as 100 for 10 mA are safe for the RGB LED, higher values might destroy the LED. (yes, correct, the RGB could be damaged from heat if set to more than 10 mA on all 3 LEDs)

	~~NOTE: There must be a delay (how much? The specs of LP5521 mentions it) between writes to sysfs files.~~

imported_>joerg_rw: /* References */ ditto

2013-09-23T13:23:40Z

References: ditto

← Older revision		Revision as of 13:23, 23 September 2013
Line 43:		Line 43:
	also see [[LED_patterns]] of which this page is a "fork" without cleaning the original page, so now there are two versions with almost identical but slightly complementary info		also see [[LED_patterns]] of which this page is a "fork" without cleaning the original page, so now there are two versions with almost identical but slightly complementary info

	Since beginning of 2012 a datasheet for LP5523 is available from TI: http://www.ti.com/product/lp5523		Since beginning of 2012 a datasheet for LP5523 is available from TI: http://www.ti.com/product/lp5523 Direct link: http://www.ti.com/general/docs/lit/getliterature.tsp?literatureNumber=snvs550d&fileType=pdf

	<references />		<references />

	[[Category:N900 Hardware]]		[[Category:N900 Hardware]]

imported_>joerg_rw: /* References */ fixed dangling link to datasheet on TI site

2013-09-23T13:20:35Z

References: fixed dangling link to datasheet on TI site

← Older revision		Revision as of 13:20, 23 September 2013
Line 43:		Line 43:
	also see [[LED_patterns]] of which this page is a "fork" without cleaning the original page, so now there are two versions with almost identical but slightly complementary info		also see [[LED_patterns]] of which this page is a "fork" without cleaning the original page, so now there are two versions with almost identical but slightly complementary info

	Since beginning of 2012 a datasheet for LP5523 is available from TI: http://www.ti.com/~~lit~~/~~ds/snvs550c/snvs550c.pdf~~		Since beginning of 2012 a datasheet for LP5523 is available from TI: http://www.ti.com/product/lp5523

	<references />		<references />

	[[Category:N900 Hardware]]		[[Category:N900 Hardware]]

imported_>joerg_rw: /* References */ added link to datasheet

2012-06-05T12:39:03Z

References: added link to datasheet

← Older revision		Revision as of 12:39, 5 June 2012
Line 42:		Line 42:

	also see [[LED_patterns]] of which this page is a "fork" without cleaning the original page, so now there are two versions with almost identical but slightly complementary info		also see [[LED_patterns]] of which this page is a "fork" without cleaning the original page, so now there are two versions with almost identical but slightly complementary info

			Since beginning of 2012 a datasheet for LP5523 is available from TI: http://www.ti.com/lit/ds/snvs550c/snvs550c.pdf

	<references />		<references />

	[[Category:N900 Hardware]]		[[Category:N900 Hardware]]

imported_>joerg_rw: /* Hardware */ added warning about hardware bug

2011-08-06T16:58:09Z

Hardware: added warning about hardware bug

← Older revision		Revision as of 16:58, 6 August 2011
Line 20:		Line 20:

	NOTE: There must be a delay (how much? The specs of LP5521 mentions it) between writes to sysfs files.		NOTE: There must be a delay (how much? The specs of LP5521 mentions it) between writes to sysfs files.


			''BEWARE!
			register addr 0x3B: GPO
			LP5523 has one General Purpose Output pin (GPO).
			Status of the pin can be controlled with this register. Also,
			'''INT pin can be configured to function as a GPO''' by setting
			the bit INT_CONF. When INT is configured to function as
			a GPO, '''output level is defined by the VDD voltage'''.
			3B — Bit [2] INT_CONF
			0 = INT pin is set to function as an interrupt pin (default).
			1 = INT pin is configured to function as a GPO.

			INT is routed directly to a SOC GPIO that is not designed to take voltages >1.8V ! So setting 0x3B:2 to 1 may fry your CPU
			''

	==Software==		==Software==

imported_>joerg_rw: /* References */ link to http://wiki.maemo.org/LED_patterns

2011-08-06T15:40:04Z

References: link to http://wiki.maemo.org/LED_patterns

← Older revision		Revision as of 15:40, 6 August 2011
Line 25:		Line 25:

	== References ==		== References ==

			also see [[LED_patterns]] of which this page is a "fork" without cleaning the original page, so now there are two versions with almost identical but slightly complementary info

	<references />		<references />

	[[Category:N900 Hardware]]		[[Category:N900 Hardware]]

imported_>joerg_rw: /* Hardware */

2011-08-06T15:28:30Z

Hardware

← Older revision		Revision as of 15:28, 6 August 2011
Line 8:		Line 8:
	* <code>load</code>: In that state, there are two more files in that directory:		* <code>load</code>: In that state, there are two more files in that directory:
	** engine1_LEDs is in the form "0000rgb00" (9 digits, "1" or "0"), where rgb control which LEDs should participate. The 6 "0" in the above pattern correspond to the 6 kbd white LEDs controlled by MCE via engine3, so readout of engine3_leds gives 111100011 ;-)		** engine1_LEDs is in the form "0000rgb00" (9 digits, "1" or "0"), where rgb control which LEDs should participate. The 6 "0" in the above pattern correspond to the 6 kbd white LEDs controlled by MCE via engine3, so readout of engine3_leds gives 111100011 ;-)
	** engine1_load accepts a string as specified above (e.g. 9d804000427f0d7f7f007f0042000000). LP5523 has an absolute storage of 96 steps a 16bits, which can dynamically partitioned between the three engines. ~~(ToDo: check if driver supports >16 instructions / machine)~~ (Supports 32-96 steps per engine, dynamically-assigned)		** engine1_load accepts a string as specified above (e.g. 9d804000427f0d7f7f007f0042000000). LP5523 has an absolute storage of 96 steps a 16bits, which can dynamically partitioned between the three engines. (Supports 32-96 steps per engine, dynamically-assigned, alas the lp5523.ko driver is braindamaged and doesn't support more than 16 instructions per engine)
	After that, when the state is changed to "run", the program will be ran by the controller.		After that, when the state is changed to "run", the program will be ran by the controller.

imported_>joerg_rw: /* Hardware */

2011-08-06T15:26:38Z

Hardware

← Older revision		Revision as of 15:26, 6 August 2011
Line 11:		Line 11:
	After that, when the state is changed to "run", the program will be ran by the controller.		After that, when the state is changed to "run", the program will be ran by the controller.

	In order for the LEDs to work, the led_current of the appropriate LEDs need to be set to non-zero values. This is accomplished by writing to files LEDs:lp5523:[bgr]/led_current under the same directory. ~~Perhaps (?) not or~~ values are suitable.		In order for the LEDs to work, the led_current of the appropriate LEDs need to be set to non-zero values. This is accomplished by writing to files LEDs:lp5523:[bgr]/led_current under the same directory. Default values from kernel module init are suitable.

	Despite the line		Despite the line
Line 17:		Line 17:
	#define LP5523_DEFAULT_CURRENT 50 /* microAmps */		#define LP5523_DEFAULT_CURRENT 50 /* microAmps */
	</source>		</source>
	suggesting different, the units in there are 0.1 mA (100 µA per step is correct). So the driver init default for all ~~LED~~ is 5 mA, and mce seems to set current to 0.2 mA (value 2 in the led_current sysnode) for B and G, and either to 0.2 mA or 0.8 mA for R. Probably settings as high as 100 for 10 mA are safe for the RGB LED, higher values might destroy the LED. (yes, correct, the RGB could be damaged from heat if set to more than 10 mA on all 3 LEDs)		suggesting different, the units in there are 0.1 mA (100 µA per step is correct). So the driver init default "50" for all LEDs is 5 mA, and mce seems to set current to 0.2 mA (value 2 in the led_current sysnode) for B and G, and either to 0.2 mA or 0.8 mA for R. Probably settings as high as 100 for 10 mA are safe for the RGB LED, higher values might destroy the LED. (yes, correct, the RGB could be damaged from heat if set to more than 10 mA on all 3 LEDs)

	NOTE: There must be a delay (how much? The specs of LP5521 mentions it) between writes to sysfs files.		NOTE: There must be a delay (how much? The specs of LP5521 mentions it) between writes to sysfs files.