[PATCH] bus: mhi: host: Change the log levels for SYS_ERR event
Baochen Qiang
quic_bqiang at quicinc.com
Tue Jan 3 18:57:20 PST 2023
On 1/4/2023 10:41 AM, Jeffrey Hugo wrote:
> Why was this not sent to the MHI mailing list?
I don't know the MHI mailing list address, could tell me that?
>
> On Tue, Jan 3, 2023 at 7:19 PM Baochen Qiang <quic_bqiang at quicinc.com> wrote:
>> Currently no log printed when SYS_ERR happens, this makes
>> debug quite hard, so change log level to make it noisy.
> You are going to need to explain this more.
> There are two drivers in the upstream kernel that are MHI clients -
> pci_generic and ath11k.
> I'm assuming that you care about ath11k because you included that mail list.
Yes, I am talking about ath11k.
> In ath11k_mhi_op_status_cb() I see a warning message printed when the
> syserr callback is triggered.
> I see something similar in pci_generic.
>
> Looks like a log is printed when SYS_ERR happens in all possible
> scenarios, so I don't understand the point of this change.
> Particularly given that dev_dbg messages can be trivially enabled.
>
> -Jeff
Well, this is not true in some cases. For example, we have met cases where
WLAN HW/firmware is not working well, and only send a SYS_ERR event to MHI
driver, however this event is not sent to ath11k host becuase of
mhi_pm_sys_err_handler(),
so we got no log at all.
More information about the ath11k
mailing list