;;-*-Lisp-*- (in-package goal) ;; name: timer-h.gc ;; name in dgo: timer-h ;; dgos: GAME, ENGINE ;; There are two sources for timing: ;; - EE TIMER1, used for the frame profiler. There are 9765 counts of this per frame. It gets reset in drawable. ;; - The "stopwatch" system, used for reading the CPU clock cycle counter, at 300 MHz (32-bit) ;; The Emotion Engine has 4 hardware timers, timer1 is used as the (defconstant TIMER0_BANK #x10000000) ;; has HOLD register! (defconstant TIMER1_BANK #x10000800) ;; has HOLD register! (defconstant TIMER2_BANK #x10001000) ;; does NOT have HOLD register! (defconstant TIMER3_BANK #x10001800) ;; does NOT have HOLD register! ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; PC Port Timer ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (defmacro get-cpu-clock () "Read the 300 MHz clock." ;; __read-ee-timer is a 300 MHz timer from the C Kernel. ;; it's a real timer. `(the uint (logand #xffffffff (__read-ee-timer))) ) (defmacro get-bus-clock/256 () "Read the 150 MHz / 256 clock." ;; 300 MHz / (2^9) `(the uint (logand #xffffffff (shr (__read-ee-timer) 9))) ) (#when PC_PORT ;; the bus clock can be reset, which just stores the current count here. (define *timer-reset-value* (the uint 0)) ) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Timer HW ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (defenum timer-clock-selection :type uint8 (busclk 0) (busclk/16 1) (busclk/256 2) (hblank 3) ) ;; this matches the Tn_MODE register structure of the ps2 EE timers. ;; Only the lower 32 bits of these registers are usable, and the upper 16 hardwired to zero (deftype timer-mode (uint32) ((clks timer-clock-selection :offset 0 :size 2) (gate uint8 :offset 2 :size 1) ;; gate function enable (gats uint8 :offset 3 :size 1) ;; gate selection: 0 = hblank, 1 = vblank ;; gate mode: ;; 0: count while gate signal is low ;; 1: start when gate signal rises ;; 2: start when gate signal falls ;; 3: start when gate signal rises/falls (gatm uint8 :offset 4 :size 2) (zret uint8 :offset 6 :size 1) ;; zero return: clear counter when equal to reference value (cue uint8 :offset 7 :size 1) ;; count-up enable (cmpe uint8 :offset 8 :size 1) ;; compare-interrupt enable (ovfe uint8 :offset 9 :size 1) ;; overflow-interrupt enable (equf uint8 :offset 10 :size 1) ;; equal-flag (ovff uint8 :offset 11 :size 1) ;; overflow-flag ) :method-count-assert 9 :size-assert #x4 :flag-assert #x900000004 ) ;; this matches an EE timer (without a HOLD register, timers 2 and 3) ;; Each register is 128-bits wide, but only the lower 32-bits are usable, and the upper ;; 16-bits of that are hardwired to zero. (deftype timer-bank (structure) ((count uint32 :offset 0) (mode timer-mode :offset 16) (comp uint32 :offset 32) ) :method-count-assert 9 :size-assert #x24 :flag-assert #x900000024 ) ;; this matches an EE timer (with a HOLD register, timers 0 and 1) (deftype timer-hold-bank (timer-bank) ((hold uint32 :offset 48) ) :method-count-assert 9 :size-assert #x34 :flag-assert #x900000034 ) ;; stopwatches are used to measure CPU clock cycles ;; they don't use the timer above, but instead the Count COP0 register ;; which counts CPU clock cycles directly (deftype stopwatch (basic) ((prev-time-elapsed time-frame :offset-assert 8) (start-time time-frame :offset-assert 16) (begin-level int32 :offset-assert 24) ) :method-count-assert 9 :size-assert #x1c :flag-assert #x90000001c ) ;; Confusing! What IS this measuring exactly? Hmm... ;; this is set by default for NTSC, it will later be changed if PAL. (define *ticks-per-frame* (/ 2500000 256)) ;; 2 500 000 / 256 = 9765 (defun timer-init ((timer timer-bank) (mode timer-mode)) "Initiate a timer, start counting at a rate of 1 every 256 bus clocks (BUSCLK: ~147.456MHz)." (set! (-> timer mode) mode) (set! (-> timer count) 0) ) ;; needs PS2 TIMER porting (#unless PC_PORT (timer-init (the-as timer-bank TIMER1_BANK) (new 'static 'timer-mode :clks (timer-clock-selection busclk/16) :cue 1)) ) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Profiler ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; The profiler uses the EE Timer 1 to record how long is spent in each part of the frame. ;; There is a EE and VU1 profiler. The EE profiler relies on code manually reporting how long ;; it takes to run, and the VU1 profiler uses VIF interrupts to do this automatically on ;; microprogram completion. ;; A single thing in the profiler (deftype profile-frame (structure) ((name symbol :offset-assert 0) (time-stamp uint32 :offset-assert 4) (color rgba :offset-assert 8) ) :method-count-assert 9 :size-assert #xc :flag-assert #x90000000c ) (defmethod inspect profile-frame ((obj profile-frame)) (let ((this-frame obj)) (format #t "[~8x] profile-frame~%" this-frame) (format #t "~Tname: ~A~%" (-> this-frame name)) (format #t "~Ttime-stamp: ~D~%" (-> this-frame time-stamp)) (format #t "~Tcolor: ~D ~D ~D~%" (-> this-frame color r) (-> this-frame color g) (-> this-frame color b)) ) obj ) ;; A "bar" to display all the timed events (declare-type dma-buffer basic) (deftype profile-bar (basic) ((profile-frame-count int32 :offset-assert 4) (cache-time time-frame :offset-assert 8) (data profile-frame 1024 :inline :offset-assert 16) ) :method-count-assert 14 :size-assert #x4010 :flag-assert #xe00004010 (:methods (new (symbol type) _type_ 0) (get-last-frame-time-stamp (_type_) uint 9) (reset (_type_) _type_ 10) (add-frame (_type_ symbol rgba) profile-frame 11) (add-end-frame (_type_ symbol rgba) profile-frame 12) (draw (_type_ dma-buffer int) float 13) ) ) (defmacro add-ee-profile-frame (name &key (r 0) &key (g 0) &key (b 0) &key (a #x80)) `(if *debug-segment* (add-frame (-> *display* frames (-> *display* on-screen) frame profile-bar 0) ,name (new 'static 'rgba :r ,r :g ,g :b ,b :a ,a) ) ) ) ;; tentative name (defmethod get-last-frame-time-stamp profile-bar ((obj profile-bar)) "Returns the timestamp of the last (non-remaining) frame on the profiler bar." (-> obj data (+ (-> obj profile-frame-count) -2) time-stamp) )