On Mon, Aug 19, 2024 at 09:53:09AM -0700, Bjorn Andersson wrote: > On Mon, Aug 19, 2024 at 05:48:26PM +0200, Johan Hovold wrote: > > I can confirm that I still see the -ECANCELED issue with this series > > applied: > > > > [ 8.979329] pmic_glink_altmode.pmic_glink_altmode pmic_glink.altmode.0: failed to send altmode request: 0x10 (-125) > > [ 9.004735] pmic_glink_altmode.pmic_glink_altmode pmic_glink.altmode.0: failed to request altmode notifications: -125 > > Could you confirm that you're seeing a call to > qcom_glink_handle_intent_req_ack() with granted == 0, leading to the > transfer failing. It appears so: [ 9.539415] 30000000.remoteproc:glink-edge: qcom_glink_handle_intent_req_ack - cid = 9, granted = 0 [ 9.561750] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: failed to request power notifications [ 9.448945] 30000000.remoteproc:glink-edge: qcom_glink_handle_intent_req_ack - cid = 9, granted = 0 [ 9.461267] pmic_glink_altmode.pmic_glink_altmode pmic_glink.altmode.0: failed to send altmode request: 0x10 (-125) [ 9.469241] qcom,apr 30000000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1 [ 9.478968] pmic_glink_altmode.pmic_glink_altmode pmic_glink.altmode.0: failed to request altmode notifications: -125 > It would also be nice, just for completeness sake to rule out that you > do not get a call to qcom_glink_intent_req_abort() here. And I'm not seeing this function being called. Johan
