Viresh Kumar <viresh.kumar@xxxxxxxxxx> writes: > On 04-11-24, 20:14, Andreas Kemnade wrote: >> no clear idea how. What aliases should I add? The cpufreq-dt-platdev is >> not a real driver, so I could not create mod_devicetable aliases to >> match a given device. It constructs a device under certain conditions >> depending on the board compatible, so no simple list of compatibles, it >> contains allow and blocklists. >> >> cpufreq-dt then binds to that device and that one can be built as a >> module (which then made cpufreq-dt-platdev also a module, causing the >> trouble). I do not see any benefit from having cpufreq-dt-platdev as a >> module. ti-cpufreq has a similar role and is also just builtin. >> It does itself no real work but provides a device cpufreq-dt then binds >> to. >> >> Handling module removal would probably need to be added and tested. I >> feel not comfortable having such as a regression fix and for stable. > > Applied this patch for now (with some changes to commit log), as there is no > clean way to fix this for now. Got reports from other folks too about it. Oops, I thought I had replied to this earlier after detailed explanation from Andreas, but I guess I didn't. Thanks for applying. Kevin