From: Greg KH <gregkh@linuxfoundation.org>
To: Weitao Wang <WeitaoWang-oc@zhaoxin.com>
Cc: stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, tonywwang@zhaoxin.com,
weitaowang@zhaoxin.com
Subject: Re: [PATCH] UHCI:adjust zhaoxin UHCI controllers OverCurrent bit value
Date: Thu, 20 Apr 2023 10:05:44 +0200 [thread overview]
Message-ID: <ZEDyWC7GsbcEn7UK@kroah.com> (raw)
In-Reply-To: <20230420111445.5028-1-WeitaoWang-oc@zhaoxin.com>
On Thu, Apr 20, 2023 at 07:14:45PM +0800, Weitao Wang wrote:
> Over Current condition is not standardized in the UHCI spec.
> Zhaoxin UHCI controllers report OverCurrent bit active off.
> Intel controllers report it active on, so we'll adjust the bit value.
>
> Signed-off-by: Weitao Wang <WeitaoWang-oc@zhaoxin.com>
Note, your Subject: line has odd characters in it, can you rewrite it to
just use ascii? I think it's the ':' character which should be ':',
right?
> ---
> drivers/usb/host/uhci-pci.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/usb/host/uhci-pci.c b/drivers/usb/host/uhci-pci.c
> index 3592f757fe05..177e3c2aa287 100644
> --- a/drivers/usb/host/uhci-pci.c
> +++ b/drivers/usb/host/uhci-pci.c
> @@ -126,6 +126,10 @@ static int uhci_pci_init(struct usb_hcd *hcd)
> if (to_pci_dev(uhci_dev(uhci))->vendor == PCI_VENDOR_ID_VIA)
> uhci->oc_low = 1;
>
> + /* ZHAOXIN controllers report OverCurrent bit active off. */
> + if (to_pci_dev(uhci_dev(uhci))->vendor == PCI_VENDOR_ID_ZHAOXIN)
> + uhci->oc_low = 1;
> +
This should also go to the stable kernels, right?
But a new UHCI controller? And this affects all of them? And why is
Intel an issue here (as you mention in the changelog text)?
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-20 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 11:14 [PATCH] UHCI:adjust zhaoxin UHCI controllers OverCurrent bit value Weitao Wang
2023-04-20 8:05 ` Greg KH [this message]
2023-04-20 17:14 ` WeitaoWang-oc
2023-04-20 9:23 ` Greg KH
2023-04-20 14:49 ` Alan Stern
2023-04-21 10:59 ` WeitaoWang-oc
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=ZEDyWC7GsbcEn7UK@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=WeitaoWang-oc@zhaoxin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tonywwang@zhaoxin.com \
--cc=weitaowang@zhaoxin.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.