From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: liulongfang <liulongfang@huawei.com>,
gregkh@linuxfoundation.org, mathias.nyman@intel.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
yisen.zhuang@huawei.com
Subject: Re: [PATCH] xhci: print warning when HCE was set
Date: Mon, 26 Sep 2022 10:58:18 +0300 [thread overview]
Message-ID: <8271d551-4034-71fe-5be4-e08e28b6dd6b@linux.intel.com> (raw)
In-Reply-To: <2648444c-2f2a-4d9b-8545-6677663adcf0@huawei.com>
On 24.9.2022 5.35, liulongfang wrote:
> On 2022/9/22 21:01, Mathias Nyman Wrote:
>> Hi
>>
>> On 15.9.2022 4.11, Longfang Liu wrote:
>>> When HCE(Host Controller Error) is set, it means that the xhci hardware
>>> controller has an error at this time, but the current xhci driver
>>> software does not log this event.
>>>
>>> By adding an HCE event detection in the xhci interrupt processing
>>> interface, a warning log is output to the system, which is convenient
>>> for system device status tracking.
>>>
>>
>> xHC should cease all activity when it sets HCE, and is probably not
>> generating interrupts anymore.
>>
>> Would probably be more useful to check for HCE at timeouts than in the
>> interrupt handler.
>>
>
> Which function of the driver code is this timeout in?
xhci_handle_command_timeout() will usually trigger at some point,
>
>> If this is something seen on actual hardware then it makes sense to add it.
>>
>
> This HCE error is sure to report an interrupt on the chip we are using.
Ok, then makes sense to add this patch.
Thanks
-Mathias
next prev parent reply other threads:[~2022-09-26 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 1:11 [PATCH] xhci: print warning when HCE was set Longfang Liu
2022-09-22 13:01 ` Mathias Nyman
2022-09-24 2:35 ` liulongfang
2022-09-26 7:58 ` Mathias Nyman [this message]
2022-10-14 3:12 ` liulongfang
2022-10-14 7:56 ` Mathias Nyman
2022-12-09 6:13 ` liulongfang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8271d551-4034-71fe-5be4-e08e28b6dd6b@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=mathias.nyman@intel.com \
--cc=yisen.zhuang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.