#
…

2022-06-05

00:03nuh^ has joined #asahi-dev
00:31Owsley has joined #asahi-dev
02:19ModR\M has quit [Ping timeout: 480 seconds]
02:27ModR\M has joined #asahi-dev
02:32nuh^ has quit [Ping timeout: 480 seconds]
02:36ModR\M has quit [Ping timeout: 480 seconds]
02:46ModR\M has joined #asahi-dev
02:47phiologe has joined #asahi-dev
02:50PhilippvK has quit [Ping timeout: 480 seconds]
02:54ModR\M has quit [Ping timeout: 480 seconds]
03:03ModR\M has joined #asahi-dev
03:05nuh^ has joined #asahi-dev
03:31nuh^ has quit [Ping timeout: 480 seconds]
03:33pyropeter2 has joined #asahi-dev
03:34pyropeter1 has quit [Ping timeout: 480 seconds]
05:00ModR\M has quit [Remote host closed the connection]
05:05ModR\M has joined #asahi-dev
05:10jluthra has quit [Remote host closed the connection]
05:11jluthra has joined #asahi-dev
05:30ModR\M has quit [Remote host closed the connection]
05:55ModR\M has joined #asahi-dev
06:06ModR\M has quit [Remote host closed the connection]
06:07chadmedmarcan: i think those regs count up in microjoules
06:08chadmedif i take the difference before and after running bench and divide by the elapsed microseconds, i get values in microwatts that are very very similar to the values i got from the SMC for the pstates where that worked
06:10chadmedseems true for the firestorm cores at least, im not too sure on the cluster counters or icestorm since i couldnt verify with the SMC but they behave roughly how i'd expect them to (i.e. the values arent totally insane)
06:21chadmedsurely they wouldnt count in non-reasonable units (tens/hundreds of microjoules, etc)
06:29chadmedyeah im only really unsure about the p cluster value
06:44bisko has joined #asahi-dev
06:46marcanit's possible the init is still wrong
06:48chadmedim only unsure because i refuse to believe the entire cluster is only using 200uW on top of the actual core
06:48chadmedeven though the numbers line up with what i had from the SMC...
06:48bisko has quit []
06:49chadmedthe second p cluster on the m1 max gives the exact same values too
06:49marcanI assume you duplicated the init for the p cluster onto the second one?
06:50marcan(including all the hardcoded stuff that wasn't properly broken out)
06:50chadmedyeah so im not surprised it would give the same results, just wanted to check
06:51marcanlet me see if I can de-uglify the init and make sure I didn't miss anything
06:52chadmedi know at least that final set64 is unnecessary, because i didnt copy it and the second cluster still gave me the same values
06:52ModR\M has joined #asahi-dev
06:52chadmedsetting it didnt affect the numbers either
06:54marcanI'll probably make m1n1 init this eventually since it probably makes sense for it to deal with this and let Linux just read the data
06:55chadmedyeah of course
06:56chadmedhaving sane data at this stage at least lets us bring EAS online without having to anything dodgy in cpufreq
06:57chadmedjust update the opp tables and let register_em_with_opp() deal with it (which currently silently fails since we dont have enough data for it in the dt)
07:32bisko has joined #asahi-dev
07:34fetsorn has joined #asahi-dev
07:34fetsorn has quit [Remote host closed the connection]
07:40bisko has quit [Ping timeout: 480 seconds]
07:57nuh^ has joined #asahi-dev
08:09nsklaus has joined #asahi-dev
08:23nuh^ has quit [Ping timeout: 480 seconds]
08:26ModR\M has quit [Ping timeout: 480 seconds]
09:00___nick___ has joined #asahi-dev
09:22chadmed has quit [Remote host closed the connection]
09:44jeffmiw has quit [Ping timeout: 480 seconds]
09:59chadmed has joined #asahi-dev
11:18bps has joined #asahi-dev
12:21bps has quit [Ping timeout: 480 seconds]
12:31jeffmiw has joined #asahi-dev
12:56roxfan has quit [Remote host closed the connection]
12:58roxfan has joined #asahi-dev
13:12amarioguy has quit [Remote host closed the connection]
13:45jannaudcp is strange, on the internal display (mbp 14") a modeset (changing just the refresh rate) causes freeing and reallocating of buffers. That doesn't happen on mac mini or mac studio on mode changes
13:50nuh^ has joined #asahi-dev
13:55Dcow[m]what about m1 air or mbp13 ?
14:02jannauthe annoying part is that dcp crashes after what I believe is the last re-allocation
14:07pashencija[m] has joined #asahi-dev
14:21the_lanetly_052__ has joined #asahi-dev
14:24nuh^ has quit [Ping timeout: 480 seconds]
14:27the_lanetly_052___ has quit [Ping timeout: 480 seconds]
14:57amarioguy has joined #asahi-dev
14:58___nick___ has quit []
15:00___nick___ has joined #asahi-dev
15:00___nick___ has quit []
15:02___nick___ has joined #asahi-dev
15:36jannauissue was unrelated to the buffer allocation
15:56ModR\M has joined #asahi-dev
16:02ModR\M has quit [Read error: No route to host]
16:04ModR\M has joined #asahi-dev
16:04bps has joined #asahi-dev
16:25ModR\M has quit [Read error: No route to host]
16:25ModR\M has joined #asahi-dev
16:26kov has joined #asahi-dev
16:45scientist has joined #asahi-dev
16:51ModR\M has quit [Ping timeout: 480 seconds]
16:52unevenrhombus[m] has quit []
16:52unevenrhombus[m] has joined #asahi-dev
16:53unevenrhombus[m] has quit []
16:53unevenrhombus[m] has joined #asahi-dev
17:24bisko has joined #asahi-dev
17:32bisko has quit [Ping timeout: 480 seconds]
17:34j`eymarcan: im assuming you know about pwm?
17:35j`eydoes "@period: PWM period (in nanoseconds)" mean the entire off and on period?
17:35j`eyand "@duty_cycle: PWM duty cycle (in nanoseconds)" is the portion of the '@period' where it's on
17:36marcancorrect, I would say
17:36marcanduty cycle is more often a fraction but if it says nanoseconds then it's relative to period
17:36j`eythat makes somewhat sense then.. for some reason I thought 'period' was the off period
17:37j`ey(up until now, and was getting confused by the code)
17:48mpsduty cycle in pwm usually means how long in percent signal is active
17:48scientist has quit [Quit: WeeChat 3.4.1]
17:49j`eyyeah, i was just confused because in linux it's represented by nanoseconds
17:49mpsah, didn't knew that
18:01kubes has joined #asahi-dev
18:01handofstand[m] has joined #asahi-dev
18:14the_lanetly_052__ has quit [Ping timeout: 480 seconds]
19:01kubes has quit [Quit: Leaving]
19:46bps has quit [Ping timeout: 480 seconds]
19:55amarioguysven: not sure if you saw, but i offered to take up the i2c stuff, figured i'd help contribute to that
19:55amarioguyif we have someone on that no worries
19:57svenI’m about to go to bed but I can give you some pointers tomorrow
19:57amarioguyalright sounds good
20:08___nick___ has quit [Ping timeout: 480 seconds]
20:44bps has joined #asahi-dev
21:12fetsorn has joined #asahi-dev
21:15fetsorn has quit []
21:18fetsorn has joined #asahi-dev
21:22fetsorn has quit [Remote host closed the connection]
21:40lrea^ has joined #asahi-dev
21:55kaprests has joined #asahi-dev
21:55joske has joined #asahi-dev
21:55joske has quit []
21:59kaprests has left #asahi-dev [#asahi-dev]
22:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
22:02kaprests has joined #asahi-dev
22:51kaprests has quit [autokilled: Possible botnet activity. Mail support@oftc.net with questions. (2022-06-05 22:51:21)]
22:55kaprests has joined #asahi-dev
23:14c10l has quit [Quit: Bye o/]
23:15c10l has joined #asahi-dev
23:18c10l7 has joined #asahi-dev
23:25c10l has quit [Ping timeout: 480 seconds]
23:34c10l7 has quit []
23:35c10l7 has joined #asahi-dev
23:40lrea^ has quit [Ping timeout: 480 seconds]
…