From: "Chen, Hu" <hu1.chen@intel.com>
To: hdegoede@redhat.com
Cc: hu1.chen@intel.com, Balaji <m.balaji@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] usb: roles: Add PM callbacks
Date: Mon, 8 Jul 2019 10:25:14 +0800 [thread overview]
Message-ID: <20190708022514.7161-1-hu1.chen@intel.com> (raw)
On some Broxton NUC, the usb role is lost after S3 (it becomes "none").
Add PM callbacks to address this issue: save the role during suspend and
restore usb to that role during resume.
Test:
Run Android on UC6CAY, a NUC powered by Broxton. Access this NUC via
"adb shell" from a host PC. After a suspend/resume cycle, the adb still
works well.
Signed-off-by: Chen, Hu <hu1.chen@intel.com>
Signed-off-by: Balaji <m.balaji@intel.com>
diff --git a/drivers/usb/roles/intel-xhci-usb-role-switch.c b/drivers/usb/roles/intel-xhci-usb-role-switch.c
index 277de96181f9..caa1cfab41cc 100644
--- a/drivers/usb/roles/intel-xhci-usb-role-switch.c
+++ b/drivers/usb/roles/intel-xhci-usb-role-switch.c
@@ -37,6 +37,7 @@
struct intel_xhci_usb_data {
struct usb_role_switch *role_sw;
void __iomem *base;
+ enum usb_role role;
};
static int intel_xhci_usb_set_role(struct device *dev, enum usb_role role)
@@ -167,6 +168,30 @@ static int intel_xhci_usb_remove(struct platform_device *pdev)
return 0;
}
+static int intel_xhci_usb_suspend(struct platform_device *pdev,
+ pm_message_t state)
+{
+ struct intel_xhci_usb_data *data = platform_get_drvdata(pdev);
+ struct device *dev = &pdev->dev;
+
+ data->role = intel_xhci_usb_get_role(dev);
+
+ return 0;
+}
+
+static int intel_xhci_usb_resume(struct platform_device *pdev)
+{
+ struct intel_xhci_usb_data *data = platform_get_drvdata(pdev);
+ struct device *dev = &pdev->dev;
+
+ if (intel_xhci_usb_get_role(dev) != data->role) {
+ if (intel_xhci_usb_set_role(dev, data->role) != 0)
+ dev_warn(dev, "Failed to set role during resume\n");
+ }
+
+ return 0;
+}
+
static const struct platform_device_id intel_xhci_usb_table[] = {
{ .name = DRV_NAME },
{}
@@ -180,6 +205,8 @@ static struct platform_driver intel_xhci_usb_driver = {
.id_table = intel_xhci_usb_table,
.probe = intel_xhci_usb_probe,
.remove = intel_xhci_usb_remove,
+ .suspend = intel_xhci_usb_suspend,
+ .resume = intel_xhci_usb_resume,
};
module_platform_driver(intel_xhci_usb_driver);
--
2.22.0
next reply other threads:[~2019-07-08 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 2:25 Chen, Hu [this message]
2019-07-08 8:30 ` Sergei Shtylyov
2019-07-08 14:10 ` Hans de Goede
2019-07-09 10:30 ` [PATCH v2] " Chen, Hu
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=20190708022514.7161-1-hu1.chen@intel.com \
--to=hu1.chen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.balaji@intel.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®