[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250110140934.GB2630182-robh@kernel.org>
Date: Fri, 10 Jan 2025 08:09:34 -0600
From: Rob Herring <robh@...nel.org>
To: Stephen Boyd <swboyd@...omium.org>
Cc: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>,
linux-kernel@...r.kernel.org, patches@...ts.linux.dev,
devicetree@...r.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Arnd Bergmann <arnd@...db.de>, Conor Dooley <conor+dt@...nel.org>,
Saravana Kannan <saravanak@...gle.com>,
Uwe Kleine-König <u.kleine-koenig@...libre.com>
Subject: Re: [RFC PATCH 5/6] bus: qcom-sc7180: Attach pm domain to watchdog
device
On Tue, Jan 07, 2025 at 05:28:42PM -0800, Stephen Boyd wrote:
> Find the watchdog device described as a child node of the sc7180 SoC
> node and attach a generic pm domain to the device before registering the
> device with the platform bus. The domain simply gets the clk and turns
> it on when the pm domain is powered on and turns it off when the pm
> domain is powered off.
>
> Cc: Rob Herring <robh@...nel.org>
> Cc: Bjorn Andersson <andersson@...nel.org>
> Cc: Konrad Dybcio <konradybcio@...nel.org>
> Cc: <linux-arm-msm@...r.kernel.org>
> Signed-off-by: Stephen Boyd <swboyd@...omium.org>
> ---
> drivers/bus/qcom/qcom-sc7180.c | 122 +++++++++++++++++++++++++++++++++
> 1 file changed, 122 insertions(+)
>
> diff --git a/drivers/bus/qcom/qcom-sc7180.c b/drivers/bus/qcom/qcom-sc7180.c
> index a615cf5a2129..7dfe6b32efef 100644
> --- a/drivers/bus/qcom/qcom-sc7180.c
> +++ b/drivers/bus/qcom/qcom-sc7180.c
> @@ -3,18 +3,140 @@
> * SoC bus driver for Qualcomm SC7180 SoCs
> */
>
> +#include <linux/cleanup.h>
> +#include <linux/clk.h>
> #include <linux/device.h>
> +#include <linux/dev_printk.h>
> #include <linux/init.h>
> #include <linux/mod_devicetable.h>
> #include <linux/module.h>
> #include <linux/of.h>
> #include <linux/of_platform.h>
> #include <linux/platform_device.h>
> +#include <linux/pm.h>
> +#include <linux/pm_domain.h>
> +
> +struct qcom_soc_pm_domain {
> + struct clk *clk;
> + struct generic_pm_domain pd;
> +};
> +
> +static struct qcom_soc_pm_domain *
> +gpd_to_qcom_soc_pm_domain(struct generic_pm_domain *gpd)
> +{
> + return container_of(gpd, struct qcom_soc_pm_domain, pd);
> +}
> +
> +static struct qcom_soc_pm_domain *pd_to_qcom_soc_pm_domain(struct dev_pm_domain *pd)
> +{
> + struct generic_pm_domain *gpd;
> +
> + gpd = container_of(pd, struct generic_pm_domain, domain);
> +
> + return gpd_to_qcom_soc_pm_domain(gpd);
> +}
> +
> +static struct qcom_soc_pm_domain *dev_to_qcom_soc_pm_domain(struct device *dev)
> +{
> + struct dev_pm_domain *pd;
> +
> + pd = dev->pm_domain;
> + if (!pd)
> + return NULL;
> +
> + return pd_to_qcom_soc_pm_domain(pd);
> +}
> +
> +static struct platform_device *
> +qcom_soc_alloc_device(struct platform_device *socdev, const char *compatible)
> +{
> + struct device_node *np __free(device_node);
> +
> + np = of_get_compatible_child(socdev->dev.of_node, compatible);
> +
> + return of_platform_device_alloc(np, NULL, &socdev->dev);
> +}
> +
> +static int qcom_soc_domain_activate(struct device *dev)
> +{
> + struct qcom_soc_pm_domain *soc_domain;
> +
> + dev_info(dev, "Activating device\n");
> + soc_domain = dev_to_qcom_soc_pm_domain(dev);
> +
> + soc_domain->clk = devm_clk_get(dev, NULL);
> +
> + return PTR_ERR_OR_ZERO(soc_domain->clk);
> +}
> +
> +static int qcom_soc_domain_power_on(struct generic_pm_domain *domain)
> +{
> + struct qcom_soc_pm_domain *soc_domain;
> +
> + pr_info("Powering on device\n");
> + soc_domain = gpd_to_qcom_soc_pm_domain(domain);
> +
> + return clk_prepare_enable(soc_domain->clk);
> +}
> +
> +static int qcom_soc_domain_power_off(struct generic_pm_domain *domain)
> +{
> + struct qcom_soc_pm_domain *soc_domain;
> +
> + pr_info("Powering off device\n");
> + soc_domain = gpd_to_qcom_soc_pm_domain(domain);
> +
> + clk_disable_unprepare(soc_domain->clk);
How's this going to scale when there are multiple clocks and it's not
just turn on/off all the clocks in any order? Or when there's ordering
requirements between different resources.
I'm pretty sure I've seen attempts to order clock entries in DT based on
the order they want to enable them.
> +
> + return 0;
> +}
> +
> +static int qcom_soc_add_clk_domain(struct platform_device *socdev,
> + struct platform_device *pdev)
> +{
> + struct qcom_soc_pm_domain *domain;
> + struct generic_pm_domain *pd;
> + int ret;
> +
> + domain = devm_kzalloc(&socdev->dev, sizeof(*domain), GFP_KERNEL);
> + if (!domain)
> + return -ENOMEM;
> +
> + pd = &domain->pd;
> + pd->name = "wdog";
> + ret = pm_genpd_init(pd, NULL, false);
> + if (ret)
> + return ret;
> +
> + /* TODO: Wrap this in a generic_pm_domain function similar to power_on() */
> + pd->domain.activate = qcom_soc_domain_activate;
> + pd->power_on = qcom_soc_domain_power_on;
> + pd->power_off = qcom_soc_domain_power_off;
> +
> + dev_info(&socdev->dev, "adding pm domain for %s\n", dev_name(&pdev->dev));
> + dev_pm_domain_set(&pdev->dev, &pd->domain);
> +
> + return 0;
> +}
>
> static int qcom_soc_sc7180_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> struct device_node *np = dev->of_node;
> + struct platform_device *sdev;
> + int ret;
> +
> + sdev = qcom_soc_alloc_device(pdev, "qcom,apss-wdt-sc7180");
We're going to have to have an explicit call for every child node?
> + if (!sdev)
> + return dev_err_probe(dev, -ENODEV, "Failed to alloc sdev\n");
> +
> + ret = qcom_soc_add_clk_domain(pdev, sdev);
> + if (ret)
> + return dev_err_probe(dev, ret, "Failed to add clk domain to sdev\n");
> +
> + ret = of_platform_device_add(sdev);
> + if (ret)
> + return dev_err_probe(dev, ret, "Failed to add sdev to bus\n");
>
> return of_platform_populate(np, NULL, NULL, dev);
> }
> --
> https://chromeos.dev
>
Powered by blists - more mailing lists