From: Felipe Balbi <balbi@kernel.org>
To: Sandeep Maheswaram <sanm@codeaurora.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Boyd <swboyd@chromium.org>,
Doug Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>
Cc: linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Manu Gautam <mgautam@codeaurora.org>
Subject: Re: [PATCH v7 1/5] usb: dwc3: host: Set PHY mode during suspend
Date: Mon, 03 May 2021 14:16:34 +0300 [thread overview]
Message-ID: <87k0oghxt9.fsf@kernel.org> (raw)
In-Reply-To: <fd927828-a414-cd42-1e4a-b9e9b0744a3a@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
Hi,
Sandeep Maheswaram <sanm@codeaurora.org> writes:
>>> @@ -11,6 +11,14 @@
>>> #include <linux/platform_device.h>
>>>
>>> #include "core.h"
>>> +#include "../host/xhci.h"
>>> +#include "../host/xhci-plat.h"
>>> +
>>> +static int xhci_dwc3_suspend_quirk(struct usb_hcd *hcd);
>>> +
>>> +static const struct xhci_plat_priv xhci_plat_dwc3_xhci = {
>>> + .suspend_quirk = xhci_dwc3_suspend_quirk,
>>> +};
>> we're passing data using device_properties, why do you want this here?
> Similar implemenation was done in
> drivers/usb/cdns3/host.c<https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/usb/cdns3/host.c?h=next-20210503>
then it seems we have two places to correct :-)
>>> @@ -127,6 +142,50 @@ int dwc3_host_init(struct dwc3 *dwc)
>>> return ret;
>>> }
>>>
>>> +static void dwc3_set_phy_mode(struct usb_hcd *hcd)
>>> +{
>>> +
>>> + int i, num_ports;
>>> + u32 reg;
>>> + unsigned int ss_phy_mode = 0;
>>> + struct dwc3 *dwc = dev_get_drvdata(hcd->self.controller->parent);
>>> + 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);
>> there's a big assumption here that xhci is still alive. Why isn't this
>> quirk implemented in xhci-plat itself?
>>
>>> +int xhci_dwc3_suspend_quirk(struct usb_hcd *hcd)
>> who calls this?
> This will be called from
> xhci_plat_suspend->xhci_priv_suspend_quirk->xhci_dwc3_suspend_quirk
So xhci.ko calls a function from dwc3.ko? That sounds odd, doesn't it?
It really looks like we're just finding ways to bypass the driver
layering, rather than working with it.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2021-05-03 11:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 5:11 [PATCH v7 0/5] USB DWC3 host wake up support from system suspend Sandeep Maheswaram
2021-04-28 5:11 ` [PATCH v7 1/5] usb: dwc3: host: Set PHY mode during suspend Sandeep Maheswaram
2021-04-28 9:55 ` Felipe Balbi
[not found] ` <fd927828-a414-cd42-1e4a-b9e9b0744a3a@codeaurora.org>
2021-05-03 11:16 ` Felipe Balbi [this message]
2021-05-12 19:12 ` Matthias Kaehlcke
2021-05-13 13:46 ` Felipe Balbi
2021-05-13 14:37 ` Matthias Kaehlcke
2021-04-28 5:11 ` [PATCH v7 2/5] usb: dwc3: core: Host wake up support from system suspend Sandeep Maheswaram
2021-04-28 9:59 ` Felipe Balbi
2021-05-03 4:33 ` Sandeep Maheswaram
2021-05-03 11:20 ` Felipe Balbi
2021-05-12 21:47 ` Matthias Kaehlcke
2021-05-26 4:29 ` Sandeep Maheswaram
2021-04-28 5:11 ` [PATCH v7 3/5] usb: dwc3: qcom: Add helper functions to enable,disable wake irqs Sandeep Maheswaram
2021-04-28 5:11 ` [PATCH v7 4/5] usb: dwc3: qcom: Configure wakeup interrupts during suspend Sandeep Maheswaram
2021-04-28 10:02 ` Felipe Balbi
2021-04-28 5:11 ` [PATCH v7 5/5] usb: dwc3: qcom: Keep power domain on to support wakeup Sandeep Maheswaram
2021-04-28 10:04 ` Felipe Balbi
2021-05-13 0:23 ` Matthias Kaehlcke
2021-05-13 13:49 ` Felipe Balbi
2021-05-13 14:34 ` Matthias Kaehlcke
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=87k0oghxt9.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=agross@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=mgautam@codeaurora.org \
--cc=mka@chromium.org \
--cc=sanm@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.