Disable highperf mode in the peakmeter for swcodec targets, as it makes no sense. Improves responsiveness a lot with a peakmeter-enabled wps on targets with slow lcd updates (e.g. G5). Added a comment why highperf mode is needed for MAS targets.

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@15140 a1c6a512-1295-4272-9138-f99709370657
This commit is contained in:
Jens Arnold 2007-10-16 08:34:51 +00:00
parent e9feb063f5
commit 8b44601a7c

View file

@ -1318,10 +1318,15 @@ int peak_meter_draw_get_btn(int x, int y[], int height, int nb_screens)
long next_refresh = current_tick; long next_refresh = current_tick;
long next_big_refresh = current_tick + HZ / 10; long next_big_refresh = current_tick + HZ / 10;
int i; int i;
#ifndef SIMULATOR #if (CONFIG_CODEC == SWCODEC) || defined(SIMULATOR)
bool highperf = !ata_disk_is_active();
#else
bool highperf = false; bool highperf = false;
#else
/* On MAS targets, we need to poll as often as possible in order to not
* miss a peak, as the MAS does only provide a quasi-peak. When the disk
* is active, it must not draw too much CPU power or a buffer overrun can
* happen when saving a recording. As a compromise, poll only once per tick
* when the disk is active, otherwise spin around as fast as possible. */
bool highperf = !ata_disk_is_active();
#endif #endif
bool dopeek = true; bool dopeek = true;