Hi @henrique.tx
thank you very much for your answer.
I agree that probably the best option is to leverage on Dynamic Debug approach.
I read the documentation you linked and here is what I learned/understood:
/proc/dynamic_debug/control
exists, and so kernel of Torizon OS has Dynamic Debug - goodhead /proc/dynamic_debug/control
shows the currently configured behaviour, and the items I see are all related tonet/bluetooth/bnep/core.c
If I would like disabling debug logging for module imx_rpmsg_tty
I should run the following command
echo "module imx_rpmsg_tty -p" > /proc/dynamic_debug/control
But nothing changes and I get all the debug messages in journalctl
.
From the documentation you linked I read that I can specify the Dynamic Debug while loading the module, and in Torizon OS I load it using /etc/modules-load.d
as suggested by @jeremias.tx here.
Should I load it using /etc/modprobe.d
so that I can specify more advanced options?