From: Pavan Kondeti <quic_pkondeti@quicinc.com>
To: Pavan Kondeti <quic_pkondeti@quicinc.com>
Cc: Sandeep Maheswaram <quic_c_sanm@quicinc.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Doug Anderson <dianders@chromium.org>,
"Matthias Kaehlcke" <mka@chromium.org>,
Mathias Nyman <mathias.nyman@intel.com>,
<linux-arm-msm@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_ppratap@quicinc.com>,
<quic_kriskura@quicinc.com>
Subject: Re: [PATCH v11 2/5] usb: dwc3: core: Host wake up support from system suspend
Date: Tue, 5 Apr 2022 14:55:57 +0530 [thread overview]
Message-ID: <20220405092557.GA15621@hu-pkondeti-hyd.qualcomm.com> (raw)
In-Reply-To: <20220322083221.GJ23316@hu-pkondeti-hyd.qualcomm.com>
Hi Sandeep,
On Tue, Mar 22, 2022 at 02:02:21PM +0530, Pavan Kondeti wrote:
> Hi Sandeep,
>
> On Tue, Mar 22, 2022 at 12:37:53PM +0530, Sandeep Maheswaram wrote:
> > During suspend read the status of all port and make sure the PHYs
> > are in the correct mode based on current speed.
> > Phy interrupt masks are set based on this mode. Keep track of the mode
> > of the HS PHY to be able to configure wakeup properly.
> >
> > Also check during suspend if any wakeup capable devices are
> > connected to the controller (directly or through hubs), if there
> > are none set a flag to indicate that the PHY is powered
> > down during suspend.
> >
> > Signed-off-by: Sandeep Maheswaram <quic_c_sanm@quicinc.com>
> > ---
> > drivers/usb/dwc3/core.c | 54 ++++++++++++++++++++++++++++++++++++++++---------
> > 1 file changed, 45 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> > index 1170b80..232a734 100644
> > --- a/drivers/usb/dwc3/core.c
> > +++ b/drivers/usb/dwc3/core.c
> > @@ -32,12 +32,14 @@
> > #include <linux/usb/gadget.h>
> > #include <linux/usb/of.h>
> > #include <linux/usb/otg.h>
> > +#include <linux/usb/hcd.h>
> >
> > #include "core.h"
> > #include "gadget.h"
> > #include "io.h"
> >
> > #include "debug.h"
> > +#include "../host/xhci.h"
> >
> > #define DWC3_DEFAULT_AUTOSUSPEND_DELAY 5000 /* ms */
> >
> > @@ -1861,10 +1863,36 @@ static int dwc3_core_init_for_resume(struct dwc3 *dwc)
> > return ret;
> > }
> >
> > +static void dwc3_set_phy_speed_mode(struct dwc3 *dwc)
> > +{
> > +
> > + int i, num_ports;
> > + u32 reg;
> > + struct usb_hcd *hcd = platform_get_drvdata(dwc->xhci);
> > + struct xhci_hcd *xhci_hcd = hcd_to_xhci(hcd);
> > +
> > + dwc->hs_phy_mode = 0;
> > +
> > + reg = readl(&xhci_hcd->cap_regs->hcs_params1);
> > +
> > + num_ports = HCS_MAX_PORTS(reg);
> > + for (i = 0; i < num_ports; i++) {
> > + reg = readl(&xhci_hcd->op_regs->port_status_base + i * 0x04);
> > + if (reg & PORT_PE) {
> > + if (DEV_HIGHSPEED(reg) || DEV_FULLSPEED(reg))
> > + dwc->hs_phy_mode |= PHY_MODE_USB_HOST_HS;
> > + else if (DEV_LOWSPEED(reg))
> > + dwc->hs_phy_mode |= PHY_MODE_USB_HOST_LS;
> > + }
> > + }
> > + phy_set_mode(dwc->usb2_generic_phy, dwc->hs_phy_mode);
> > +}
>
> Are these flags cleared somewhere? Also qcom-snps-hs phy driver checks
> for (hsphy->mode == PHY_MODE_USB_HOST) condition in qcom_snps_hsphy_suspend
> to enable auto-resume. PHY_MODE_USB_HOST_HS/PHY_MODE_USB_HOST_LS flags
> are different from PHY_MODE_USB_HOST. Currently this flag is set from
> __dwc3_set_mode() when entering host mode. Can you clarify your intention
> in calling phy_set_mode() here.
I think re-purposing phy_set_mode() to override PHY_MODE_USB_HOST with
PHY_MODE_USB_HOST_HS/PHY_MODE_USB_HOST_LS might break other drivers. All
most all the phy drivers are checking against PHY_MODE_USB_HOST.
Why do we need to set phy_set_mode() here? The next patch in this series
only uses dwc->hs_phy_mode. can we drop phy_set_mode() call here?
Thanks,
Pavan
next prev parent reply other threads:[~2022-04-05 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 7:07 [PATCH v11 0/5] USB DWC3 host wake up support from system suspend Sandeep Maheswaram
2022-03-22 7:07 ` [PATCH v11 1/5] usb: dwc3: core: Add HS phy mode variable and phy poweroff flag Sandeep Maheswaram
2022-03-22 8:09 ` Pavan Kondeti
2022-03-22 8:42 ` Sandeep Maheswaram (Temp)
2022-03-22 7:07 ` [PATCH v11 2/5] usb: dwc3: core: Host wake up support from system suspend Sandeep Maheswaram
2022-03-22 8:32 ` Pavan Kondeti
2022-03-22 8:40 ` Pavan Kondeti
2022-04-05 9:25 ` Pavan Kondeti [this message]
2022-03-23 18:07 ` Matthias Kaehlcke
2022-03-24 4:54 ` Sandeep Maheswaram (Temp)
2022-03-30 4:03 ` Pavan Kondeti
2022-03-30 16:46 ` Matthias Kaehlcke
2022-03-31 3:14 ` Pavan Kondeti
2022-03-22 7:07 ` [PATCH v11 3/5] usb: dwc3: qcom: Add helper functions to enable,disable wake irqs Sandeep Maheswaram
2022-03-22 8:33 ` Pavan Kondeti
2022-03-22 7:07 ` [PATCH v11 4/5] usb: dwc3: qcom: Configure wakeup interrupts during suspend Sandeep Maheswaram
2022-03-22 8:36 ` Pavan Kondeti
2022-03-22 7:07 ` [PATCH v11 5/5] usb: dwc3: qcom: Keep power domain on to retain controller status Sandeep Maheswaram
2022-03-22 8:37 ` Pavan Kondeti
2022-03-22 9:18 ` Sandeep Maheswaram (Temp)
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=20220405092557.GA15621@hu-pkondeti-hyd.qualcomm.com \
--to=quic_pkondeti@quicinc.com \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mka@chromium.org \
--cc=quic_c_sanm@quicinc.com \
--cc=quic_kriskura@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=swboyd@chromium.org \
/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).