Could you please give a bit more context on what error you see
when this happens?
I get Oops. This is what happens with all other patches in this
series and only this one reverted:
root@APL:~# rmmod snd_soc_sst_bxt_rt298
root@APL:~# rmmod snd_soc_hdac_hdmi
root@APL:~# rmmod snd_soc_skl
Thanks, Amadeusz. I think the order in which the drivers are
is what's causing the oops in your case. With SOF, the order we
1. rmmod sof_pci_dev
2. rmmod snd_soc_sst_bxt_rt298
3. rmmod snd_soc_hdac_hdmi
Well, there is nothing enforcing the order in which modules can be
unloaded (and I see no reason to force it), as you can see from
following excerpt, you can either start unloading from
snd_soc_sst_bxt_rt298 or snd_soc_skl, and yes if you start from
snd_soc_skl, there is no problem.
I am good with this patch. I just wanted to understand why we werent
seeing this error with SOF. Sure, there's nothing enforcing the order
in which modules are unloaded but there must be a logical order for
Pierre, can you please comment on it. I vaguely remember discussing
this with you last year.