From: Haotien Hsu <haotienh@nvidia.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: WK Tsai <wtsai@nvidia.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Wayne Chang <waynec@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mathias.nyman@intel.com" <mathias.nyman@intel.com>,
Jui Chang Kuo <jckuo@nvidia.com>, Henry Lin <henryl@nvidia.com>
Subject: Re: [PATCH v2] usb: xhci: tegra: Add shutdown callback for Tegra XUSB
Date: Thu, 27 Jul 2023 08:08:15 +0000 [thread overview]
Message-ID: <1f9a2e6de117df62c77eca0560785c49a8245ba8.camel@nvidia.com> (raw)
In-Reply-To: <2023072532-vacancy-headlock-46be@gregkh>
On Tue, 2023-07-25 at 18:19 +0200, Greg Kroah-Hartman wrote:
> External email: Use caution opening links or attachments
>
>
> On Tue, Jul 18, 2023 at 05:14:25PM +0800, Haotien Hsu wrote:
> > From: Henry Lin <henryl@nvidia.com>
> >
> > If memory accesses by the Tegra XUSB controller are translated
> > through
> > the SMMU (System MMU), the hardware may continue accessing memory
> > even
> > after the SMMU translations have been disabled during the shutdown
> > process and this can in turn cause unpredictable crashes.
> > Fix this by adding a shutdown implementation that ensures the
> > hardware
> > is turned off during system reboot or shutdown.
> >
> > Signed-off-by: Henry Lin <henryl@nvidia.com>
> > Signed-off-by: Haotien Hsu <haotienh@nvidia.com>
> > Acked-by: Thierry Reding <treding@nvidia.com>
> >
> > ---
> > V1 -> V2: Resend for the typo in the mailing list
> > ---
> > drivers/usb/host/xhci-tegra.c | 28 +++++++++++++++++++++-------
> > 1 file changed, 21 insertions(+), 7 deletions(-)
>
> Does not apply against 6.5-rc4 at all :(
I rebased the patch and sent it again.
I am sorry about that.
prev parent reply other threads:[~2023-07-27 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 9:14 Haotien Hsu
2023-07-18 9:18 ` Oliver Neukum
2023-07-18 11:35 ` Thierry Reding
2023-07-25 16:19 ` Greg Kroah-Hartman
2023-07-27 8:08 ` Haotien Hsu [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=1f9a2e6de117df62c77eca0560785c49a8245ba8.camel@nvidia.com \
--to=haotienh@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=henryl@nvidia.com \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=thierry.reding@gmail.com \
--cc=waynec@nvidia.com \
--cc=wtsai@nvidia.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
all inboxes | Powered by JetHome®