SAMA5 LCDC: Back out the delay kludge. Increase the LCDC input clock from MCK to 2*MCK was sufficient for all timing instbility problems
This commit is contained in:
parent
6298ead42c
commit
78adc980e6
@ -203,19 +203,6 @@
|
||||
#define BOARD_LCDC_PIXELCLOCK \
|
||||
(BOARD_LCDC_HSPERIOD * BOARD_LCDC_VSPERIOD * BOARD_LCDC_FRAMERATE)
|
||||
|
||||
/* This specifies a delay after enabling the LCDC. This was found
|
||||
* experimentally and is very much a kludge. I presume that a delay of a
|
||||
* couple of frame times allows some unstable clocking to synchronize before
|
||||
* we start thrashing the framebuffer? But I am not sure why this is
|
||||
* necessary and, in fact, is certainly not necessary in other LCDC
|
||||
* configurations. Perhaps the delay would not be necessary if timings were
|
||||
* more precise?
|
||||
*
|
||||
* Delays are in units of microseconds.
|
||||
*/
|
||||
|
||||
#define BOARD_LCDC_ENABLE_DELAY (50*1000)
|
||||
|
||||
/* Backlight prescaler value and PWM output polarity */
|
||||
|
||||
#define BOARD_LCDC_PWMPS LCDC_LCDCFG6_PWMPS_DIV1
|
||||
|
Loading…
Reference in New Issue
Block a user