From: Greg KH <gregkh@linuxfoundation.org>
To: Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: stern@rowland.harvard.edu, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, ludovic.desroches@microchip.com,
cristian.birsan@microchip.com, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: host: ohci-at91: suspend/resume ports after/before OHCI accesses
Date: Wed, 21 Jul 2021 10:08:18 +0200 [thread overview]
Message-ID: <YPfV8gCx1SVTedxd@kroah.com> (raw)
In-Reply-To: <20210609121027.70951-1-claudiu.beznea@microchip.com>
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().
>
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
>
> The patch was tested on SAMA7G5, SAMA5D2 and SAM9X60.
This does not apply to 5.14-rc2, can you please rebase and resend?
thanks,
greg k-h
prev parent reply other threads:[~2021-07-21 8:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 12:10 [PATCH] usb: host: ohci-at91: suspend/resume ports after/before OHCI accesses Claudiu Beznea
2021-06-09 12:40 ` Nicolas Ferre
2021-06-09 23:07 ` Alan Stern
2021-06-23 12:47 ` Claudiu.Beznea
2021-06-23 13:59 ` Alan Stern
2021-06-23 14:09 ` Claudiu.Beznea
2021-06-23 14:19 ` Alan Stern
2021-06-23 14:33 ` Claudiu.Beznea
2021-06-23 16:41 ` Alan Stern
2021-06-24 6:40 ` Claudiu.Beznea
2021-06-24 6:54 ` Claudiu.Beznea
2021-06-24 13:23 ` Alan Stern
2021-06-30 14:46 ` Claudiu.Beznea
2021-06-30 18:21 ` Alan Stern
2021-07-01 5:45 ` Claudiu.Beznea
2021-07-01 14:01 ` Alan Stern
2021-06-30 14:47 ` Claudiu.Beznea
2021-07-21 8:08 ` 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=YPfV8gCx1SVTedxd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=cristian.birsan@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).