From: Ryder Lee <ryder.lee@mediatek.com>
To: honghui.zhang@mediatek.com
Cc: lorenzo.pieralisi@arm.com, marc.zyngier@arm.com,
bhelgaas@google.com, matthias.bgg@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
yingjoe.chen@mediatek.com, eddie.huang@mediatek.com,
hongkun.cao@mediatek.com, youlin.pei@mediatek.com,
yong.wu@mediatek.com, yt.shen@mediatek.com,
sean.wang@mediatek.com, xinping.qian@mediatek.com
Subject: Re: [PATCH] PCI: mediatek: Add system pm support for MT2712
Date: Thu, 31 May 2018 10:05:36 +0800 [thread overview]
Message-ID: <1527732336.9842.3.camel@mtkswgap22> (raw)
In-Reply-To: <1527647736-19986-1-git-send-email-honghui.zhang@mediatek.com>
On Wed, 2018-05-30 at 10:35 +0800, honghui.zhang@mediatek.com wrote:
> From: Honghui Zhang <honghui.zhang@mediatek.com>
>
> The MTCMOS of PCIe Host for MT2712 will be off when system suspend, and all
> the internel control register will be reset after system resume. The PCIe
> link should be re-established and the related control register values should
> be re-set after system resume.
>
> Signed-off-by: Honghui Zhang <honghui.zhang@mediatek.com>
> CC: Ryder Lee <ryder.lee@mediatek.com>
> ---
> drivers/pci/host/pcie-mediatek.c | 82 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 82 insertions(+)
>
> diff --git a/drivers/pci/host/pcie-mediatek.c b/drivers/pci/host/pcie-mediatek.c
> index dabf1086..60f98d92 100644
> --- a/drivers/pci/host/pcie-mediatek.c
> +++ b/drivers/pci/host/pcie-mediatek.c
> @@ -132,12 +132,14 @@ struct mtk_pcie_port;
> /**
> * struct mtk_pcie_soc - differentiate between host generations
> * @need_fix_class_id: whether this host's class ID needed to be fixed or not
> + * @pm_support: whether the host's MTCMOS will be off when suspend
> * @ops: pointer to configuration access functions
> * @startup: pointer to controller setting functions
> * @setup_irq: pointer to initialize IRQ functions
> */
> struct mtk_pcie_soc {
> bool need_fix_class_id;
> + bool pm_support;
> struct pci_ops *ops;
> int (*startup)(struct mtk_pcie_port *port);
> int (*setup_irq)(struct mtk_pcie_port *port, struct device_node *node);
> @@ -1179,12 +1181,91 @@ static int mtk_pcie_probe(struct platform_device *pdev)
> return err;
> }
>
> +static int __maybe_unused mtk_pcie_suspend_noirq(struct device *dev)
> +{
> + struct platform_device *pdev;
> + struct mtk_pcie *pcie;
> + struct mtk_pcie_port *port;
> + const struct mtk_pcie_soc *soc;
> +
> + pdev = to_platform_device(dev);
> + pcie = platform_get_drvdata(pdev);
How about this -
struct mtk_pcie *pcie = dev_get_drvdata(dev);
> + soc = pcie->soc;
> + if (!soc->pm_support)
> + return 0;
> +
> + list_for_each_entry(port, &pcie->ports, list) {
> + clk_disable_unprepare(port->ahb_ck);
> + clk_disable_unprepare(port->sys_ck);
> + phy_power_off(port->phy);
> + }
> +
> + return 0;
> +}
> +
> +static int __maybe_unused mtk_pcie_resume_noirq(struct device *dev)
> +{
> + struct platform_device *pdev;
> + struct mtk_pcie *pcie;
> + struct mtk_pcie_port *port;
> + const struct mtk_pcie_soc *soc;
> + int ret;
> +
> + pdev = to_platform_device(dev);
> + pcie = platform_get_drvdata(pdev);
struct mtk_pcie *pcie = dev_get_drvdata(dev);
> + soc = pcie->soc;
> + if (!soc->pm_support)
> + return 0;
> +
> + list_for_each_entry(port, &pcie->ports, list) {
> + ret = phy_power_on(port->phy);
> + if (ret) {
> + dev_err(dev, "could not power on phy\n");
> + return ret;
> + }
> + ret = clk_prepare_enable(port->sys_ck);
> + if (ret) {
> + dev_err(dev, "enable sys clock error\n");
> + phy_power_off(port->phy);
> + return ret;
> + }
> +
> + ret = clk_prepare_enable(port->ahb_ck);
> + if (ret) {
> + dev_err(dev, "enable ahb clock error\n");
> + phy_power_off(port->phy);
> + clk_disable_unprepare(port->sys_ck);
> + return ret;
> + }
> +
> + ret = soc->startup(port);
> + if (ret) {
> + dev_err(dev, "pcie linkup failed\n");
> + phy_power_off(port->phy);
> + clk_disable_unprepare(port->sys_ck);
> + clk_disable_unprepare(port->ahb_ck);
> + return ret;
> + }
> +
> + if (IS_ENABLED(CONFIG_PCI_MSI))
> + mtk_pcie_enable_msi(port);
> + }
> +
> + return 0;
> +}
> +
next prev parent reply other threads:[~2018-05-31 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 2:35 [PATCH] PCI: mediatek: Add system pm support for MT2712 honghui.zhang
2018-05-31 2:05 ` Ryder Lee [this message]
2018-05-31 2:19 ` Honghui Zhang
2018-05-31 4:20 ` Bjorn Helgaas
2018-05-31 7:37 ` Honghui Zhang
2018-06-01 0:42 ` [RFC PATCH] PCI: mediatek: mtk_pcie_pm_ops can be static kbuild test robot
2018-06-01 0:42 ` [PATCH] PCI: mediatek: Add system pm support for MT2712 kbuild test robot
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=1527732336.9842.3.camel@mtkswgap22 \
--to=ryder.lee@mediatek.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=honghui.zhang@mediatek.com \
--cc=hongkun.cao@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@mediatek.com \
--cc=xinping.qian@mediatek.com \
--cc=yingjoe.chen@mediatek.com \
--cc=yong.wu@mediatek.com \
--cc=youlin.pei@mediatek.com \
--cc=yt.shen@mediatek.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;
as well as URLs for NNTP newsgroup(s).