[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: LCD timing

In 2.4.19 you can enable FAST_TIMERS and use schedule_usleep.
You'll have to test if this works better than a polling solution
or not.

I assume that you don't write to the LCD very often? How much 
do you write each time? (1024 is a lot for a LCD, is it a large LCD?)
It may be ok to busy-wait for the LCD if you write small amounts
of data and not very often.

-----Original Message-----
From: owner-dev-etrax@xxxxxxx.com]On">mailto:owner-dev-etrax@xxxxxxx.com]On
Behalf Of Szabo, Tamas
Sent: Friday, November 22, 2002 8:25 AM
To: dev-etrax
Subject: LCD timing


Currently I write a driver for LCD (ks0108 based). Unfortunately writing to
the display data RAM is very  slow (~10 us) and if I write 1024 bytes it
takes more than 10 ms. But as this routine in the kernel, most of this time
is just wasted. Since the display has no interrupt pin the checking of busy
is only possible with polling (continuously reading status register).

Has any suggestion to increase the efficiency?

Thanks in advance,

Problems with Windows - Reboot.
Problems with Linux       - Be root.

The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only. 

This email and any response may be monitored by Sony United Kingdom Limited.