| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20210915140524.GB6787@codeaurora.org>
Date: Wed, 15 Sep 2021 19:35:24 +0530
From: Pavan Kondeti <pkondeti@...eaurora.org>
To: Felipe Balbi <balbi@...nel.org>
Cc: Matthias Kaehlcke <mka@...omium.org>,
Sandeep Maheswaram <sanm@...eaurora.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Stephen Boyd <swboyd@...omium.org>,
Doug Anderson <dianders@...omium.org>,
Mathias Nyman <mathias.nyman@...el.com>,
linux-arm-msm@...r.kernel.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org,
Pratham Pratap <prathampratap@...eaurora.org>,
linux-pm@...r.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: [PATCH v8 6/6] usb: dwc3: qcom: Keep power domain on to support
wakeup
+linux-pm and Rafael
Hi Balbi,
On Mon, Jul 12, 2021 at 12:42:17PM +0300, Felipe Balbi wrote:
>
> >> @@ -355,9 +356,15 @@ static int dwc3_qcom_suspend(struct dwc3_qcom *qcom)
> >> u32 val;
> >> int i, ret;
> >>
> >> + struct dwc3 *dwc = platform_get_drvdata(qcom->dwc3);
> >> + struct generic_pm_domain *genpd = pd_to_genpd(qcom->dev->pm_domain);
> >> +
> >> if (qcom->is_suspended)
> >> return 0;
> >>
> >> + if (!dwc->phy_power_off && dwc->xhci)
> >> + genpd->flags |= GENPD_FLAG_ACTIVE_WAKEUP;
> >> +
> >> val = readl(qcom->qscratch_base + PWR_EVNT_IRQ_STAT_REG);
> >> if (!(val & PWR_EVNT_LPM_IN_L2_MASK))
> >> dev_err(qcom->dev, "HS-PHY not in L2\n");
> >> @@ -382,9 +389,15 @@ static int dwc3_qcom_resume(struct dwc3_qcom *qcom)
> >> int ret;
> >> int i;
> >>
> >> + struct dwc3 *dwc = platform_get_drvdata(qcom->dwc3);
> >> + struct generic_pm_domain *genpd = pd_to_genpd(qcom->dev->pm_domain);
> >> +
> >> if (!qcom->is_suspended)
> >> return 0;
> >>
> >> + if (dwc->xhci)
> >> + genpd->flags &= ~GENPD_FLAG_ACTIVE_WAKEUP;
> >> +
> >> if (device_may_wakeup(qcom->dev))
> >> dwc3_qcom_disable_interrupts(qcom);
> >>
> >
> > This is essentially the same as v7, which Felipe NAKed
> > (https://patchwork.kernel.org/project/linux-arm-msm/patch/1619586716-8687-6-git-send-email-sanm@codeaurora.org/)
> >
> > I think Felipe wants to see the handling of the power domain in the
> > xhci-plat driver. One problem here is that the power domain is owned
>
> this is not exactly what I meant to say, though. I want drivers to be
> self-contained. I.e. dwc3 doesn't modify xhci data and vice-versa. There
> are a few assummpmtions that we can make, though. The structure is
> usually like this:
>
> glue {
> dwc3 {
> xhci
> };
> };
>
> This means that in order for glue_suspend() to run, dwc3 has to suspend
> first and xhci has to suspend before dwc3.
>
> For example, in the suspend call above, qcom (the glue) is directly
> accessing dwc3 core data, which is incorrect. It looks like we want to
> know if the PHY is not powered off and if it isn't, then we want to
> change the power domain ACTIVE_WAKEUP flag. Now, phy_power_off is false
> whenever any of xHCI's children enable USB wakeup.
>
> It seems like we need to way to generically propagate that knowledge up
> the parent tree. I.e., a parent needs to know if its child is wakeup
> capable, then dwc3 could, in its suspend routine:
>
> static int dwc3_suspend(struct device *dev)
> {
> /* ... */
>
> if (device_children_wakeup_capable(dev))
> device_enable_wakeup(dev);
>
> /* ... */
> }
>
> and similarly for qcom glue:
>
> static int dwc3_qcom_suspend(struct device *dev)
> {
> /* ... */
>
> if (device_children_wakeup_capable(dev)) {
> device_enable_wakeup(dev);
> genpd->flags |= GENPD_FLAG_ACTIVE_WAKEUP;
> }
>
> /* ... */
> }
>
> It also seems plausible that this could be done at driver core and
> completely hidden away from drivers.
>
device_children_wakeup_capable() idea sounds good. Added linux-pm and Rafael
for more inputs on this.
AFAICT, device wakeup settings are NOT propagated to the parent. Ideally one
expects the parent to be wake up capable and enabled when any of its children
is enabling the wakeup. If that had been propagated, we could simply check
device_may_wakeup() and take an action. I am sure there are good reason why
and how this propgation may not work as we expect it to work for all devices.
Can we make something like below to make sure that DWC3 core respects its
child wakeup setting? This is inline with your suggestion of propagating it
through layers. we should probably enable wakeup on dwc3 dev so that the
glue drivers can take the action appropriately.
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index 172dfd2..9c43d37 100644
--- a/drivers/usb/dwc3/core.c
+++ b/drivers/usb/dwc3/core.c
@@ -1749,7 +1749,7 @@ static int dwc3_suspend_common(struct dwc3 *dwc, pm_message_t msg)
dwc3_core_exit(dwc);
break;
case DWC3_GCTL_PRTCAP_HOST:
- if (!PMSG_IS_AUTO(msg)) {
+ if (!PMSG_IS_AUTO(msg) && !device_may_wakeup(&dwc->xhci->dev)) {
dwc3_core_exit(dwc);
break;
}
@@ -1810,7 +1810,7 @@ static int dwc3_resume_common(struct dwc3 *dwc, pm_message_t msg)
spin_unlock_irqrestore(&dwc->lock, flags);
break;
case DWC3_GCTL_PRTCAP_HOST:
- if (!PMSG_IS_AUTO(msg)) {
+ if (!PMSG_IS_AUTO(msg) && !device_may_wakeup(&dwc->xhci->dev)) {
ret = dwc3_core_init_for_resume(dwc);
if (ret)
return ret;
Thanks,
Pavan
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists