From: Greg KH <gregkh@linuxfoundation.org>
To: jose.alberto.reguero@gmail.com
Cc: linux-usb@vger.kernel.org, Mathias Nyman <mathias.nyman@intel.com>
Subject: Re: PATCH: Fix problem with xhci resume from suspend
Date: Wed, 18 Sep 2024 07:39:06 +0200 [thread overview]
Message-ID: <2024091824-village-surgery-c283@gregkh> (raw)
In-Reply-To: <018846f9a846e70d22f31203e4e8e93a1ee58de1.camel@gmail.com>
On Wed, Sep 18, 2024 at 12:10:24AM +0200, jose.alberto.reguero@gmail.com wrote:
> El mar, 17-09-2024 a las 22:45 +0200, Greg KH escribió:
> > On Tue, Sep 17, 2024 at 08:47:43PM +0200, Jose Alberto Reguero wrote:
> > > I have a ASUS PN51 S mini pc that has two xhci devices. One from
> > > AMD,
> > > and other from ASMEDIA. The one from ASMEDIA have problems when
> > > resume
> > > from suspend, and keep broken until unplug the power cord. I use
> > > this
> > > kernel parameter: xhci-hcd.quirks=128 and then it works ok. I make
> > > a
> > > path to reset only the ASMEDIA xhci.
> > >
> > >
> > > Signed-off-by: Jose Alberto Reguero
> > > <jose.alberto.reguero@gmail.com>
> > >
> > > diff -ur linux-6.10.8/drivers/usb/host/xhci-pci.c
> > > linux-6.10.8.new/drivers/usb/host/xhci-pci.c
> > > --- linux-6.10.8/drivers/usb/host/xhci-pci.c 2024-09-04
> > > 13:30:16.000000000 +0200
> > > +++ linux-6.10.8.new/drivers/usb/host/xhci-pci.c 2024-09-12
> > > 19:37:14.378870385 +0200
> > > @@ -76,6 +76,7 @@
> > > #define PCI_DEVICE_ID_ASMEDIA_1042A_XHCI 0x1142
> > > #define PCI_DEVICE_ID_ASMEDIA_1142_XHCI 0x1242
> > > #define PCI_DEVICE_ID_ASMEDIA_2142_XHCI 0x2142
> > > +#define PCI_DEVICE_ID_ASMEDIA_3042_XHCI 0x3042
> > > #define PCI_DEVICE_ID_ASMEDIA_3242_XHCI 0x3242
> > >
> > > static const char hcd_name[] = "xhci_hcd";
> > > @@ -447,6 +448,10 @@
> > > pdev->device == PCI_DEVICE_ID_ASMEDIA_1042A_XHCI)
> > > xhci->quirks |= XHCI_ASMEDIA_MODIFY_FLOWCONTROL;
> > >
> > > + if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
> > > + pdev->device == PCI_DEVICE_ID_ASMEDIA_3042_XHCI)
> > > + xhci->quirks |= XHCI_RESET_ON_RESUME;
> >
> > Something went wrong with the whitespace here, can you try sending it
> > again? You can't use cut/paste from a web client for patches, the
> > email
> > documentation should explain how to do this properly from gmail if
> > you
> > have problems.
> >
> > thanks,
> >
> > greg k-h
>
> Sorry, submit it again. Hope this time is alright.
>
> Jose Alberto Reguero
>
> diff -ur linux-6.10.8/drivers/usb/host/xhci-pci.c linux-
> 6.10.8.new/drivers/usb/host/xhci-pci.c
> --- linux-6.10.8/drivers/usb/host/xhci-pci.c 2024-09-04
> 13:30:16.000000000 +0200
> +++ linux-6.10.8.new/drivers/usb/host/xhci-pci.c 2024-09-12
> 19:37:14.378870385 +0200
> @@ -76,6 +76,7 @@
> #define PCI_DEVICE_ID_ASMEDIA_1042A_XHCI 0x1142
> #define PCI_DEVICE_ID_ASMEDIA_1142_XHCI 0x1242
> #define PCI_DEVICE_ID_ASMEDIA_2142_XHCI 0x2142
> +#define PCI_DEVICE_ID_ASMEDIA_3042_XHCI 0x3042
> #define PCI_DEVICE_ID_ASMEDIA_3242_XHCI 0x3242
>
> static const char hcd_name[] = "xhci_hcd";
> @@ -447,6 +448,10 @@
> pdev->device == PCI_DEVICE_ID_ASMEDIA_1042A_XHCI)
> xhci->quirks |= XHCI_ASMEDIA_MODIFY_FLOWCONTROL;
>
> + if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
> + pdev->device == PCI_DEVICE_ID_ASMEDIA_3042_XHCI)
> + xhci->quirks |= XHCI_RESET_ON_RESUME;
> +
> if (pdev->vendor == PCI_VENDOR_ID_TI && pdev->device ==
> 0x8241)
It is line-wrapped :(
Try sending it to yourself first, and then see if you can apply it to
the tree from that email.
Or use 'git send-email' that will do it all properly for you, we
recommend that.
thanks,
greg k-h
prev parent reply other threads:[~2024-09-18 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 18:47 PATCH: Fix problem with xhci resume from suspend Jose Alberto Reguero
2024-09-17 20:45 ` Greg KH
2024-09-17 21:35 ` Jose Alberto Reguero
2024-09-18 5:39 ` Greg KH
2024-09-17 22:10 ` jose.alberto.reguero
2024-09-18 5:39 ` Greg KH [this message]
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=2024091824-village-surgery-c283@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jose.alberto.reguero@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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