From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Baoqi Zhang <zhangbaoqi@loongson.cn>
Subject: Re: [PATCH] USB: pci-quirks: Fix HCCPARAMS register error for LS7A EHCI
Date: Fri, 31 Jan 2025 11:48:27 +0100 [thread overview]
Message-ID: <2025013107-droplet-reset-127e@gregkh> (raw)
In-Reply-To: <20250131100651.343015-1-chenhuacai@loongson.cn>
On Fri, Jan 31, 2025 at 06:06:51PM +0800, Huacai Chen wrote:
> LS7A EHCI controller doesn't have extended capabilities, so the EECP
> (EHCI Extended Capabilities Pointer) field of HCCPARAMS register should
> be 0x0, but it reads as 0xa0 now. This is a hardware flaw and will be
> fixed in future, now just clear the EECP field to avoid error messages
> on boot:
>
> ......
> [ 0.581675] pci 0000:00:04.1: EHCI: unrecognized capability ff
> [ 0.581699] pci 0000:00:04.1: EHCI: unrecognized capability ff
> [ 0.581716] pci 0000:00:04.1: EHCI: unrecognized capability ff
> [ 0.581851] pci 0000:00:04.1: EHCI: unrecognized capability ff
> ......
> [ 0.581916] pci 0000:00:05.1: EHCI: unrecognized capability ff
> [ 0.581951] pci 0000:00:05.1: EHCI: unrecognized capability ff
> [ 0.582704] pci 0000:00:05.1: EHCI: unrecognized capability ff
> [ 0.582799] pci 0000:00:05.1: EHCI: unrecognized capability ff
> ......
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Baoqi Zhang <zhangbaoqi@loongson.cn>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
> ---
> drivers/usb/host/pci-quirks.c | 4 ++++
> include/linux/pci_ids.h | 1 +
> 2 files changed, 5 insertions(+)
>
> diff --git a/drivers/usb/host/pci-quirks.c b/drivers/usb/host/pci-quirks.c
> index 1f9c1b1435d8..7e3151400a5e 100644
> --- a/drivers/usb/host/pci-quirks.c
> +++ b/drivers/usb/host/pci-quirks.c
> @@ -958,6 +958,10 @@ static void quirk_usb_disable_ehci(struct pci_dev *pdev)
> * booting from USB disk or using a usb keyboard
> */
> hcc_params = readl(base + EHCI_HCC_PARAMS);
> + if (pdev->vendor == PCI_VENDOR_ID_LOONGSON &&
> + pdev->device == PCI_DEVICE_ID_LOONGSON_EHCI)
> + hcc_params &= ~(0xffL << 8);
> +
> offset = (hcc_params >> 8) & 0xff;
> while (offset && --count) {
> pci_read_config_dword(pdev, offset, &cap);
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index de5deb1a0118..74a84834d9eb 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -162,6 +162,7 @@
>
> #define PCI_VENDOR_ID_LOONGSON 0x0014
>
> +#define PCI_DEVICE_ID_LOONGSON_EHCI 0x7a14
If you read the top of this file, does this patch meet the requirement
to add this entry here to this file?
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-31 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 10:06 [PATCH] USB: pci-quirks: Fix HCCPARAMS register error for LS7A EHCI Huacai Chen
2025-01-31 10:48 ` Greg Kroah-Hartman [this message]
2025-01-31 14:28 ` Huacai Chen
2025-01-31 15:18 ` Alan Stern
2025-02-01 6:18 ` Huacai Chen
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=2025013107-droplet-reset-127e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=zhangbaoqi@loongson.cn \
/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