From: liulongfang <liulongfang@huawei.com>
To: Oliver Neukum <oneukum@suse.com>, <gregkh@linuxfoundation.org>,
<mathias.nyman@intel.com>, <stern@rowland.harvard.edu>,
<liudongdong3@huawei.com>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kong.kongxinwei@hisilicon.com>, <yisen.zhuang@huawei.com>
Subject: Re: [PATCH 1/2] USB:ehci:Add a whitelist for EHCI controllers
Date: Thu, 8 Apr 2021 17:44:39 +0800 [thread overview]
Message-ID: <0d5963d0-9e25-5411-67df-146bf924fc17@huawei.com> (raw)
In-Reply-To: <a14fcaffd6e26081c07bcfa36a81ded38dcf88b2.camel@suse.com>
On 2021/4/8 17:33, Oliver Neukum wrote:
> Am Donnerstag, den 08.04.2021, 17:11 +0800 schrieb Longfang Liu:
>> Some types of EHCI controllers do not have SBRN registers.
>> By comparing the white list, the operation of reading the SBRN
>> registers is skipped.
>>
>> Subsequent EHCI controller types without SBRN registers can be
>> directly added to the white list.
>
> Hi,
>
> shouldn't this set a flag for a missing functionality?
>
> Regards
> Oliver
>
>
> .
>
This flag is ehci->sbrn.
Thanks,
Longfang
next prev parent reply other threads:[~2021-04-08 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 9:11 [PATCH 0/2] USB:ehci:fix the no SRBN register problem Longfang Liu
2021-04-08 9:11 ` [PATCH 1/2] USB:ehci:Add a whitelist for EHCI controllers Longfang Liu
2021-04-08 9:22 ` Greg KH
2021-04-08 13:04 ` liulongfang
2021-04-08 14:53 ` Greg KH
2021-04-08 9:33 ` Oliver Neukum
2021-04-08 9:44 ` liulongfang [this message]
2021-04-08 9:11 ` [PATCH 2/2] USB:ehci:fix Kunpeng920 ehci hardware problem Longfang Liu
-- strict thread matches above, loose matches on Subject: below --
2021-04-08 9:09 [PATCH 0/2] USB:ehci:fix the no SRBN register problem Longfang Liu
2021-04-08 9:09 ` [PATCH 1/2] USB:ehci:Add a whitelist for EHCI controllers Longfang Liu
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=0d5963d0-9e25-5411-67df-146bf924fc17@huawei.com \
--to=liulongfang@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=kong.kongxinwei@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=mathias.nyman@intel.com \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).