On Tue, Mar 21, 2023 at 7:19 PM Ralf Ramsauer <[email protected]> wrote: > > Hi, > > On 17/03/2023 15:19, Daniel Baluta wrote: > > On Fri, Mar 17, 2023 at 4:13 PM Ralf Ramsauer > > <[email protected]> wrote: > >> > >> > >> > >> On 17/03/2023 14:49, Daniel Baluta wrote: > >>> > >>> What you can already do is pushing the setup into an initramfs. > >>> > >>> > >>> This won't really help in our case. Our driver (Sound Open Firmware) > >>> runs at boot and somehow > >>> it already expects that the jailhouse to be enabled in a controlled way. > >> > >> Why? What happens? > > > > Our driver loads the "inmate" firmware like here: (1) > > > > https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/sof/core.c#L238 > > > > And then later "starts" it, like here (2) > > > > https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/sof/core.c#L252 > > > > By the point our SOF driver code reaches point (1) we already need the > > jailhouse hypervisor to already > > have been setup and the inmate enabled. > > I still don't get why that must be the case. Why can't Jailhouse be > enabled later? > > Anyway - You could have both as kernel modules: snd-sof and jailhouse, > and first enable jailhouse, and after that loading snd-sof.
Thanks. It looks like we don't really have other choices since jailhouse module doesn't export control functions to other modules. Thanks for your answer. -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/CAEnQRZCjODX%3D6cOzFnC%3DGqRL-bA9ozG3wvUrsUcwB6d7r7H_Xw%40mail.gmail.com.
