From: Manivannan Sadhasivam <mani@kernel.org>
To: Krishna chaitanya chundru <quic_krichai@quicinc.com>
Cc: manivannan.sadhasivam@linaro.org, quic_vbadigan@quicinc.com,
quic_ramkri@quicinc.com, linux-arm-msm@vger.kernel.org,
konrad.dybcio@linaro.org,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"open list:PCIE ENDPOINT DRIVER FOR QUALCOMM"
<linux-pci@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC v1 3/3] PCI: qcom: ep: Add wake up host op to dw_pcie_ep_ops
Date: Fri, 23 Jun 2023 11:48:39 +0530 [thread overview]
Message-ID: <20230623061839.GC5611@thinkpad> (raw)
In-Reply-To: <1686754850-29817-4-git-send-email-quic_krichai@quicinc.com>
On Wed, Jun 14, 2023 at 08:30:49PM +0530, Krishna chaitanya chundru wrote:
> Add wakeup host op to dw_pcie_ep_ops to wake up host from D3cold
> or D3hot.
>
Commit message should describe how the wakeup is implemented in the driver.
> Signed-off-by: Krishna chaitanya chundru <quic_krichai@quicinc.com>
> ---
> drivers/pci/controller/dwc/pcie-qcom-ep.c | 34 +++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/drivers/pci/controller/dwc/pcie-qcom-ep.c b/drivers/pci/controller/dwc/pcie-qcom-ep.c
> index 5d146ec..916a138 100644
> --- a/drivers/pci/controller/dwc/pcie-qcom-ep.c
> +++ b/drivers/pci/controller/dwc/pcie-qcom-ep.c
> @@ -91,6 +91,7 @@
> /* PARF_PM_CTRL register fields */
> #define PARF_PM_CTRL_REQ_EXIT_L1 BIT(1)
> #define PARF_PM_CTRL_READY_ENTR_L23 BIT(2)
> +#define PARF_PM_CTRL_XMT_PME BIT(4)
> #define PARF_PM_CTRL_REQ_NOT_ENTR_L1 BIT(5)
>
> /* PARF_MHI_CLOCK_RESET_CTRL fields */
> @@ -794,10 +795,43 @@ static void qcom_pcie_ep_init(struct dw_pcie_ep *ep)
> dw_pcie_ep_reset_bar(pci, bar);
> }
>
> +static int qcom_pcie_ep_wakeup_host(struct dw_pcie_ep *ep, u8 func_no)
> +{
> + struct dw_pcie *pci = to_dw_pcie_from_ep(ep);
> + struct qcom_pcie_ep *pcie_ep = to_pcie_ep(pci);
> + struct device *dev = pci->dev;
> + u32 perst, dstate, val;
> +
> + perst = gpiod_get_value(pcie_ep->reset);
> + /* Toggle wake GPIO when device is in D3 cold */
> + if (perst) {
> + dev_info(dev, "Device is in D3 cold toggling wake\n");
dev_dbg(). "Waking up the host by toggling WAKE#"
> + gpiod_set_value_cansleep(pcie_ep->wake, 1);
Waking a device from D3cold requires power-on sequence by the host and in the
presence of Vaux, the EPF should be prepared for that. In that case, the mode of
wakeup should be decided by the EPF driver. So the wakeup API should have an
argument to decide whether the wakeup is through PME or sideband WAKE#.
Also note that as per PCIe Spec 3.0, the devices can support PME generation from
D3cold provided that the Vaux is supplied to the device. I do not know if that
is supported by Qcom devices but API should honor the spec. So the wakeup
control should come from EPF driver as I suggested above.
> + usleep_range(WAKE_DELAY_US, WAKE_DELAY_US + 500);
> + gpiod_set_value_cansleep(pcie_ep->wake, 0);
> + return 0;
> + }
> +
> + dstate = dw_pcie_readl_dbi(pci, DBI_CON_STATUS) &
> + DBI_CON_STATUS_POWER_STATE_MASK;
> + if (dstate == 3) {
> + dev_info(dev, "Device is in D3 hot sending inband PME\n");
dev_dbg(). As I said, the device can sent PME from D3cold also. So the log could
be "Waking up the host using PME".
> + val = readl_relaxed(pcie_ep->parf + PARF_PM_CTRL);
> + val |= PARF_PM_CTRL_XMT_PME;
> + writel_relaxed(val, pcie_ep->parf + PARF_PM_CTRL);
> + } else {
> + dev_err(dev, "Device is not in D3 state wakeup is not supported\n");
> + return -EPERM;
-ENOTSUPP
- Mani
> + }
> +
> + return 0;
> +}
> +
> static const struct dw_pcie_ep_ops pci_ep_ops = {
> .ep_init = qcom_pcie_ep_init,
> .raise_irq = qcom_pcie_ep_raise_irq,
> .get_features = qcom_pcie_epc_get_features,
> + .wakeup_host = qcom_pcie_ep_wakeup_host,
> };
>
> static int qcom_pcie_ep_probe(struct platform_device *pdev)
> --
> 2.7.4
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-06-23 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1686754850-29817-1-git-send-email-quic_krichai@quicinc.com>
2023-06-14 15:00 ` [PATCH RFC v1 1/3] PCI: endpoint: Add wakeup host API to EPC core Krishna chaitanya chundru
2023-06-19 9:22 ` Kishon Vijay Abraham I
2023-06-23 5:43 ` Manivannan Sadhasivam
2023-06-26 13:40 ` Krishna Chaitanya Chundru
2023-06-27 14:36 ` Manivannan Sadhasivam
2023-06-14 15:00 ` [PATCH RFC v1 2/3] pci: dwc: Add wakeup host op to pci_epc_ops Krishna chaitanya chundru
2023-06-14 15:00 ` [PATCH RFC v1 3/3] PCI: qcom: ep: Add wake up host op to dw_pcie_ep_ops Krishna chaitanya chundru
2023-06-23 6:18 ` Manivannan Sadhasivam [this message]
2023-06-26 13:48 ` Krishna Chaitanya Chundru
2023-06-27 13:53 ` Manivannan Sadhasivam
2023-06-28 2:31 ` Krishna Chaitanya Chundru
2023-06-28 4:57 ` Manivannan Sadhasivam
2023-06-28 6:19 ` Krishna Chaitanya Chundru
2023-06-28 6:29 ` Manivannan Sadhasivam
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=20230623061839.GC5611@thinkpad \
--to=mani@kernel.org \
--cc=bhelgaas@google.com \
--cc=konrad.dybcio@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=robh@kernel.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