#asahi-dev · 2026-04-12 12:02
tryhard[m]other q: is there anyway to disable uboot console? my o key doesnt work so i cant type boot. ext keyboard also doesnt work.#asahi-dev · 2026-04-12 12:01
chaos_princessyes, it is in the installed fedora #asahi-dev · 2026-04-12 12:00
tryhard[m]in the fedora installation?#asahi-dev · 2026-04-12 11:56
chaos_princessit is under /boot, next to vmlinuz files#asahi-dev · 2026-04-12 11:55
tryhard[m]where is it?#asahi-dev · 2026-04-12 11:55
tryhard[m]didnt know it existed#asahi-dev · 2026-04-12 11:50
chaos_princessis the fedora one not working?#asahi-dev · 2026-04-12 11:49
tryhard[m]chaos_princess: can u send me your .config or some other up to date one?#asahi-dev · 2026-04-11 21:46
tryhard[m]lemme see#asahi-dev · 2026-04-11 21:46
chaos_princesslook at what aop and aop_audio do#asahi-dev · 2026-04-11 21:46
tryhard[m]so#asahi-dev · 2026-04-11 21:46
chaos_princessno.#asahi-dev · 2026-04-11 21:46
tryhard[m]yeah#asahi-dev · 2026-04-11 21:45
chaos_princessyour two drivers?#asahi-dev · 2026-04-11 21:45
tryhard[m]chaos_princess: should i make them talk in shared memory?#asahi-dev · 2026-04-11 21:30
tryhard[m]i thought u talk about .c. nvm then#asahi-dev · 2026-04-11 21:29
chaos_princessit is in rust/kernel/soc/apple/rtkit.rs#asahi-dev · 2026-04-11 21:29
chaos_princessno?#asahi-dev · 2026-04-11 21:29
tryhard[m]drivers/soc/apple#asahi-dev · 2026-04-11 21:28
tryhard[m]its in soc/apple#asahi-dev · 2026-04-11 21:28
chaos_princessyou can use bindings:: from that one#asahi-dev · 2026-04-11 21:28
chaos_princessthat part is in the kernel crate, no in the drivers crate#asahi-dev · 2026-04-11 21:28
tryhard[m]there is rtkit.c and there is rtkit.rs#asahi-dev · 2026-04-11 21:28
tryhard[m]but that like uses bindings no?#asahi-dev · 2026-04-11 21:26
chaos_princessthats because we have rtkit abstractions#asahi-dev · 2026-04-11 21:26
tryhard[m]but asahi drivers use rtkit#asahi-dev · 2026-04-11 21:26
chaos_princessbasically, you aren't supposed to use anything under bindings:: from drivers directly, if you do that, it is not upstreamable#asahi-dev · 2026-04-11 21:25
tryhard[m]yes#asahi-dev · 2026-04-11 21:25
chaos_princessi mean full abstractions.#asahi-dev · 2026-04-11 21:25
tryhard[m]that's the point of it#asahi-dev · 2026-04-11 21:24
tryhard[m]i mean creating bindings is not really hard#asahi-dev · 2026-04-11 21:24
tryhard[m]i think it should be easy#asahi-dev · 2026-04-11 21:23
chaos_princessthough genpd bindings don't look that hard to make#asahi-dev · 2026-04-11 21:22
chaos_princessyea, kinda why i have the c/rust split :P#asahi-dev · 2026-04-11 21:22
tryhard[m]i thought at first to use pmdomain in rust but it seems there are no bindings for it#asahi-dev · 2026-04-11 21:21
chaos_princessif you look at the pmp v2 driver, you will see how the "pmp-reporting-entry" drivers just delegate to "pmp-reporting". You should do something like that, but in your case you have just 2 drivers instead of 3 like for v2#asahi-dev · 2026-04-11 21:20
tryhard[m]chaos_princess: ok that's good.#asahi-dev · 2026-04-11 21:19
tryhard[m]because i need to send the devpwr messages whenever the kernel asks for.#asahi-dev · 2026-04-11 21:19
chaos_princessin your case you want your driver for "entry" devices to call a function on your main driver, that will in turn send a rtkit message#asahi-dev · 2026-04-11 21:18
chaos_princessmy "rust for init, c for actual communication" split works because the rtkit and sram parts of pmp are effectively independent#asahi-dev · 2026-04-11 21:17
chaos_princessnot sure why you want to reinit in c#asahi-dev · 2026-04-11 21:03
tryhard[m]i need then to send a message through rtkit, but i think that the main driver is already initializaing rtkit so it might not be a good idea to reinit in c?#asahi-dev · 2026-04-11 19:08
chaos_princessthe .data in struct of_device_id is just whatever model-specific data the driver wants to have. i store it in apple_pmp_report.offsets, and then use it to calculate the addresses to read/write, such as here https://github.com/AsahiLinux/linux/blob/asahi-wip/drivers/pmdomain/apple/pmp-report.c#L110#asahi-dev · 2026-04-11 19:04
tryhard[m]it justs seems that apple_pmp_report_of_match uses those#asahi-dev · 2026-04-11 19:03
chaos_princessjust offsets into said shared memory area that the driver and PMP use. v2-exclusive stuff.#asahi-dev · 2026-04-11 19:02
tryhard[m]so what are those apple_pmp_report_offsets?#asahi-dev · 2026-04-11 18:55
chaos_princessso, some nodes in the dt have "power-domains" that links to another device (pmp-report-entry in v2's case). if those are set, then before using the device, linux powers it on using the genpd callbacks https://github.com/AsahiLinux/linux/blob/asahi-wip/drivers/pmdomain/apple/pmp-report.c#L166#asahi-dev · 2026-04-11 18:53
tryhard[m]yes i saw that. then i guess the job is simpler now. although i don't understand how exactly i get the reporting in the driver from the dtsi.#asahi-dev · 2026-04-11 18:51
chaos_princessi don't. v2 no longer sends messages for that but instead has a bitmap in shared memory. https://github.com/AsahiLinux/linux/blob/asahi-wip/drivers/pmdomain/apple/pmp-report.c#L114#asahi-dev · 2026-04-11 18:48
tryhard[m]chaos_princess: where do you actually send the messages in your driver for devpwr?