The present disclosure relates generally to light emitting diodes (LEDs) and more particularly to pulse width modulation (PWM) for LED drivers.
Light emitting diodes (LEDs) often are used as light sources in liquid crystal displays (LCDs) and other displays. LED drivers for these displays often use pulse width modulation (PWM) signals to control the intensity of the light emitted by the LEDs while driving the LEDs at a fixed current, thereby achieving high color fidelity while varying intensity. However, video content is displayed as a series of frames, and if the PWM cycles of an LED driver are not carefully synchronized with the frame rate, visual noise, such as flickering, can occur at the display. One conventional synchronization scheme is to utilize a phase-locked loop (PLL) to directly synchronize the PWM cycles to the frame rate. However, PLLs are relatively expensive and complex to implement. Further, typical frame rates of 30 Hz to 120 Hz often are well below the effective reference frequency range of many PLL designs. For these applications, PLLs typically must have a very small loop bandwidth, leading to large components in the loop filter and a relatively long frequency locking time. These requirements often limit the suitability of conventional PWM synchronization techniques in video applications.
The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference symbols in different drawings indicates similar or identical items.
The term “completeable PWM cycle”, as used herein, refers to a PWM cycle of a PWM data signal that would complete before a frame boundary (i.e., a PWM cycle that, given its complete duration, would not cross a frame boundary). The term “incompleteable PWM cycle”, as used herein, refers to a PWM cycle of a PWM data signal that, given its complete duration, would not fully complete before a frame boundary (i.e., a PWM cycle that, if fully completed, would cross over a frame boundary). The term “incomplete PWM cycle”, as used herein, refers to the duration or portion of an incompleteable PWM cycle that is prematurely terminated at a frame boundary. The term “constant-level PWM cycle,” as used herein, refers to a PWM cycle that is driven at a constant reference level (e.g., ground/logic “0” or VDD/logic “1”) for its duration (full or prematurely terminated) regardless of the associated PWM duty ratio that normally is associated with the PWM cycle.
The techniques of the present disclosure are described in an example context whereby each PWM duty cycle initiates at a high level and then transitions to a low level after the corresponding duty ratio has been achieved (i.e., a “high-first” duty cycle). However, these techniques can be equally applied in a context whereby each PWM cycle initiates at a low level and then transitions to a high level to implement the corresponding duty ratio (i.e., a “low-first” duty cycle).
LCDs and other LED-based displays can operate in two PWM modes. In a first mode, the entire display frame is made available for PWM display (i.e., the PWM cycles can span the entire display frame duration). Thus, in this mode the active PWM period of the display frame is the entire display frame. However, the LEDs of LCD displays often exhibit a memory effect that can cause blurring in the displayed video. As such, it can be advantageous to “reset” the LEDs between each display frame by driving them with an increased current, thereby reducing the memory effect of the LEDs between display frames. Accordingly, in a second mode, the active PWM period is limited to only a portion of the display frame so that the remaining portion (the inactive PWM period) of the display frame duration can be used to perform a reset of the LEDs in preparation for the next display frame. Accordingly, for the first mode, the term “display frame” in relation to the PWM cycles refers to the entire display frame, and for the second mode, the term “display frame” in relation to the PWM cycles refers to the portion of the display frame that serves as the active PWM period of the display frame.
In the depicted example, the LED system 100 includes a video source 102 and a display device 104. The display device 104 includes an LED panel 106, a frame-synchronized (frame-sync) PWM generation module 110, and an LED driver 112. The video source 102 is configured to process video data to generate video signals to control the display device 104. The video source 102 can include, for example, a digital signal processor (DSP) configured to process video content encoded in accordance with one or more formats, such as an MPEG format, an H.264 format, a National Television Standards Committee (NTSC) format, a Phase Alternating Line (PAL) format, or a High Definition Television (HDTV) format. The video signals generated by the video source 102 include a frame timing reference 114, PWM duty data 115, as well as other video-related signaling (e.g., a pixel clock, pixel data, etc.). The frame timing reference 114 comprises digital or analog signaling representative of the timing of the frames (e.g., indicating the start of the display of each image frame) of the video content to be displayed at the LED panel 106 and is generated from the frame rate information associated with the video data. Examples of the frame rate information can include, for example, the Vertical Synchronization (VSYNC) signaling provided in NTSC, PAL, and HDTV systems, or the Vertical Blanking Interval used in Video Graphics Array (VGA)-based signaling and Digital Video Interface (DVI)-based signaling. The PWM duty data 115 represents the duty cycle ratio (variable or fixed) for the PWM cycles of each LED string or each set of LED strings of the LED panel 106. Additional signaling is generated in the LED system 100, including a PWM frequency indicator 120 that indicates the PWM cycle frequency (e.g., 240 PWM cycles per second) and a PWM resolution indicator 122 that indicates the step resolution of a PWM cycle (e.g., an 8-bit resolution or 255 (28−1) resolution steps. The PWM frequency indicator 120 can be generated in any of a variety of ways. To illustrate, a register, cache or memory can be used to store a value representative of a particular PWM frequency to be implemented, and thus the PWM frequency indicator 120 can be programmed by storing a particular value to the storage location corresponding to the PWM frequency indicator 120. Alternately, the PWM frequency indicator 120 can be programmed via a resistor or fuse. The PWM resolution indicator typically is application dependent, but in certain instances can be programmed in a similar manner.
The frame-sync PWM generation module 110 is configured to receive the frame timing reference 114, the PWM duty data 115, the PWM frequency indicator 120, and the PWM resolution indicator 122 and to generate a PWM data signal 116 that is synchronized to the frame rate represented in the frame timing reference 114 from these inputs. A single PWM data signal 116 can be used to drive all of the LED strings of the LED panel 106 (e.g., when driving a backlight panel of the LED panel). Alternately, the process of generating the PWM data signal 116 can be performed in parallel to generate a plurality of PWM data signals 116, each corresponding to a different set of one or more LED strings. For ease of convenience, a single PWM data signal 116 will be referenced herein, but the same principles apply for generating and processing a plurality of PWM data signals 116 for different LED strings of the LED display 106. Also for ease of illustration, the techniques of the present disclosure are described in an example context whereby the frame boundaries of the LED strings are synchronized (i.e., start simultaneous). However, it will be appreciated that it can be advantageous to offset or stagger the frame timings of the LED strings so as to reduce the instantaneous current load of the LED driver 112. The techniques disclosed herein apply equally to this staggered implementation.
As described in greater detail herein, the frame-sync PWM generation module 110 implements a technique whereby a new sequence of completeable PWM cycles is started at the start of each frame and whereby a constant reference level (e.g., a ground voltage or “0” volts) is driven on the PWM data signal 116 in place of incompleteable PWM cycles occurring at the ends of the sequences of completeable PWM cycles. The frame-sync PWM generation module 110 configures each completeable PWM cycle to have the PWM duty ratio identified by the PWM duty data 115. By providing a constant reference level for the PWM data signal 116 in place of an incompleteable PWM cycle, the display distortion exhibited by conventional PWM synchronization schemes can be reduced or eliminated. An example implementation of the frame-sync PWM generation module 110 and its related process are described below with reference to
The LED driver 112 is configured to drive an output voltage for one or more LED strings (of the LED panel 106) and control activation of the LED strings based on one or more PWM data signals 116 while regulating the current through the LED strings at a fixed current during the active portion of the corresponding PWM cycle (i.e., when the corresponding LED string is “on”). Typically, the LED driver 112 is configured to activate one or more LED strings when the PWM data signal 116 is at one reference level (e.g., VDD or logic “1”) and to deactivate one or more strings of LEDs when PWM data signal 116 is at another reference level (e.g., ground or logic “0”). Thus the duty ratio of a PWM cycle of the PWM data signal 116 represents and controls the average intensity of the corresponding LED string over the PWM cycle, while regulating the current through the LED strings at or near a fixed current maintains the desired output for the LED strings. Example implementations of the LED driver are disclosed in U.S. patent application Ser. No. 12/056,237, entitled “LED Driver with Dynamic Power Management” and filed on Mar. 26, 2008, U.S. patent application Ser. No. 12/183,492, entitled “LED Driver with Frame-Based Dynamic Power Management” and filed on Jul. 31, 2008, and U.S. Patent Application Ser. No. 61/036,053, entitled “LED Driver with Dynamic Power Management” and filed on Mar. 12, 2008, the entireties of which are incorporated by reference herein.
Chart 202 illustrates a conventional PWM signaling scheme whereby an incompleteable PWM cycle is prematurely terminated at a frame boundary 257 that marks the end of the display of a frame 258 and the start of the display of a frame 259, thereby resulting in an incomplete PWM cycle 256, and whereby an incompleteable PWM cycle is prematurely terminated at a frame boundary 261 that marks the end of the display of the frame 259 and the start of the display of the next frame (not shown), thereby resulting in an incomplete PWM cycle 260. Each incompleteable PWM cycle is generated in accordance with its corresponding PWM duty ratio. Accordingly, as illustrated by chart 202, the incomplete PWM cycle 256 is at a high reference level due to its high PWM duty ratio. In contrast, due to its low duty ratio, the incomplete PWM cycle 260 switches from the high reference to a low reference level before it is prematurely terminated changes. Thus, it will be appreciated that the average brightness of LED strings driven by the PWM signal of chart 202 is disproportionably greater for the frame 258 than for the frame 259 due to the difference between effective PWM duty ratios of the incomplete PWM cycles 256 and 260. This disproportionate change in average brightness over the frames can result in display distortion, thereby affecting viewing quality.
Chart 203 illustrates an example implementation of the frame-based PWM synchronization technique described herein. In the illustrated example, the PWM data signal 116 is configured such that a series of PWM cycles (e.g., PWM cycles 213, 214, 215) having a predetermined PWM duty ratio are driven on the PWM data signal 116 in response to a frame boundary 212 marking the start of the display of a frame 218. In one embodiment, the number of PWM cycles of the series is equal to a number of completeable PWM cycles expected to occur in the frame 218. As with the conventional technique illustrated by chart 202, the PWM synchronization technique of chart 203 starts the initial PWM cycle 213 of the series at the frame boundary 212. However, unlike the conventional technique whereby an incompleteable PWM cycle of the PWM data signal is permitted to continue up to the point of termination at the frame boundary in accordance with its associated PWM duty cycle, the PWM synchronization technique of chart 203 instead drives the PWM data signal 116 at a constant reference level (e.g., logic “0” or ground) for the duration of an incomplete PWM cycle 216 that starts at the end of the series of PWM cycles and that is terminated at the next frame boundary 220, regardless of the associated PWM duty ratio. Likewise, for a frame 219 initiated at the frame boundary 220, another series of PWM cycles 221, 222, and 223 having a predetermined PWM duty ratio is driven on the PWM data signal 116, whereby the number of PWM cycles of this series is equal to the number of completeable PWM cycles expected to occur for the frame 219. At the end of this series, the PWM data signal 116 is driven at the constant reference level for the duration of an incomplete PWM cycle 224 that starts at the end of the series and which is prematurely terminated by a frame boundary 226.
In other words, the PWM synchronization technique illustrated by chart 203 drives incompleteable PWM cycles at a fixed PWM duty ratio of 0% (regardless of the predetermined PWM duty ratio associated with the other PWM cycles of the frame) until they are terminated at the corresponding frame boundaries. In an alternate embodiment, rather than driving the PWM data signal 116 at a low reference level (e.g., logic “0” or ground) for the entire durations of incomplete PWM cycle, the PWM data signal 116 can instead be driven at a high reference level (e.g., logic “1” or VDD) for the durations of incompleteable PWM cycles. That is, the PWM synchronization technique illustrated by chart 203 can instead drive incompleteable PWM cycles at a fixed PWM duty ratio of 100% until they are terminated at the corresponding frame boundaries.
By driving incompleteable PWM cycles at the end of a frame at a constant reference level, the PWM synchronization technique disclosed herein achieves substantial linearity of average light intensity between frames, thereby reducing or eliminating the potential for display distortion that otherwise often arises in conventional PWM synchronization techniques.
The frequency synthesizer 308 receives the oscillation count n_osc, the clock signal 320, an indicator 328 of the resolution number of PWM duty ratio (n_pwm) (e.g., n_pwm=255 (28−1) for a PWM duty ratio represented by an 8-bit value), and an indicator (330) of an initial number of PWM cycles expected to occur during a frame (m_frame). From these inputs, the frequency synthesizer 308 generates two signals: a PWM duty resolution frequency signal 332 having a PWM duty resolution frequency (f_res); and a PWM frequency signal 334 having a PWM frequency (f_pwm). Alternatively, the frequency synthesizer 308 can provide the resolution number of the PWM duty ratio (n_pwm) to the PWM signal generator 312 for generating the PWM frequency signal 334 (f_pwm). An example method of generating these two signals is described below with reference to
The PWM signal generator 312 receives the PWM duty resolution frequency signal 332, the PWM frequency signal 334, the frame signal 322, and the PWM duty data 115. From these inputs, the PWM signal generator 312 generates the PWM data signal 116 such that a new PWM cycle is started at each of the frame boundaries, and such that any incompleteable PWM cycle at the end of a frame is implemented in the PWM data signal 116 as a constant reference level for its duration until terminated by the frame boundary.
Further, in at least one embodiment, the PWM signal generator 312 is configured to implement a self-learning process to dynamically determine the number of completeable PWM cycles that occur during a frame and adjust the process of generating the PWM data signal 116 accordingly. This self-learning process allows the PWM signal generator 312 to adapt to dynamic changes in the operating parameters of the LED system 100, including, but not limited to, changes in frame rate, changes to the PWM cycle frequency, and changes in the frequency f_osc of the oscillator 302, etc. An example method for generating the PWM data signal 116 from these inputs is described with respect to
The controller 310 is configured to receive the frame timing reference 114 and the oscillation count n_osc (signal 326) and is further configured to provide the frame signal 322, the indicator 328 of the resolution number of PWM duty ratio (n_pwm), and the indicator 330 of number of PWM cycles expected to occur during a frame (m_frame). The controller 310 further provides control signal 340 (C1) to control the operation of the counter 304, control signal 342 (C2) to control the operation of the frequency synthesizer 308, a control signal (not shown) to control the operation of the PWM signal generator 312, and a control signal 346 (osc_ctl) to control the operation of the oscillator 302. In one embodiment, the controller 310 is configured to provide the frame timing reference 114 directly as the frame signal 322. Alternately the controller 310 can derive the frame signal 322 from the frame timing reference 114. The controller 310 can determine the indicator 330 (m_frame) from the PWM frequency indicator 120. As noted above, the PWM frequency indicator 120 can be set via, for example, a programmable register or other storage device that stores a value representative of the desired number of PWM cycles per second, or via the voltage generated via a variable programmable resistor or fuse configured to indicate the desired number of PWM cycles per second. The controller 310 can determine the indicator 328 (n_pwm) from, for example, the PWM resolution indicator 122. Alternately, the controller 310 can be hardwired to provide a predetermined value for the indicator 328.
At block 402, an initialization event (e.g., a power-on reset) occurs, in response to which the controller 310 initializes the components of the frame-sync PWM generation module 110 by, for example, resetting counters, resetting the indicators to their initial or starting values, and the like.
At block 404, the counter 304 determines the number of oscillations of the clock signal 320 per frame by counting oscillations of the clock signal 320 between pairs of frame boundaries indicated by the frame signal 322 (i.e., n_osc=f_osc/f_frame) and provides the counted oscillations per frame as the oscillation count n_osc. To illustrate, for an oscillator frequency of 600 kHz and a frame rate of 60 frames per second (fps), the number of oscillations per frame would be 10000 oscillations per second (n_osc=10000=600 kHz/60 fps).
At block 405, the controller 310 can adjust (via control signal 346) the oscillator 302 for improved frequency control by comparing the absolute value of the difference between the oscillation count n_osc to a predetermined target oscillation count n_osc_tgt and adjusting the frequency of the oscillator 302 until the difference between the two is not greater than a threshold.
At block 406, the frequency synthesizer 308 determines the number of oscillations of the clock signal 320 per resolution step of the PWM cycles (n_res) using the oscillation count n_osc, the indicator 330 of the number of PWM cycles per frame (m_frame), and the indicator 328 of the resolution number of the PWM duty ratio (n_pwm) (i.e., n_res=n_osc/(m_frame×n_pwm). To illustrate, for an_oscillation count of 10000 (n_osc), 10 PWM cycles per frame (m_frame), and a PWM resolution of eight bits (n_pwm=255 steps (28−1)), the number of oscillations of the clock signal 320 per resolution step would be approximately 3.92 (n_res=3.92=10000/(10×255). In at least one embodiment, the frequency synthesizer 308 determines or uses only the integer portion of the determined value for n_res (e.g., n_res=integer(3.92)=3 in the above example).
At block 408, the frequency synthesizer 308 generates the PWM duty resolution frequency signal 332 having the PWM duty resolution frequency (f_res) using the clock signal 320 and the number of oscillations per resolution step (n_res) determined at block 406. In one embodiment, the PWM duty resolution frequency signal 332 is generated from the output of a counter (not shown) that counts the oscillations of the clock signal 320 by n_res (i.e., f_res=count f_osc by n_res).
At block 410, the frequency synthesizer 308 generates the PWM frequency signal 334 having the PWM frequency (f_pwm) based on the PWM duty resolution frequency signal 332 and the indicator 328 of the resolution number of the PWM duty ratio (n_pwm). In one embodiment, PWM frequency signal 334 is generated from the output of a counter (not shown) that counts the PWM duty resolution frequency signal 332 by the resolution number of the PWM duty ratio (n_pwm)(i.e., f_pwm=count f_res by n_pwm).
At block 412, the PWM signal generator 312 uses the PWM duty resolution frequency signal 332, the PWM frequency signal 334, the PWM duty ratio (PWM_duty) identified by the PWM duty data 115, and the frame signal 322 to generate the PWM data signal 116 having PWM cycles synchronized to the frame boundaries and with incompleteable PWM cycles driven at a constant reference level until their termination. Alternatively, the PWM signal generator 312 can use the indicator 328 (n_pwm) in place of the PWM frequency signal 334 in generating the PWM data signal 116.
For the process described below, the PWM data signal generator 312 utilizes variable mc. As noted above, the variable m_frame represents the number of completeable PWM cycles expected to occur in a frame. The variable mc represents a current count of completed PWM cycles during a frame, and which is used to determine whether the expected number of completeable PWM cycles is reached.
In response to being set to an initial state by the controller 310, at block 502 the PWM signal generator 312 sets the variable mc to zero (0) (i.e., mc=0). At block 504, the PWM signal generator 312 uses the frame signal 322 to determine whether a frame boundary has occurred. When a frame boundary is detected, at block 506 the PWM signal generator 312 generates a PWM duty cycle for the PWM data signal 116 using the PWM frequency signal 334, which demarks in time the duration of the PWM cycle being generated, the PWM duty resolution frequency signal 332, which demarks in time each of the resolution steps of the PWM cycle duration (e.g., 255 steps for an 8-bit resolution), and the PWM duty data 115, which signals how many resolution steps of the PWM cycle the PWM data signal is to be driven at a high reference level, with the remaining resolution steps of the PWM cycle being driven at the low reference level (or vice versa). Upon completion of the PWM cycle, the PWM signal generator 312 increments the variable mc by 1 (i.e., mc=mc+1) at block 508 to reflect the completion of another PWM cycle during the current frame.
At block 510, the PWM signal generator 312 compares the variable mc to m_frame to determine whether the expected number of completeable PWM cycles have been completed in the current frame. If the number of completed PWM cycles in the current frame is not equal to the number of expected completeable PWM cycles for a frame (i.e., mc=m_frame), the process returns to block 506 for the generation of the next completeable PWM cycle for the frame. Otherwise, the expected number of completeable PWM cycles has been generated for the current frame, and thus at block 512 the PWM signal generator 312 drives the PWM data signal 116 at a constant reference level to generate a constant-level PWM cycle on the PWM data signal 116 until the next frame boundary is identified at block 514. In response to the frame boundary, at block 516 the PWM signal generator 312 terminates the constant-level PWM cycle and resets the variable mc to zero. The process then returns to block 506 for the next frame. As illustrated by the process of
In this example, the variable m_pwm represents the number of completeable PWM cycles expected to occur in a frame and which is increased or decreased when the actual number of completed PWM cycles in a frame is greater than or less than the expected number, respectively. The variable mc represents a current count of completed PWM cycles during a frame, and which is used to determine whether the expected number of completeable PWM cycles is equal to the actual number.
In response to being set to an initial state by the controller 310, at block 602 the PWM signal generator 312 sets the variable m_pwm to the initial number of completeable PWM cycles expected per frame as represented by m_frame (i.e., m_pwm=m_frame). At block 604, the PWM signal generator 312 sets the variable mc to zero (0) (i.e., mc=0).
At block 606, the PWM signal generator 312 uses the frame signal 322 to determine whether a frame boundary has occurred. When a frame boundary is detected, at block 608 the PWM signal generator 312 generates a PWM duty cycle for the PWM data signal 116 using the PWM frequency signal 334, the PWM duty resolution frequency signal 332, and the PWM duty data 115.
While the PWM cycle is being generated on the PWM data signal 116, at block 610 the PWM signal generator 312 monitors the frame signal 322 to determine whether the PWM cycle being generated has completed before the next frame boundary. In other words, the PWM signal generator 312 determines whether the PWM cycle is to be a completed PWM cycle or an incompleteable PWM cycle. That a PWM cycle does not complete when it is expected to complete indicates that actual number of completed PWM cycles (as represented by the current value of mc) within a frame is less than the expected number of completeable frames for the frame (as represented by m_pwm). Accordingly, in the event that the PWM cycle did not complete before the frame boundary (i.e., it is an incompleteable PWM cycle), at block 612 the PWM signal generator 312 sets the variable m_pwm to the current value of the variable mc (i.e., m_pwm=mc) so as to set the expected number of PWM cycles per frame to the determined actual number of PWM cycles detected in the current frame and the PWM signal generator 312 resets the variable mc to zero. Further, the PWM signal generator 312 terminates generation of the current PWM signal and the process returns to block 608 for the next frame using the updated count of expected completeable PWM cycles represented by the updated value of the variable m_pwm.
Otherwise, if the PWM cycle completes before the frame boundary (i.e., the PWM cycle is a completed PWM cycle), at block 614 the PWM signal generator 312 increments the variable mc (i.e., mc=mc+1) to reflect that another PWM cycle has completed within the frame. At block 616, the PWM signal generator 312 determines whether the number of completed PWM cycles within the current frame is equal to the expected number of completeable PWM cycles (i.e., whether mc=m_pwm). If not equal, then at least one more completeable PWM cycle is expected for the current frame and thus the process returns to block 608 for generation of the next PWM cycle for the frame. Otherwise, if the actual number of completed cycles is equal to the expected number, it is expected that the next PWM cycle will be incompleteable due to an upcoming frame boundary. Accordingly, at block 618 the PWM signal generator 312 drives a constant-level PWM cycle on the PWM data signal 116 until the frame boundary is reached.
While driving the PWM data signal 116 at the constant reference level for the constant-level PWM cycle, at block 620 the PWM signal generator 312 uses the PWM duty resolution frequency signal 332 and one of the PWM frequency (f_pwm) or the resolution number of the PWM duty ratio (n_pwm) to determine whether it has been driving the PWM data signal 116 at the constant reference level for the duration of the constant-level PWM cycle. In other words, the PWM signal generator 312 determines whether the constant-level PWM cycle completed before the frame boundary. A completion of the constant-level PWM cycle before the frame boundary indicates that the actual number of completeable PWM cycles in the frame is greater than the expected number. In this event, at block 622 the PWM signal generator 312 increments m_pwm to reflect an increase in the expected number of completeable PWM cycles in a frame and the process returns to block 618 for generation of another constant-level PWM cycle until the frame boundary occurs. Otherwise, if the constant-level PWM cycle is not completed by the frame boundary, at block 624 the PWM signal generator 312 terminates the constant-level PWM cycle in response to the frame boundary and resets the variable mc to zero. The process then returns to block 608 for the next frame using the updated expected number of completeable PWM cycles per frame as represented by the value of the variable m_pwm.
As the process of
Other embodiments, uses, and advantages of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The specification and drawings should be considered exemplary only, and the scope of the invention is accordingly intended to be limited only by the following claims and equivalents thereof.
Number | Name | Date | Kind |
---|---|---|---|
4162444 | Rodgers | Jul 1979 | A |
4615029 | Hu et al. | Sep 1986 | A |
4649432 | Watanabe et al. | Mar 1987 | A |
4686640 | Simison | Aug 1987 | A |
4907862 | Suntola | Mar 1990 | A |
5025176 | Takeno | Jun 1991 | A |
5038055 | Kinoshita | Aug 1991 | A |
5508909 | Maxwell et al. | Apr 1996 | A |
5668611 | Ernstoff et al. | Sep 1997 | A |
5723950 | Wei et al. | Mar 1998 | A |
5844540 | Terasaki | Dec 1998 | A |
5898329 | Hopkins | Apr 1999 | A |
6281822 | Park | Aug 2001 | B1 |
6864641 | Dygert | Mar 2005 | B2 |
6937084 | Bowling | Aug 2005 | B2 |
6943500 | LeChevalier | Sep 2005 | B2 |
6995592 | Agarwal | Feb 2006 | B2 |
7106294 | Kumamoto et al. | Sep 2006 | B2 |
7126397 | Mok | Oct 2006 | B1 |
7176948 | Lewis | Feb 2007 | B2 |
7262724 | Hughes et al. | Aug 2007 | B2 |
7391280 | Hsu | Jun 2008 | B2 |
7436378 | Ito et al. | Oct 2008 | B2 |
7511545 | Kesler | Mar 2009 | B1 |
7550932 | Kung et al. | Jun 2009 | B2 |
7593243 | Ganev et al. | Sep 2009 | B2 |
7741885 | Guo et al. | Jun 2010 | B1 |
7800415 | Yedevelly et al. | Sep 2010 | B2 |
20040008159 | Cunha et al. | Jan 2004 | A1 |
20040208011 | Horiuchi et al. | Oct 2004 | A1 |
20040232964 | Wiktor et al. | Nov 2004 | A1 |
20040233144 | Rader et al. | Nov 2004 | A1 |
20040251942 | Chiu et al. | Dec 2004 | A1 |
20050275355 | Samuelsson | Dec 2005 | A1 |
20060064609 | Bryan | Mar 2006 | A1 |
20060164142 | Stanley | Jul 2006 | A1 |
20060186830 | Shami et al. | Aug 2006 | A1 |
20070080911 | Liu et al. | Apr 2007 | A1 |
20070182701 | Kim et al. | Aug 2007 | A1 |
20070253330 | Tochio et al. | Nov 2007 | A1 |
20080054815 | Kotikalapoodi | Mar 2008 | A1 |
20080074381 | Kumamoto | Mar 2008 | A1 |
20080297067 | Wang et al. | Dec 2008 | A1 |
20090073735 | Kesler | Mar 2009 | A1 |
20090128045 | Szczeszynski et al. | May 2009 | A1 |
20090187925 | Hu et al. | Jul 2009 | A1 |
20090230874 | Zhao et al. | Sep 2009 | A1 |
20090230891 | Zhao et al. | Sep 2009 | A1 |
20090273288 | Zhao et al. | Nov 2009 | A1 |
20090315481 | Zhao | Dec 2009 | A1 |
20100026203 | Zhao et al. | Feb 2010 | A1 |
Number | Date | Country |
---|---|---|
2003332624 | Nov 2003 | JP |
2005116199 | Apr 2005 | JP |
WO 2008 124718 | Oct 2008 | WO |
Entry |
---|
Susumu Tadakuma et al, “improved PWM Control for GTO Inverters with Pulse Number Modulation”, IEEE Transactions on Industry Applications, IEEE Service Center, Piscataway, NJ, US, vol. 32, No. 3, Jun. 1, 1996. |
Feng et al, “A new switched-capacitor frequency modulated driver for light emitting diodes”, Review of Scientific Instruments 78, 114701 (2007). |
PCT Search Report mailed Mar. 28, 2011 for International Application No. PCT/US2010/044067, 3 pages. |
Mc Nerney, Tim, “constant-current power supply for Luxeon 5W LED with low-voltage warning and shut-off Software Documentation, as shipped to Mali in first 45 prototypes,” Nov. 2004, www.designthatmatters.org/ke/pubs/kled-doc.txt, 5 pages. |
Maxim: “Application Note 810, Understanding Flash ADCs,” Oct. 2, 2001, 8 pages. |
National Semiconductor Data Sheet: “LM3432/LM3432B 6-Channel Current Regulator for LED Backlight Application,” May 22, 2008, pp. 1-18. |
U.S. Appl. No. 12/537,443, filed Aug. 7, 2009, entitled Pulse Width Modulation Frequency Conversion. |
U.S. Appl. No. 12/703,239, filed Feb. 10, 2010, entitled “Pulse Width Modulation With Effective High Duty Resolution”. |
U.S. Appl. No. 12/537,692, filed Aug. 7, 2009, entitled “Phase-Shifted Pulse Width Modulation Signal Generation”. |
U.S. Appl. No. 12/625,818, filed Nov. 25, 2009, entitled “Synchronized Phase-Shifted Pulse Width Modulation Signal Generation”. |
U.S. Appl. No. 12/703,249, filed Feb. 10, 2010, entitled “Duty Transition Control in Pulse Width Modulation Signaling”. |
Luke Huiyong Chung, Electronic Products: “Driver ICs for LED BLUs,” May 1, 2008, 3 pages. |
Akira Takahashi, Electronic Products: “Methods and features of LED drivers,” Mar. 2008, 3 pages. |
U.S. Appl. No. 12/340,985, filed Dec. 22, 2008, entitled “LED Driver With Feedback Calibration”. |
U.S. Appl. No. 12/326,963, filed Dec. 3, 2008, entitled “LED Driver With Precharge and Track/Hold”. |
U.S. Appl. No. 12/367,672, filed Feb. 9, 2009, entitled “Configuration for Dynamic Power Control in LED Displays”. |
U.S. Appl. No. 12/424,326, filed Apr. 15, 2009, entitled “Peak Detection With Digital Conversion”. |
U.S. Appl. No. 12/504,841, filed Jul. 17, 2009, entitled “Analog-To-Digital Converter With Non-Uniform Accuracy”. |
U.S. Appl. No. 12/690,972, filed Jan. 21, 2010, entitled “Serial Cascade of Minimum Tail Voltages of Subsets of LED Strings for Dynamic Power Contrl in LED Displays”. |
U.S. Appl. No. 12/363,607, filed Jan. 30, 2009, entitled “LED Driver With Dynamic Headroom Control”. |
International Application No. PCT/US2009/035284, Search Report and Written Opinion, Oct. 28, 2009, 11 pages. |
Texas Instruments Publication, “Interleaved Dual PWM Controller with Programmable Max Duty Cycle,” SLUS544A, (UCC28220, UCC28221) Sep. 2003, pp. 1-28. |
Notice of Allowance mailed Oct. 5, 2010 for U.S. Appl. No. 12/537,692, 13 pages. |
U.S. Appl. No. 13/025,201, filed Feb. 11, 2011 entitled, “Phase-Shifted Pulse Width Modulation Signal Generation Device and Method Therefor”. |
Notice of Allowance mailed Dec. 29, 2011 for U.S. Appl. No. 12/703,249, 24 pages. |
Non-Final Office Action mailed Oct. 20, 2011 for U.S. Appl. No. 12/537,443, 22 pages. |
Notice of Allowance mailed Jan. 25, 2012 for U.S. Appl. No. 12/537,443, 18 pages. |
Notice of Allowance mailed Mar. 22, 2012 for U.S. Appl. No. 12/625,818, 25 pages. |
Notice of Allowance mailed Jun. 8, 2012 for U.S. Appl. No. 12/537,443, 11 pages. |
Number | Date | Country | |
---|---|---|---|
20100085295 A1 | Apr 2010 | US |