> Am 14.01.2020 um 22:00 schrieb Tony Lindgren <tony@xxxxxxxxxxx>: > > * H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [200114 18:40]: >> I have checked our tree and it is already built into a separate module with >> >> sound/soc/ti/aess/omap-aess-core.c: { .compatible = "ti,omap4-aess", }, >> >> So >> >>> target-module@f1000 { /* 0x401f1000, ap 32 20.0 */ >>> ... >>> aess: aess { >>> compatible = "ti,omap4-aess"; >>> status = "disabled"; >>> }; >>> }; >> >> would be what we will need. > > OK good to hear. I have cleaned up my working tree and added your patches and the one above (without status = "disabled" and could a) boot well b) see that the (non-working) aess driver module is loaded through child node So you can add my Tested-by: Nikolaus Schaller <hns@xxxxxxxxxxxxx> BR and thanks, Nikolaus