[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210609230735.GA1861855@rowland.harvard.edu>
Date: Wed, 9 Jun 2021 19:07:35 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Claudiu Beznea <claudiu.beznea@...rochip.com>
Cc: gregkh@...uxfoundation.org, nicolas.ferre@...rochip.com,
alexandre.belloni@...tlin.com, ludovic.desroches@...rochip.com,
cristian.birsan@...rochip.com, linux-usb@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: host: ohci-at91: suspend/resume ports after/before
OHCI accesses
On Wed, Jun 09, 2021 at 03:10:27PM +0300, Claudiu Beznea wrote:
> On SAMA7G5 suspending ports will cut the access to OHCI registers and
> any subsequent access to them will lead to CPU being blocked trying to
> access that memory. Same thing happens on resume: if OHCI memory is
> accessed before resuming ports the CPU will block on that access. The
> OCHI memory is accessed on suspend/resume though
> ohci_suspend()/ohci_resume().
That sounds very strange. Suppose one of the ports is suspended, so access to the
OHCI registers is blocked. Then how can you resume the port? Don't you have to
access the OHCI registers in order to tell the controller to do the port resume?
What happens when there's more than one port, and one of them is suspended while
the other one is still running? How can you communicate with the active port if
access to the OHCI registers is blocked?
Alan Stern
Powered by blists - more mailing lists