On 27/09/22 12:10, Tony Lindgren wrote: > Hi, > > * Romain Naour <romain.naour@xxxxxxxx> [220921 08:13]: >> Ok, I understand what's going on... >> >> The issue appear on the merge commit since on a omap side there was the switch >> to ti-sysc (devicetree interconnect description) and on upstream side there was >> a change on driver core behavior with fw_devlink=on being set by default: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ea718c699055c8566eb64432388a04974c43b2ea > > OK good to hear it's not the change to ti-sysc. That should be all pretty > much standard Linux driver related changes. > >> Actually the issue is really on the TI's prueth and IEP driver whith >> fw_devlink=on. The IEP driver probe correctly with fw_devlink=permissive. > > Argh not again, the fw_devlink changes seem to be causing all kind of > issues. Any ideas what the issue here might be? It might be worth testing > with v6.0-rc7 too as it has a series of fixes to related issues. > Could you also try [1] from Puranjay's series? He did have to rework pru_rproc_get()/pru_rproc_put() a bit to fix few probe failures seen only on > 5.11 kernels. [1] https://lore.kernel.org/netdev/20220406094358.7895-3-p-mohan@xxxxxx/ -- Regards Vignesh
