On RB4, for ADSP, only three FastRPC context banks (CBs) are available.
Each CB supports a single session, which means a maximum of three processes can run on ADSP simultaneously.
If all three sessions are consumed by fastrpc daemons, no session remains available when a user application starts, causing the application to fail.
To address this issue, a Device Tree change was used till now:
qcom,nsessions = <5>;
However, feedback from the upstream community indicated that this change should not be made in the Device Tree. Instead, it was recommended to handle this as a driver-level change.
Reference: https://lore.kernel.org/all/ejt3dzkuo76sb6jipkuae2u47kushc3vporxn3xclts445pgck@5qfcnufjljiw/
I am currently working on implementing this change in the driver.
On RB4, for ADSP, only three FastRPC context banks (CBs) are available.
Each CB supports a single session, which means a maximum of three processes can run on ADSP simultaneously.
If all three sessions are consumed by fastrpc daemons, no session remains available when a user application starts, causing the application to fail.
To address this issue, a Device Tree change was used till now:
qcom,nsessions = <5>;However, feedback from the upstream community indicated that this change should not be made in the Device Tree. Instead, it was recommended to handle this as a driver-level change.
Reference: https://lore.kernel.org/all/ejt3dzkuo76sb6jipkuae2u47kushc3vporxn3xclts445pgck@5qfcnufjljiw/
I am currently working on implementing this change in the driver.