linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Longfang Liu <liulongfang@huawei.com>
Cc: mathias.nyman@intel.com, stern@rowland.harvard.edu,
	liudongdong3@huawei.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, kong.kongxinwei@hisilicon.com,
	yisen.zhuang@huawei.com
Subject: Re: [PATCH v3 1/2] USB:ehci:Add a whitelist for EHCI controllers
Date: Fri, 9 Apr 2021 08:46:49 +0200	[thread overview]
Message-ID: <YG/4WTTAg2cjjRDi@kroah.com> (raw)
In-Reply-To: <1617937215-39035-2-git-send-email-liulongfang@huawei.com>

On Fri, Apr 09, 2021 at 11:00:14AM +0800, Longfang Liu wrote:
> 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.

Your subject line still contains "whitelist" when the code does not.
Please fix it up to reflect your recent changes.

> 
> The current patch does not affect the drive function.
> 
> Signed-off-by: Longfang Liu <liulongfang@huawei.com>
> ---
>  drivers/usb/host/ehci-pci.c | 27 +++++++++++++++++++++++----
>  1 file changed, 23 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/usb/host/ehci-pci.c b/drivers/usb/host/ehci-pci.c
> index 3c3820a..f7f3156 100644
> --- a/drivers/usb/host/ehci-pci.c
> +++ b/drivers/usb/host/ehci-pci.c
> @@ -47,6 +47,28 @@ static inline bool is_bypassed_id(struct pci_dev *pdev)
>  	return !!pci_match_id(bypass_pci_id_table, pdev);
>  }
>  
> +static const struct ehci_nosbrn {
> +	u16 vendor;
> +	u16 device;
> +} ehci_nosbrn_table[] = {
> +	/* STMICRO ConneXT has no sbrn register */
> +	{PCI_VENDOR_ID_STMICRO, PCI_DEVICE_ID_STMICRO_USB_HOST},
> +	{},
> +};
> +
> +static bool usb_forbid_sbrn_read(struct pci_dev *pdev)
> +{
> +	const struct ehci_nosbrn *entry;
> +
> +	for (entry = ehci_nosbrn_table; entry->vendor; entry++) {
> +		if (pdev->vendor == entry->vendor &&
> +		    pdev->device == entry->device)
> +			return true;

There is a PCI-match-device function somewhere, right?

But as Alan said, why is all of this needed?  You only have 2 devices
you are testing for, we have if statements that are MUCH bigger than
that for simple things like this.

And the odds that a new device will be added to this list in the future
is _VERY_ low given that I would think that no one is making new EHCI
controllers anymore.

So just make this one patch, and add your device id to that, like you
did in the first set of patches.

thanks,

greg k-h

  reply	other threads:[~2021-04-09  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  3:00 [PATCH v3 0/2] USB:ehci:fix the no SRBN register problem Longfang Liu
2021-04-09  3:00 ` [PATCH v3 1/2] USB:ehci:Add a whitelist for EHCI controllers Longfang Liu
2021-04-09  6:46   ` Greg KH [this message]
2021-04-09  3:00 ` [PATCH v3 2/2] USB:ehci:fix Kunpeng920 ehci hardware problem 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=YG/4WTTAg2cjjRDi@kroah.com \
    --to=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=liulongfang@huawei.com \
    --cc=mathias.nyman@intel.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).