From: Daniel Walker <danielwa@cisco.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: HEMANT RAMDASI <hramdasi@cisco.com>,
Christian Engelmayer <christian.engelmayer@frequentis.com>,
Gopalakrishnan Santhanam <gsanthan@cisco.com>,
xe-linux-external@cisco.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] fsl-usb: add need_oc_pp_cycle flag for 85xx also
Date: Fri, 7 May 2021 10:23:00 -0700 [thread overview]
Message-ID: <20210507172300.3075939-1-danielwa@cisco.com> (raw)
From: Gopalakrishnan Santhanam <gsanthan@cisco.com>
Commit e6604a7fd71f9 ("EHCI: Quirk flag for port power handling on overcurrent.")
activated the quirks handling (flag need_oc_pp_cycle) for Freescale 83xx
based boards.
Activate same for 85xx based boards as well.
Cc: xe-linux-external@cisco.com
Signed-off-by: Gopalakrishnan Santhanam <gsanthan@cisco.com>
Signed-off-by: Daniel Walker <danielwa@cisco.com>
---
drivers/usb/host/ehci-fsl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/ehci-fsl.c b/drivers/usb/host/ehci-fsl.c
index 6f7bd6641694..c7d74c1a23f5 100644
--- a/drivers/usb/host/ehci-fsl.c
+++ b/drivers/usb/host/ehci-fsl.c
@@ -387,7 +387,7 @@ static int ehci_fsl_setup(struct usb_hcd *hcd)
/* EHCI registers start at offset 0x100 */
ehci->caps = hcd->regs + 0x100;
-#ifdef CONFIG_PPC_83xx
+#if defined(CONFIG_PPC_83xx) || defined(CONFIG_PPC_85xx)
/*
* Deal with MPC834X that need port power to be cycled after the power
* fault condition is removed. Otherwise the state machine does not
--
2.25.1
next reply other threads:[~2021-05-07 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 17:23 Daniel Walker [this message]
2021-05-07 17:36 ` [PATCH] fsl-usb: add need_oc_pp_cycle flag for 85xx also Alan Stern
2021-05-11 13:19 ` Gopalakrishnan Santhanam -X (gsanthan - Altran ACT S.A.S at Cisco)
2021-05-13 8:32 ` [PATCH v2] " Gopalakrishnan Santhanam
2021-05-13 14:42 ` Alan Stern
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=20210507172300.3075939-1-danielwa@cisco.com \
--to=danielwa@cisco.com \
--cc=christian.engelmayer@frequentis.com \
--cc=gregkh@linuxfoundation.org \
--cc=gsanthan@cisco.com \
--cc=hramdasi@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=xe-linux-external@cisco.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;
as well as URLs for NNTP newsgroup(s).