Keyboard backlight driver IC

Information

  • Patent Grant
  • 9013113
  • Patent Number
    9,013,113
  • Date Filed
    Wednesday, October 24, 2012
    11 years ago
  • Date Issued
    Tuesday, April 21, 2015
    9 years ago
Abstract
One embodiment of a display backlight driver integrated circuit can be configured for operation in at least two different ways. A first method transfers data from an EEPROM to hardware registers prior to regular operation. A second method also transfers data from an EEPROM to registers. However, hardware registers can be overwritten with data accepted from a control bus, prior to regular operation. A keyboard driver IC can detect the presence or absence of a cable to an LED. If the cable is absent, the driver IC will not supply power for the LED. One embodiment of a keyboard and display backlight control system can be configured to allow substantially independent operation.
Description
FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to light emitting diode (LED) controllers, and more particularly configurable LED controllers capable of controller two independent LED systems.


BACKGROUND

Portable computing devices often include displays to provide a user graphical or textual information. The displays often include a backlight that enables the display to be used in low or dim ambient lighting environments. There can be some displays that are not useable without at least some amount of backlight. In some embodiments, portable computing devices can also include a backlight for an included keyboard.


Display and keyboard backlights typically require controllers to control dimming of the respective lights and also to provide a voltage for powering the LED (light emitting diode) arrays that typically provide the backlights. Portable computing devices are continually getting smaller and thinner. As a consequence, LED controllers must also become smaller and more integrated.


Some integrated LED controller solutions lack configuration flexibility. That is, while some LED controllers can work well in a first mode of operation, the same LED controller may not work as well in a second mode of operation, especially when an operating mode can be based on an operating system. Examples of operating systems are Windows® from Microsoft®, Mac-OS® from Apple Inc.®, Linux, UNIX and others. For example, a portable computing device including a particular LED controller can boot with no difficulty with a first operating system; however, the same LED controller can exhibit artifacts such a flashing and blinking when booting with a second operating system.


Therefore, what is desired is a relatively compact configurable LED controller that can easily be configured to operate in multiple operating modes.


SUMMARY OF THE DESCRIBED EMBODIMENTS

This paper describes various embodiments that relate to a configurable LED control system. In one embodiment a LED driver device can include a voltage boost circuit, a current sink circuit, an enable input and a brightness input.


In another embodiment, a keyboard LED controlling system can include a LED array configured to backlight a keyboard of a computing device, and a LED array controller, the controller including a voltage boost circuit configured to provide a supply voltage to the LED array, a current sinking circuit configured to sink current from the LED array and a configuration port, configured to control, at least in part, the LED array controller.


In yet another embodiment, a LED controller system for a portable computing device can include a first LED array configured to provide light for a keyboard for the portable computing device, a second LED array configured to provide light for a display of the portable computing device and a LED array controller that can include a voltage boost circuit configured to supply a voltage to the first and second LED arrays, a current sink circuit configured to couple a return current to ground and a brightness input configured to control the current sink circuit.





BRIEF DESCRIPTION OF THE DRAWINGS

The described embodiments and the advantages thereof may best be understood by reference to the following description taken in conjunction with the accompanying drawings. These drawings in no way limit any changes in form and detail that may be made to the described embodiments by one skilled in the art without departing from the spirit and scope of the described embodiments.



FIG. 1 is a block diagram of an LED driver integrated circuit (IC) in a system, in accordance with one embodiment of the specification.



FIG. 2 is a block diagram of one embodiment of an LED driver IC.



FIG. 3 is a block diagram illustrating the EEPROM and hardware registers shown in FIG. 2.



FIG. 4 is a flow chart of method steps for configuring LED driver IC when operating in the second operational mode.



FIG. 5 is a timing diagram illustrating some of the signals related to a first operational mode for the LED driver IC.



FIG. 6 is a timing diagram illustrating some of the signals related to a second operational mode for the LED driver IC.



FIG. 7 is a block diagram of PWM generation circuit, in accordance with one embodiment of the specification.



FIG. 8 is a simplified block diagram of a flex cable detection circuit in accordance with one embodiment of the specification.



FIG. 9 is a block diagram of an LED light control system.



FIG. 10 is a flow chart of method steps for configuring a LED controller for use in a computing device.



FIG. 11 is a flow chart of method steps for controlling the output state of a LED driver in a computing device





DETAILED DESCRIPTION OF SELECTED EMBODIMENTS

Representative applications of methods and apparatus according to the present application are described in this section. These examples are being provided solely to add context and aid in the understanding of the described embodiments. It will thus be apparent to one skilled in the art that the described embodiments may be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order to avoid unnecessarily obscuring the described embodiments. Other applications are possible, such that the following examples should not be taken as limiting.


In the following detailed description, references are made to the accompanying drawings, which form a part of the description and in which are shown, by way of illustration, specific embodiments in accordance with the described embodiments. Although these embodiments are described in sufficient detail to enable one skilled in the art to practice the described embodiments, it is understood that these examples are not limiting; such that other embodiments may be used, and changes may be made without departing from the spirit and scope of the described embodiments.


A compact and configurable LED controller system can comprise a boost converter and a LED driver integrated circuit (IC). Together, the boost converter and the LED driver IC can control a keyboard backlight LED array and a display backlight LED array and allow independent control of each LED array. The configurable LED controller system can be configured to work in a plurality of operational modes. In one embodiment, the operational modes can be modes related to different operating systems.



FIG. 1 is a block diagram of an LED driver integrated circuit (IC) in a system 100, in accordance with one embodiment described in the specification. The system 100 can include LED driver IC 104, that can be configured to control a display LED 108 by sinking current from the display LED 108. In one embodiment, system 100 can be included in a computing device such as a portable computer, a media player, a personal digital assistant or the like. The display LED can receive power from a boost converter 102. The boost converter 102 can receive input voltages (VDDD, VDDA and Vbat) and, in one embodiment, up convert an input voltage from a first, lower voltage to a second higher (boost) voltage. In this Figure, the boost voltage can be provided to display LED 108. The system can include a timing controller (TCON) 106 that can be configured to provide at least one pulse width modulated (PWM) signal to LED driver IC 104. In one embodiment, the PWM signal can be used to control, at least in part, the current being directed to ground 150 from the display LED 108.


System 100 can also include graphics processing unit (GPU) 120. In one embodiment, GPU 120 can provide control signals 112 to TCON 106 and LED driver IC 104. One example of control signals can be a serial control bus that can include at least two signals: clock and data. For example, a serial clock (SCL), and a serial data (SDA) signal can be sent from GPU 120. In other embodiments, GPU 120 can be replaced with any other suitable device for generating and monitoring control signals such as a micro-controller, processor, state machine, field programmable gate array (FPGA), processor or the like. The LED driver IC 104 can provide control signals 112 to boost converter 102. In one embodiment, the control signals 112 can be serial control bus signals. Boost converter 102 can also include an enable pin that can enable one or more features within boost converter 102. In one embodiment, the serial control bus can be used to control, at least in part, the current being directed to ground 150 from the display LED 108.


LED driver IC 104 can be configured to control display LED 108 brightness under at least two operational modes. In a first operational mode, a power on reset event can cause EEPROM (electrically erasable programmable read only memory) data to be loaded into hardware registers. Although EEPROM is used to exemplify non-volatile storage herein, other forms of non-volatile storage can be used such as masked ROM, NAND cells and battery backed RAM. The hardware registers can control LED driver IC 104 operation. In one embodiment, EEPROM data can be stored in EEPROM memory included in boost converter 102. After the power on reset event, the loaded hardware registers can be used as the default values in the LED driver IC 104. In this first operational mode, as soon as an enable signal 110 is asserted, LED driver IC 104 can become active and can control the output of display LED 108.


In a second operational mode, although EEPROM data can be loaded into hardware registers after a power on reset event, these values can be overridden prior to LED driver IC 104 becoming active through enable signal 110. For example, the power on reset event can cause initial values for the hardware registers to be loaded from EEPROM. Then, the initial values for hardware registers can be overridden through control signals 112, even when enable signal 110 is not asserted. In this second operational mode, a PWM signal from TCON 106 can affect a brightness of display LED 108. In one embodiment, a return current from display LED 108 is coupled to ground in accordance with the PWM signal from TCON 106.



FIG. 2 is a block diagram 200 of one embodiment of LED driver IC 104. In this embodiment EEPROM 204 can be included within LED driver IC 104. In other embodiments, EEPROM 204 can be separate from LED driver IC 104, but can be coupled through an address and data bus, for example. After a power on reset event is detected, data from EEPROM 204 can be transferred to hardware registers 206. Alternatively, a control signal interface 208 can be coupled to control signals 112 and a write or overwrite data in hardware registers 206. Power on reset detector 210 can detect when power applied to LED driver IC can transition from zero volts to an operating voltage. Enable signal 110 can enable operation of at least a portion of the LED driver IC 104.



FIG. 3 is a block diagram 300 illustrating the EEPROM 204 and hardware registers 206 shown in FIG. 2 in accordance with one embodiment described in the specification. EEPROM 204 can include EEPROM registers 304 that provide access to EEPROM data 302. After a power on reset event, data from EEPROM data 302 can be retrieved by EEPROM registers 304 and transferred into registers 308. In some embodiments, EEPROM data can be transferred into LED driver IC 104 hardware registers 206. Control signals 112 can be received by control signal interface 208.



FIG. 4 is a flow chart 400 of method steps for configuring LED driver IC 104 when operating in the second operational mode. The method can begin in step 402 when a power on reset event is detected. In one embodiment, a power on reset event can be when power is detected on the power supply pins of the LED driver IC 104. In step 404, data from EEPROM 204 can be transferred to hardware registers 206. In step 406 the enable signal 110 can be de-asserted. In step 408, the LED driver IC 104 can be configured with control signals 112 through control signal interface 208. In some embodiments, control signals 112 can be coupled to hardware registers 206 to enable configuration. In step 410 the enable signal 110 can be asserted. In step 412, the LED is turned on.



FIG. 5 is a timing diagram 500 illustrating some of the signals related to a first operational mode for the LED driver IC 104. After a power on reset event, data from EEPROM 204 is loaded into hardware registers 206. The power on reset event can occur after power is applied to the LED driver IC 104 as shown by signal 506. Data loading from EEPROM 204 to hardware registers 206 is shown with signal 502. In this operational mode, display LED 108 is maintained in the off state until the enable signal 110 is asserted. Signal 504 illustrates the enable signal 110. Since, in this graph, the signal is always un-asserted, the display LED 108 is off.



FIG. 6 is a timing diagram 600 illustrating some of the signals related to a second operational mode for the LED driver IC. In this mode, after a power on reset event, data from EEPROM 204 is again loaded into hardware registers 206. The power on reset event can occur after power is applied to the LED driver IC 104 as shown by signal 506. Data loading from EEPROM 204 to hardware registers 206 is shown with signal 502. Control signals 112 can be used to overwrite the hardware registers 206, even before the enable signal 110 is asserted. Signal 604 illustrates timing of control signals 112 that can be used to overwrite hardware registers 206. Signal 606 illustrates the enable signal 110. Note that the enable signal is not asserted when control signals 112 are active. When enable signal 110 becomes asserted, the associated LED display can be enabled as well. In one embodiment a pulse width modulation (PWM) signal 608 is active and can be used to control display LED 108 brightness.


Special signal handling of some clock or timing signals may be required when operation of LED driver IC 104 transitions from the first operational mode to the second operational mode or from the second operational mode to the first operational mode. In one embodiment a special reset signal can be used to reset at least one portion of a phased locked loop (PLL) system. FIG. 7 is a block diagram of PWM generation circuit 700, in accordance with one embodiment described in the specification. The PWM generation circuit can include a PLL 702, a PWM module 710, internal clock generator 706 and external sync signal module 704.


PWM module 710 can be used to control current sink circuits of the display LED 108. PWM module 710 can select either a signal from the external sync signal module 704 or a signal from the PLL 702 to base the output of the PWM module 710. In the first operational mode, the PLL 702 can phase lock the output of the external sync signal module 704 to the output of the internal clock generator 706. In one embodiment, the internal clock generator 706 can be based on an oscillator, such as a crystal oscillator. The phase locked output of the PLL 702 is coupled to the PWM module 710.


In the second operational mode, the PLL 702 is not used by the PWM module 710. In the second operational mode, a signal from the external sync signal module 704 is coupled to the PWM module 710. When transitioning from the second operational mode to the first operational mode, the sync path may require a reset signal, separate and independent from the power on reset signal. In one embodiment, the clkmux_sync_reset signal 708 can be applied to the external sync signal module 704, PLL 702 and PWM module 710 and reset internal registers and counters in these registers.



FIG. 8 is a simplified block diagram of a flexible (flex) cable detection circuit 800 in accordance with one embodiment of the specification. By detecting the presence of a flex cable prior to operation, exposure to relatively high boost voltages can be controlled. Keyboard backlight driver 814 can provide a boost voltage necessary to control and light a LED keyboard backlight 822. Sometimes, the voltage necessary to light LED keyboard backlight 822 can be relatively higher than 5.0 or 3.3 volts. If the cable 818 to the LED keyboard backlight 822 is not connected to the keyboard backlight driver 814, these relatively higher voltages can be exposed. To detect the presence or absence of the cable 818, the keyboard backlight driver 814 can include a multimode pin 816. Multimode pin 816 can normally be used by a system micro-controller (SMC) to read a system parameter in the keyboard backlight driver 814. In an extra mode, the multimode pin 816 can be tri-stated and change from an output to an input. The multimode pin 816 can be used to detect the presence of the cable 818, and therefore control the enabling of power to the LED keyboard backlight 822.


Power for the LED keyboard backlight 822 is routed from the keyboard backlight driver 814 to a connector 804. A mating connector 810 can be coupled to connector 804 and can couple the power through cable 818 to LED keyboard backlight 822. At the same time, a shorting connection 820 can exist in mating connector 810, cable 818 or even within LED keyboard backlight 822. Shorting connection 820 can be used to short a first pin 806 to a second pin 808 at connector 804. If mating connector 810 is not coupled to connector 804, then pull-up resistor 802 can pull multimode pin 816 to a logic high level. On the other hand, if mating connector 810 is coupled to connector 804 then shorting connection 820 can effectively short first pin 806 to second pin 808, and thereby bring multimode pin 816 to a logic low level.


Prior to enabling the power for the LED keyboard backlight 822, the keyboard backlight driver 814 can sense the logic level at the multimode pin 816. If the multimode pin 816 is at a logic high, then the cable 818 is not connected, and the power for the LED keyboard backlight 822 will not be enabled. On the other hand, if the multimode pin 816 is at a logic low, then the cable 818 is connected, and the power for the LED keyboard backlight 822 will be enabled.



FIG. 9 is a block diagram of a LED light control system 900. In one embodiment, the control system 900 can independently control at least two LED systems. For example a first system can be a keyboard backlight and a second system can be a display backlight, where both backlights may be used in a portable computing device. The control system 900 can be built around two ICs: 1) boost converter 102 and 2) LED driver IC 104. The control system 900 can also include two LED arrays: LED keyboard backlight 822 and display LED 108. The LED keyboard backlight 822 can be coupled to the boost converter 102. That is, the boost converter 102 can provide boost voltage for both the LED keyboard backlight 822 display LED 108. Additionally, boost converter 102 can also sink a return current from LED keyboard backlight 822. Display LED 108 can be coupled to both boost converter 102 and LED driver IC 104. Boost converter 102 can provide boost voltage for display LED 108, while return current from display LED 108 can be sunk by LED driver IC 104 through ground 150.


Control system 900 can also include TCON 106 coupled to LED driver IC 104. TCON 106 can be configured to provide a PWM signal 910 to LED driver IC 104. LED driver IC 104 can sink current for display LED 108 in accordance with the PWM signal. TCON 106 can also control, at least in part, the output of LED driver IC 104 through manipulation of enable signal 110. In one embodiment, the output of LED driver IC 104 can be controlled through a combination of enable signal 110 and the PWM signal from TCON 106.


Control for both the boost converter 102 and LED driver IC 104 can be through GPU 120. As described in conjunction with FIG. 1, the GPU 120 can be replaced with any other technically feasible unit that can assert control signals 112. In one embodiment, GPU 120 can also include a dedicated enable signal 113 coupled to boost converter 102. GPU 120 can also provide a PWM signal 910 to boost converter 102 to guide the current sink for the keyboard backlight 822.


Independent control of the LED keyboard backlight 822 can be through dedicated enable signal 113. Independent control of LED driver IC 104 can be through control signals 112. In one embodiment, control signals 112 can be coupled to TCON 106 and LED driver IC 104. TCON 106 can, in turn, control enable signal 110 which can be coupled to LED driver IC 104.



FIG. 10 is a flow chart of method steps 1000 for configuring a LED controller for use in a computing device. The method can begin in step 1002 when a power on reset event is detected. In one embodiment, a power on reset event is detected when power supplied to the LED controller transitions from zero volts to an operating voltage. In step 1004, data from an EEPROM 204 can be loaded into hardware registers 206. In step 1006, data in hardware registers 206 can be over ridden with additional data. In one embodiment, the additional data can be written through a control signal interface 208. In step 1008, the LED controller output can be enabled thereby lighting a LED or LED array.



FIG. 11 is a flow chart of method steps 1100 for controlling the output state of a LED driver in a computing device. The method can begin in step 1102 when the LED driver enters a configuration mode. In one embodiment, the configuration mode can be entered after detecting a power on reset event as described above. In step 1104, a multimode pin can be configured to operate in a first mode. In one embodiment, the multimode pin can be configured to operate as an input pin. In step 1106, the logic state of the multimode pin can be determined. For example, the multimode pin can be set to a logical ‘0’ or a logical ‘1’. In step 1108, the output of the LED driver can be determined by the logic state of the multimode pin. In step 1110, the multimode pin can be configured to operate in a second mode and the method ends. For example, the multimode pin can be configured to operate as an output pin.


The various aspects, embodiments, implementations or features of the described embodiments can be used separately or in any combination. Various aspects of the described embodiments can be implemented by software, hardware or a combination of hardware and software. The described embodiments can also be embodied as computer readable code on a computer readable medium for controlling manufacturing operations or as computer readable code on a computer readable medium for controlling a manufacturing line. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, HDDs, DVDs, magnetic tape, and optical data storage devices. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.


The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the described embodiments. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the described embodiments. Thus, the foregoing descriptions of specific embodiments are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the described embodiments to the precise forms disclosed. It will be apparent to one of ordinary skill in the art that many modifications and variations are possible in view of the above teachings.

Claims
  • 1. A method for operating a light emitting diode (LED) array, the method comprising: by a boost converter:providing a boost voltage greater than a supply voltage to the LED array; andcontrolling a return current from the LED array to ground based on a brightness input signal received at a brightness input.
  • 2. The method of claim 1, wherein the brightness input signal comprises a pulse width modulation (PWM) signal used by the boost converter to control brightness of the LED array.
  • 3. The method of claim 1, wherein the boost converter can be configured according to a control signal received through a serial bus interface, the control signal provided by one or more of a graphics processing unit (GPU), a microcontroller, a processor, a state machine, or an field programmable gate array (FPGA).
  • 4. The method of claim 1, further comprising turning on the LED array using an enable pin by coupling the return current from the LED array to ground.
  • 5. The method of claim 4, wherein the boost converter is further configured to receive the return current from the LED array.
  • 6. The method of claim 1, wherein the boost converter is further configured to be enabled in accordance with an enable input signal.
  • 7. A keyboard light emitting diode (LED) control system, comprising: an LED array configured to backlight a keyboard of a computing device; andan LED array controller, comprising:a boost converter configured to: provide a boost voltage greater than a supply voltage to the LED array, andcontrol a return current from the LED array to ground based on a brightness input signal received at the brightness input.
  • 8. The keyboard LED control system of claim 7, wherein the LED array controller further comprises an enable pin configured to turn on the LED array by coupling the return current from the LED array to ground.
  • 9. The keyboard LED control system of claim 7, wherein the brightness input signal comprises a pulse width modulation (PWM) signal generated based on a phase lock loop of a PWM generation circuit.
  • 10. The keyboard LED control system of claim 9, wherein the LED array controller sinks the return current from the LED array to ground in accordance with the PWM signal.
  • 11. The keyboard LED control system of claim 10, wherein the PWM signal is provided by a state machine.
  • 12. The keyboard LED control system of claim 10, wherein the PWM signal is provided by a microcontroller.
  • 13. The keyboard LED control system of claim 10, wherein the PWM signal and an enable input are provided by a graphics processing unit.
  • 14. The keyboard LED control system of claim 7, wherein the voltage boost circuit provides a supply voltage for a second LED array.
  • 15. A light emitting diode (LED) control system for a portable computing device, the LED control system comprising: a first LED array configured to provide light for a keyboard of the portable computing device;a second LED array configured to provide light for a backlight of the portable computing device; andan LED array controller, comprising: a boost converter configured to supply a voltage to the first and the second LED arrays, sink a first return current from the first LED array to ground, and control the first return current according to a first brightness input signal received at a first brightness input; andan LED driver configured to couple a second return current from the second LED array to ground, and control the second return current according to a second brightness input signal received at a second brightness input.
  • 16. The LED control system of claim 15, wherein the first brightness input signal is a first pulse width modulated (PWM) signal for controlling a brightness of the first LED array using the boost converter, and the second brightness input signal is a second PWM signal for controlling the brightness of the second LED array using the LED driver.
  • 17. The LED control system of claim 16, wherein the LED array controller further comprises a first enable input to control the boost converter and a second enable input to control the LED driver.
  • 18. The LED control system of claim 16, wherein the first LED array is coupled to the boost converter.
  • 19. The LED control system of claim 16, wherein the second PWM signal is generated based on a phase lock loop of a PWM generation circuit.
  • 20. The LED control system of claim 16, further comprising a microcontroller configured to provide the first PWM signal and the second PWM signal.
CROSS REFERENCE TO RELATED APPLICATIONS

This U.S. patent application claims priority under 35 USC 119(e) to U.S. Provisional Patent Application No. 61/636,590 filed Apr. 20, 2012 entitled “Display Backlight Driver IC” by Ascorra et al. which is incorporated by reference in its entirety for all purposes.

US Referenced Citations (30)
Number Name Date Kind
5454114 Yach et al. Sep 1995 A
5932894 Bakowski et al. Aug 1999 A
6761470 Sid Jul 2004 B2
6968065 Gu Nov 2005 B1
6980181 Sudo Dec 2005 B2
7233131 Lin et al. Jun 2007 B2
7235980 Pearson et al. Jun 2007 B2
7366891 Khanna et al. Apr 2008 B2
7535254 Case May 2009 B1
7990081 Chandran et al. Aug 2011 B2
20040249991 Ali et al. Dec 2004 A1
20060061347 Ford et al. Mar 2006 A1
20060109205 Deng May 2006 A1
20080001547 Negru Jan 2008 A1
20080265839 Yang Oct 2008 A1
20090026981 Li Volsi Jan 2009 A1
20100128064 Taylor et al. May 2010 A1
20100148679 Chen et al. Jun 2010 A1
20100176750 West Jul 2010 A1
20100194308 Zhao et al. Aug 2010 A1
20110043133 Van Laanen et al. Feb 2011 A1
20110089847 Qin Apr 2011 A1
20110267375 Yang et al. Nov 2011 A1
20110304597 Hyatt Dec 2011 A1
20120007564 Muraoka et al. Jan 2012 A1
20120074869 Cronmiller Mar 2012 A1
20120146552 West Jun 2012 A1
20120212354 Broga et al. Aug 2012 A1
20130088171 Fensore Apr 2013 A1
20130201704 Lin et al. Aug 2013 A1
Non-Patent Literature Citations (1)
Entry
Atmel LED Driver-MSL1060 Datasheet, 20 pp., (http://www.atmel.com/Images/f1—msl1060—ds.pdf).
Related Publications (1)
Number Date Country
20130278175 A1 Oct 2013 US
Provisional Applications (1)
Number Date Country
61636590 Apr 2012 US