[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAd53p5pxGfS0y260NsMF+m_Ota+d1ZKbtdq4dfM5s+T1z14bw@mail.gmail.com>
Date: Fri, 18 Aug 2023 08:01:54 +0800
From: Kai-Heng Feng <kai.heng.feng@...onical.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: mathias.nyman@...el.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] xhci: Disable connect, disconnect and over-current wakeup
on system suspend
On Thu, Aug 17, 2023 at 10:22 PM Alan Stern <stern@...land.harvard.edu> wrote:
>
> On Thu, Aug 17, 2023 at 10:07:37AM -0400, Alan Stern wrote:
> > On Thu, Aug 17, 2023 at 05:33:05PM +0800, Kai-Heng Feng wrote:
> > > HP ProOne 440 G10 AIO sometimes cannot suspend as xHCI wakes up the
> > > system:
> > > [ 445.814574] hub 2-0:1.0: hub_suspend
> > > [ 445.814652] usb usb2: bus suspend, wakeup 0
> > > [ 445.824629] xhci_hcd 0000:00:14.0: Port change event, 1-11, id 11, portsc: 0x202a0
> >
> > What is the meaning of the 0x202a0 bits? What caused this wakeup?
>
> And more to the point, given that the previous line says "wakeup 0", why
> should any port change event cause a wakeup?
I think the controller and roothub have to deal with the interrupt
about disconnecting regardless of the remote wakeup setting.
Kai-Heng
>
> Alan Stern
Powered by blists - more mailing lists