| Message ID | 20241206211145.2823-2-ansuelsmth@gmail.com (mailing list archive) |
|---|---|
| State | New |
| Delegated to: | viresh kumar |
| Headers | show |
| Series | [v7,1/2] dt-bindings: cpufreq: Document support for Airoha EN7581 CPUFreq | expand |
On Fri, 6 Dec 2024 at 22:16, Christian Marangi <ansuelsmth@gmail.com> wrote: > > Add simple CPU Freq driver for Airoha EN7581 SoC that control CPU > frequency scaling with SMC APIs and register a generic "cpufreq-dt" > device. > > CPUFreq driver registers a get-only clock to get the current global CPU > frequency from SMC and a Power Domain to configure the performance state > for each OPP to apply the requested frequency from cpufreq-dt. This is > needed as SMC use index instead of raw frequency. > > All CPU share the same frequency and can't be controlled independently. > Current shared CPU frequency is returned by the related SMC command. > > Add SoC compatible to cpufreq-dt-plat block list as a dedicated cpufreq > driver is needed with OPP v2 nodes declared in DTS. > > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> > --- > Changes v7: > - No changes > Changes v6: > - Improve Kconfig depends logic > - Select PM (PM_GENERIC_DOMAINS depends on it) > - Drop (int) cast for > Changes v5: > - Rename cpu_pd to perf for power domain name > - Use remove instead of remove_new > Changes v4: > - Rework to clk-only + PM set_performance_state implementation > Changes v3: > - Adapt to new cpufreq-dt APIs > - Register cpufreq-dt instead of custom freq driver > Changes v2: > - Fix kernel bot error with missing slab.h and bitfield.h header > - Limit COMPILE_TEST to ARM64 due to smcc 1.2 > > drivers/cpufreq/Kconfig.arm | 10 ++ > drivers/cpufreq/Makefile | 1 + > drivers/cpufreq/airoha-cpufreq.c | 222 +++++++++++++++++++++++++++ Hmm, it looks like this needs to be moved and possibly split up. The provider part (for the clock and power-domain) belongs in /drivers/pmdomain/*, along with the other power-domain providers. Other than that, I was really expecting the cpufreq-dt to take care of the rest. > drivers/cpufreq/cpufreq-dt-platdev.c | 2 + > 4 files changed, 235 insertions(+) > create mode 100644 drivers/cpufreq/airoha-cpufreq.c > > diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm > index 5f7e13e60c80..8494faac58ae 100644 > --- a/drivers/cpufreq/Kconfig.arm > +++ b/drivers/cpufreq/Kconfig.arm > @@ -15,6 +15,16 @@ config ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM > To compile this driver as a module, choose M here: the > module will be called sun50i-cpufreq-nvmem. > > +config ARM_AIROHA_SOC_CPUFREQ > + tristate "Airoha EN7581 SoC CPUFreq support" > + depends on ARM64 && (ARCH_AIROHA || COMPILE_TEST) > + select PM > + select PM_OPP > + select PM_GENERIC_DOMAINS > + default ARCH_AIROHA > + help > + This adds the CPUFreq driver for Airoha EN7581 SoCs. > + > config ARM_APPLE_SOC_CPUFREQ > tristate "Apple Silicon SoC CPUFreq support" > depends on ARCH_APPLE || (COMPILE_TEST && 64BIT) > diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile > index d35a28dd9463..890fff99f37d 100644 > --- a/drivers/cpufreq/Makefile > +++ b/drivers/cpufreq/Makefile > @@ -53,6 +53,7 @@ obj-$(CONFIG_X86_AMD_FREQ_SENSITIVITY) += amd_freq_sensitivity.o > > ################################################################################## > # ARM SoC drivers > +obj-$(CONFIG_ARM_AIROHA_SOC_CPUFREQ) += airoha-cpufreq.o > obj-$(CONFIG_ARM_APPLE_SOC_CPUFREQ) += apple-soc-cpufreq.o > obj-$(CONFIG_ARM_ARMADA_37XX_CPUFREQ) += armada-37xx-cpufreq.o > obj-$(CONFIG_ARM_ARMADA_8K_CPUFREQ) += armada-8k-cpufreq.o > diff --git a/drivers/cpufreq/airoha-cpufreq.c b/drivers/cpufreq/airoha-cpufreq.c > new file mode 100644 > index 000000000000..29738f61f401 > --- /dev/null > +++ b/drivers/cpufreq/airoha-cpufreq.c > @@ -0,0 +1,222 @@ > +// SPDX-License-Identifier: GPL-2.0 > + > +#include <linux/arm-smccc.h> > +#include <linux/bitfield.h> > +#include <linux/cpufreq.h> > +#include <linux/clk-provider.h> > +#include <linux/module.h> > +#include <linux/platform_device.h> > +#include <linux/pm_domain.h> > +#include <linux/pm_runtime.h> > +#include <linux/slab.h> > + > +#include "cpufreq-dt.h" > + > +#define AIROHA_SIP_AVS_HANDLE 0x82000301 > +#define AIROHA_AVS_OP_BASE 0xddddddd0 > +#define AIROHA_AVS_OP_MASK GENMASK(1, 0) > +#define AIROHA_AVS_OP_FREQ_DYN_ADJ (AIROHA_AVS_OP_BASE | \ > + FIELD_PREP(AIROHA_AVS_OP_MASK, 0x1)) > +#define AIROHA_AVS_OP_GET_FREQ (AIROHA_AVS_OP_BASE | \ > + FIELD_PREP(AIROHA_AVS_OP_MASK, 0x2)) > + > +struct airoha_cpufreq_priv { > + struct clk_hw hw; > + struct generic_pm_domain pd; > + > + int opp_token; > + struct dev_pm_domain_list *pd_list; > + struct platform_device *cpufreq_dt; > +}; > + > +static long airoha_cpufreq_clk_round(struct clk_hw *hw, unsigned long rate, > + unsigned long *parent_rate) > +{ > + return rate; > +} > + > +static unsigned long airoha_cpufreq_clk_get(struct clk_hw *hw, > + unsigned long parent_rate) > +{ > + const struct arm_smccc_1_2_regs args = { > + .a0 = AIROHA_SIP_AVS_HANDLE, > + .a1 = AIROHA_AVS_OP_GET_FREQ, > + }; > + struct arm_smccc_1_2_regs res; > + > + arm_smccc_1_2_smc(&args, &res); > + > + /* SMCCC returns freq in MHz */ > + return res.a0 * 1000 * 1000; > +} > + > +/* Airoha CPU clk SMCC is always enabled */ > +static int airoha_cpufreq_clk_is_enabled(struct clk_hw *hw) > +{ > + return true; > +} > + > +static const struct clk_ops airoha_cpufreq_clk_ops = { > + .recalc_rate = airoha_cpufreq_clk_get, > + .is_enabled = airoha_cpufreq_clk_is_enabled, > + .round_rate = airoha_cpufreq_clk_round, > +}; > + > +static const char * const airoha_cpufreq_clk_names[] = { "cpu", NULL }; > + > +/* NOP function to disable OPP from setting clock */ > +static int airoha_cpufreq_config_clks_nop(struct device *dev, > + struct opp_table *opp_table, > + struct dev_pm_opp *opp, > + void *data, bool scaling_down) > +{ > + return 0; > +} > + > +static const char * const airoha_cpufreq_pd_names[] = { "perf" }; > + > +static int airoha_cpufreq_set_performance_state(struct generic_pm_domain *domain, > + unsigned int state) > +{ > + const struct arm_smccc_1_2_regs args = { > + .a0 = AIROHA_SIP_AVS_HANDLE, > + .a1 = AIROHA_AVS_OP_FREQ_DYN_ADJ, > + .a3 = state, > + }; > + struct arm_smccc_1_2_regs res; > + > + arm_smccc_1_2_smc(&args, &res); > + > + /* SMC signal correct apply by unsetting BIT 0 */ > + return res.a0 & BIT(0) ? -EINVAL : 0; > +} > + > +static int airoha_cpufreq_probe(struct platform_device *pdev) > +{ > + const struct dev_pm_domain_attach_data attach_data = { > + .pd_names = airoha_cpufreq_pd_names, > + .num_pd_names = ARRAY_SIZE(airoha_cpufreq_pd_names), > + .pd_flags = PD_FLAG_DEV_LINK_ON | PD_FLAG_REQUIRED_OPP, > + }; > + struct dev_pm_opp_config config = { > + .clk_names = airoha_cpufreq_clk_names, > + .config_clks = airoha_cpufreq_config_clks_nop, > + }; > + struct platform_device *cpufreq_dt; > + struct airoha_cpufreq_priv *priv; > + struct device *dev = &pdev->dev; > + const struct clk_init_data init = { > + .name = "cpu", > + .ops = &airoha_cpufreq_clk_ops, > + /* Clock with no set_rate, can't cache */ > + .flags = CLK_GET_RATE_NOCACHE, > + }; > + struct generic_pm_domain *pd; > + struct device *cpu_dev; > + int ret; > + > + /* CPUs refer to the same OPP table */ > + cpu_dev = get_cpu_device(0); > + if (!cpu_dev) > + return -ENODEV; > + > + priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL); > + if (!priv) > + return -ENOMEM; > + > + /* Init and register a get-only clk for Cpufreq */ > + priv->hw.init = &init; > + ret = devm_clk_hw_register(dev, &priv->hw); > + if (ret) > + return ret; > + > + ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_simple_get, > + &priv->hw); > + if (ret) > + return ret; > + > + /* Init and register a PD for Cpufreq */ > + pd = &priv->pd; > + pd->name = "cpu_pd"; > + pd->flags = GENPD_FLAG_ALWAYS_ON; > + pd->set_performance_state = airoha_cpufreq_set_performance_state; > + > + ret = pm_genpd_init(pd, NULL, false); > + if (ret) > + return ret; > + > + ret = of_genpd_add_provider_simple(dev->of_node, pd); > + if (ret) > + goto err_add_provider; > + To me, the above code belongs in a power-domain provider driver. While the below should be taken care of in cpufreq-dt, except for the device registration of the cpufreq-dt device, I guess. Viresh, what's your view on this? > + /* Set OPP table conf with NOP config_clks */ > + priv->opp_token = dev_pm_opp_set_config(cpu_dev, &config); > + if (priv->opp_token < 0) { > + ret = priv->opp_token; > + dev_err(dev, "Failed to set OPP config\n"); > + goto err_set_config; > + } > + > + /* Attach PM for OPP */ > + ret = dev_pm_domain_attach_list(cpu_dev, &attach_data, > + &priv->pd_list); > + if (ret) > + goto err_attach_pm; > + > + cpufreq_dt = platform_device_register_simple("cpufreq-dt", -1, NULL, 0); > + ret = PTR_ERR_OR_ZERO(cpufreq_dt); > + if (ret) { > + dev_err(dev, "failed to create cpufreq-dt device: %d\n", ret); > + goto err_register_cpufreq; > + } > + > + priv->cpufreq_dt = cpufreq_dt; > + platform_set_drvdata(pdev, priv); > + > + return 0; > + > +err_register_cpufreq: > + dev_pm_domain_detach_list(priv->pd_list); > +err_attach_pm: > + dev_pm_opp_clear_config(priv->opp_token); > +err_set_config: > + of_genpd_del_provider(dev->of_node); > +err_add_provider: > + pm_genpd_remove(pd); > + > + return ret; > +} > + > +static void airoha_cpufreq_remove(struct platform_device *pdev) > +{ > + struct airoha_cpufreq_priv *priv = platform_get_drvdata(pdev); > + > + platform_device_unregister(priv->cpufreq_dt); > + > + dev_pm_domain_detach_list(priv->pd_list); > + > + dev_pm_opp_clear_config(priv->opp_token); > + > + of_genpd_del_provider(pdev->dev.of_node); > + pm_genpd_remove(&priv->pd); > +} > + > +static const struct of_device_id airoha_cpufreq_of_match[] = { > + { .compatible = "airoha,en7581-cpufreq" }, > + { }, > +}; > +MODULE_DEVICE_TABLE(of, airoha_cpufreq_of_match); > + > +static struct platform_driver airoha_cpufreq_driver = { > + .probe = airoha_cpufreq_probe, > + .remove = airoha_cpufreq_remove, > + .driver = { > + .name = "airoha-cpufreq", > + .of_match_table = airoha_cpufreq_of_match, > + }, > +}; > +module_platform_driver(airoha_cpufreq_driver); > + > +MODULE_AUTHOR("Christian Marangi <ansuelsmth@gmail.com>"); > +MODULE_DESCRIPTION("CPUfreq driver for Airoha SoCs"); > +MODULE_LICENSE("GPL"); > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c > index 9c198bd4f7e9..2aa00769cf09 100644 > --- a/drivers/cpufreq/cpufreq-dt-platdev.c > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c > @@ -103,6 +103,8 @@ static const struct of_device_id allowlist[] __initconst = { > * platforms using "operating-points-v2" property. > */ > static const struct of_device_id blocklist[] __initconst = { > + { .compatible = "airoha,en7581", }, > + > { .compatible = "allwinner,sun50i-a100" }, > { .compatible = "allwinner,sun50i-h6", }, > { .compatible = "allwinner,sun50i-h616", }, > -- > 2.45.2 > > Kind regards Uffe
On Thu, 12 Dec 2024 at 13:01, Ulf Hansson <ulf.hansson@linaro.org> wrote: > > On Fri, 6 Dec 2024 at 22:16, Christian Marangi <ansuelsmth@gmail.com> wrote: > > > > Add simple CPU Freq driver for Airoha EN7581 SoC that control CPU > > frequency scaling with SMC APIs and register a generic "cpufreq-dt" > > device. > > > > CPUFreq driver registers a get-only clock to get the current global CPU > > frequency from SMC and a Power Domain to configure the performance state > > for each OPP to apply the requested frequency from cpufreq-dt. This is > > needed as SMC use index instead of raw frequency. > > > > All CPU share the same frequency and can't be controlled independently. > > Current shared CPU frequency is returned by the related SMC command. > > > > Add SoC compatible to cpufreq-dt-plat block list as a dedicated cpufreq > > driver is needed with OPP v2 nodes declared in DTS. > > > > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> > > --- > > Changes v7: > > - No changes > > Changes v6: > > - Improve Kconfig depends logic > > - Select PM (PM_GENERIC_DOMAINS depends on it) > > - Drop (int) cast for > > Changes v5: > > - Rename cpu_pd to perf for power domain name > > - Use remove instead of remove_new > > Changes v4: > > - Rework to clk-only + PM set_performance_state implementation > > Changes v3: > > - Adapt to new cpufreq-dt APIs > > - Register cpufreq-dt instead of custom freq driver > > Changes v2: > > - Fix kernel bot error with missing slab.h and bitfield.h header > > - Limit COMPILE_TEST to ARM64 due to smcc 1.2 > > > > drivers/cpufreq/Kconfig.arm | 10 ++ > > drivers/cpufreq/Makefile | 1 + > > drivers/cpufreq/airoha-cpufreq.c | 222 +++++++++++++++++++++++++++ > > Hmm, it looks like this needs to be moved and possibly split up. > > The provider part (for the clock and power-domain) belongs in > /drivers/pmdomain/*, along with the other power-domain providers. > > Other than that, I was really expecting the cpufreq-dt to take care of the rest. > > > drivers/cpufreq/cpufreq-dt-platdev.c | 2 + > > 4 files changed, 235 insertions(+) > > create mode 100644 drivers/cpufreq/airoha-cpufreq.c > > > > diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm > > index 5f7e13e60c80..8494faac58ae 100644 > > --- a/drivers/cpufreq/Kconfig.arm > > +++ b/drivers/cpufreq/Kconfig.arm > > @@ -15,6 +15,16 @@ config ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM > > To compile this driver as a module, choose M here: the > > module will be called sun50i-cpufreq-nvmem. > > > > +config ARM_AIROHA_SOC_CPUFREQ > > + tristate "Airoha EN7581 SoC CPUFreq support" > > + depends on ARM64 && (ARCH_AIROHA || COMPILE_TEST) > > + select PM > > + select PM_OPP > > + select PM_GENERIC_DOMAINS > > + default ARCH_AIROHA > > + help > > + This adds the CPUFreq driver for Airoha EN7581 SoCs. > > + > > config ARM_APPLE_SOC_CPUFREQ > > tristate "Apple Silicon SoC CPUFreq support" > > depends on ARCH_APPLE || (COMPILE_TEST && 64BIT) > > diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile > > index d35a28dd9463..890fff99f37d 100644 > > --- a/drivers/cpufreq/Makefile > > +++ b/drivers/cpufreq/Makefile > > @@ -53,6 +53,7 @@ obj-$(CONFIG_X86_AMD_FREQ_SENSITIVITY) += amd_freq_sensitivity.o > > > > ################################################################################## > > # ARM SoC drivers > > +obj-$(CONFIG_ARM_AIROHA_SOC_CPUFREQ) += airoha-cpufreq.o > > obj-$(CONFIG_ARM_APPLE_SOC_CPUFREQ) += apple-soc-cpufreq.o > > obj-$(CONFIG_ARM_ARMADA_37XX_CPUFREQ) += armada-37xx-cpufreq.o > > obj-$(CONFIG_ARM_ARMADA_8K_CPUFREQ) += armada-8k-cpufreq.o > > diff --git a/drivers/cpufreq/airoha-cpufreq.c b/drivers/cpufreq/airoha-cpufreq.c > > new file mode 100644 > > index 000000000000..29738f61f401 > > --- /dev/null > > +++ b/drivers/cpufreq/airoha-cpufreq.c > > @@ -0,0 +1,222 @@ > > +// SPDX-License-Identifier: GPL-2.0 > > + > > +#include <linux/arm-smccc.h> > > +#include <linux/bitfield.h> > > +#include <linux/cpufreq.h> > > +#include <linux/clk-provider.h> > > +#include <linux/module.h> > > +#include <linux/platform_device.h> > > +#include <linux/pm_domain.h> > > +#include <linux/pm_runtime.h> > > +#include <linux/slab.h> > > + > > +#include "cpufreq-dt.h" > > + > > +#define AIROHA_SIP_AVS_HANDLE 0x82000301 > > +#define AIROHA_AVS_OP_BASE 0xddddddd0 > > +#define AIROHA_AVS_OP_MASK GENMASK(1, 0) > > +#define AIROHA_AVS_OP_FREQ_DYN_ADJ (AIROHA_AVS_OP_BASE | \ > > + FIELD_PREP(AIROHA_AVS_OP_MASK, 0x1)) > > +#define AIROHA_AVS_OP_GET_FREQ (AIROHA_AVS_OP_BASE | \ > > + FIELD_PREP(AIROHA_AVS_OP_MASK, 0x2)) > > + > > +struct airoha_cpufreq_priv { > > + struct clk_hw hw; > > + struct generic_pm_domain pd; > > + > > + int opp_token; > > + struct dev_pm_domain_list *pd_list; > > + struct platform_device *cpufreq_dt; > > +}; > > + > > +static long airoha_cpufreq_clk_round(struct clk_hw *hw, unsigned long rate, > > + unsigned long *parent_rate) > > +{ > > + return rate; > > +} > > + > > +static unsigned long airoha_cpufreq_clk_get(struct clk_hw *hw, > > + unsigned long parent_rate) > > +{ > > + const struct arm_smccc_1_2_regs args = { > > + .a0 = AIROHA_SIP_AVS_HANDLE, > > + .a1 = AIROHA_AVS_OP_GET_FREQ, > > + }; > > + struct arm_smccc_1_2_regs res; > > + > > + arm_smccc_1_2_smc(&args, &res); > > + > > + /* SMCCC returns freq in MHz */ > > + return res.a0 * 1000 * 1000; > > +} > > + > > +/* Airoha CPU clk SMCC is always enabled */ > > +static int airoha_cpufreq_clk_is_enabled(struct clk_hw *hw) > > +{ > > + return true; > > +} > > + > > +static const struct clk_ops airoha_cpufreq_clk_ops = { > > + .recalc_rate = airoha_cpufreq_clk_get, > > + .is_enabled = airoha_cpufreq_clk_is_enabled, > > + .round_rate = airoha_cpufreq_clk_round, > > +}; > > + > > +static const char * const airoha_cpufreq_clk_names[] = { "cpu", NULL }; > > + > > +/* NOP function to disable OPP from setting clock */ > > +static int airoha_cpufreq_config_clks_nop(struct device *dev, > > + struct opp_table *opp_table, > > + struct dev_pm_opp *opp, > > + void *data, bool scaling_down) > > +{ > > + return 0; > > +} > > + > > +static const char * const airoha_cpufreq_pd_names[] = { "perf" }; > > + > > +static int airoha_cpufreq_set_performance_state(struct generic_pm_domain *domain, > > + unsigned int state) > > +{ > > + const struct arm_smccc_1_2_regs args = { > > + .a0 = AIROHA_SIP_AVS_HANDLE, > > + .a1 = AIROHA_AVS_OP_FREQ_DYN_ADJ, > > + .a3 = state, > > + }; > > + struct arm_smccc_1_2_regs res; > > + > > + arm_smccc_1_2_smc(&args, &res); > > + > > + /* SMC signal correct apply by unsetting BIT 0 */ > > + return res.a0 & BIT(0) ? -EINVAL : 0; > > +} > > + > > +static int airoha_cpufreq_probe(struct platform_device *pdev) > > +{ > > + const struct dev_pm_domain_attach_data attach_data = { > > + .pd_names = airoha_cpufreq_pd_names, > > + .num_pd_names = ARRAY_SIZE(airoha_cpufreq_pd_names), > > + .pd_flags = PD_FLAG_DEV_LINK_ON | PD_FLAG_REQUIRED_OPP, > > + }; > > + struct dev_pm_opp_config config = { > > + .clk_names = airoha_cpufreq_clk_names, > > + .config_clks = airoha_cpufreq_config_clks_nop, > > + }; > > + struct platform_device *cpufreq_dt; > > + struct airoha_cpufreq_priv *priv; > > + struct device *dev = &pdev->dev; > > + const struct clk_init_data init = { > > + .name = "cpu", > > + .ops = &airoha_cpufreq_clk_ops, > > + /* Clock with no set_rate, can't cache */ > > + .flags = CLK_GET_RATE_NOCACHE, > > + }; > > + struct generic_pm_domain *pd; > > + struct device *cpu_dev; > > + int ret; > > + > > + /* CPUs refer to the same OPP table */ > > + cpu_dev = get_cpu_device(0); > > + if (!cpu_dev) > > + return -ENODEV; > > + > > + priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL); > > + if (!priv) > > + return -ENOMEM; > > + > > + /* Init and register a get-only clk for Cpufreq */ > > + priv->hw.init = &init; > > + ret = devm_clk_hw_register(dev, &priv->hw); > > + if (ret) > > + return ret; > > + > > + ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_simple_get, > > + &priv->hw); > > + if (ret) > > + return ret; > > + > > + /* Init and register a PD for Cpufreq */ > > + pd = &priv->pd; > > + pd->name = "cpu_pd"; > > + pd->flags = GENPD_FLAG_ALWAYS_ON; > > + pd->set_performance_state = airoha_cpufreq_set_performance_state; > > + > > + ret = pm_genpd_init(pd, NULL, false); > > + if (ret) > > + return ret; > > + > > + ret = of_genpd_add_provider_simple(dev->of_node, pd); > > + if (ret) > > + goto err_add_provider; > > + > > To me, the above code belongs in a power-domain provider driver. While > the below should be taken care of in cpufreq-dt, except for the device > registration of the cpufreq-dt device, I guess. > > Viresh, what's your view on this? > > > + /* Set OPP table conf with NOP config_clks */ > > + priv->opp_token = dev_pm_opp_set_config(cpu_dev, &config); > > + if (priv->opp_token < 0) { > > + ret = priv->opp_token; > > + dev_err(dev, "Failed to set OPP config\n"); > > + goto err_set_config; > > + } > > + > > + /* Attach PM for OPP */ > > + ret = dev_pm_domain_attach_list(cpu_dev, &attach_data, > > + &priv->pd_list); > > + if (ret) > > + goto err_attach_pm; > > + > > + cpufreq_dt = platform_device_register_simple("cpufreq-dt", -1, NULL, 0); > > + ret = PTR_ERR_OR_ZERO(cpufreq_dt); > > + if (ret) { > > + dev_err(dev, "failed to create cpufreq-dt device: %d\n", ret); > > + goto err_register_cpufreq; > > + } > > + > > + priv->cpufreq_dt = cpufreq_dt; > > + platform_set_drvdata(pdev, priv); > > + > > + return 0; > > + > > +err_register_cpufreq: > > + dev_pm_domain_detach_list(priv->pd_list); > > +err_attach_pm: > > + dev_pm_opp_clear_config(priv->opp_token); > > +err_set_config: > > + of_genpd_del_provider(dev->of_node); > > +err_add_provider: > > + pm_genpd_remove(pd); > > + > > + return ret; > > +} > > + > > +static void airoha_cpufreq_remove(struct platform_device *pdev) > > +{ > > + struct airoha_cpufreq_priv *priv = platform_get_drvdata(pdev); > > + > > + platform_device_unregister(priv->cpufreq_dt); > > + > > + dev_pm_domain_detach_list(priv->pd_list); > > + > > + dev_pm_opp_clear_config(priv->opp_token); > > + > > + of_genpd_del_provider(pdev->dev.of_node); > > + pm_genpd_remove(&priv->pd); > > +} > > + > > +static const struct of_device_id airoha_cpufreq_of_match[] = { > > + { .compatible = "airoha,en7581-cpufreq" }, > > + { }, > > +}; > > +MODULE_DEVICE_TABLE(of, airoha_cpufreq_of_match); > > + > > +static struct platform_driver airoha_cpufreq_driver = { > > + .probe = airoha_cpufreq_probe, > > + .remove = airoha_cpufreq_remove, > > + .driver = { > > + .name = "airoha-cpufreq", > > + .of_match_table = airoha_cpufreq_of_match, > > + }, > > +}; > > +module_platform_driver(airoha_cpufreq_driver); > > + > > +MODULE_AUTHOR("Christian Marangi <ansuelsmth@gmail.com>"); > > +MODULE_DESCRIPTION("CPUfreq driver for Airoha SoCs"); > > +MODULE_LICENSE("GPL"); > > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c > > index 9c198bd4f7e9..2aa00769cf09 100644 > > --- a/drivers/cpufreq/cpufreq-dt-platdev.c > > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c > > @@ -103,6 +103,8 @@ static const struct of_device_id allowlist[] __initconst = { > > * platforms using "operating-points-v2" property. > > */ > > static const struct of_device_id blocklist[] __initconst = { > > + { .compatible = "airoha,en7581", }, > > + I had a closer look at cpufreq-dt. Not sure if it makes sense, but to me it seems like we should extend it to support attaching cpu-devices to their performance domains (power-domains). In this way, we can avoid adding the airoha compatible above to the blocklist. Christian, do you want to take a stab at this - or just let me know and I can try to draft a patch for cpufreq-dt with this? > > { .compatible = "allwinner,sun50i-a100" }, > > { .compatible = "allwinner,sun50i-h6", }, > > { .compatible = "allwinner,sun50i-h616", }, > > -- > > 2.45.2 > > Kind regards Uffe
On 12-12-24, 13:01, Ulf Hansson wrote: > On Fri, 6 Dec 2024 at 22:16, Christian Marangi <ansuelsmth@gmail.com> wrote: > Hmm, it looks like this needs to be moved and possibly split up. > > The provider part (for the clock and power-domain) belongs in > /drivers/pmdomain/*, along with the other power-domain providers. > > Other than that, I was really expecting the cpufreq-dt to take care of the rest. > > To me, the above code belongs in a power-domain provider driver. While > the below should be taken care of in cpufreq-dt, except for the device > registration of the cpufreq-dt device, I guess. > > Viresh, what's your view on this? Sure, no issues.. These are all cpufreq related, but don't necessarily belong in the cpufreq directory.
On Fri, Dec 13, 2024 at 09:30:01AM +0530, Viresh Kumar wrote: > On 12-12-24, 13:01, Ulf Hansson wrote: > > On Fri, 6 Dec 2024 at 22:16, Christian Marangi <ansuelsmth@gmail.com> wrote: > > Hmm, it looks like this needs to be moved and possibly split up. > > > > The provider part (for the clock and power-domain) belongs in > > /drivers/pmdomain/*, along with the other power-domain providers. > > > > Other than that, I was really expecting the cpufreq-dt to take care of the rest. > > > > To me, the above code belongs in a power-domain provider driver. While > > the below should be taken care of in cpufreq-dt, except for the device > > registration of the cpufreq-dt device, I guess. > > > > Viresh, what's your view on this? > > Sure, no issues.. These are all cpufreq related, but don't necessarily belong in > the cpufreq directory. > Problem is really DT schema... I wonder if it's acceptable to push a name-only driver in pmdomain just do detach from cpufreq. The cpufreq driver would manually probe the pmdomain. Is it acceptable? Or do you have alternative solution for this?
On Fri, Dec 13, 2024 at 11:35:25PM +0100, Christian Marangi wrote: > On Fri, Dec 13, 2024 at 09:30:01AM +0530, Viresh Kumar wrote: > > On 12-12-24, 13:01, Ulf Hansson wrote: > > > On Fri, 6 Dec 2024 at 22:16, Christian Marangi <ansuelsmth@gmail.com> wrote: > > > Hmm, it looks like this needs to be moved and possibly split up. > > > > > > The provider part (for the clock and power-domain) belongs in > > > /drivers/pmdomain/*, along with the other power-domain providers. > > > > > > Other than that, I was really expecting the cpufreq-dt to take care of the rest. > > > > > > To me, the above code belongs in a power-domain provider driver. While > > > the below should be taken care of in cpufreq-dt, except for the device > > > registration of the cpufreq-dt device, I guess. > > > > > > Viresh, what's your view on this? > > > > Sure, no issues.. These are all cpufreq related, but don't necessarily belong in > > the cpufreq directory. > > > > Problem is really DT schema... I wonder if it's acceptable to push a > name-only driver in pmdomain just do detach from cpufreq. The cpufreq > driver would manually probe the pmdomain. Is it acceptable? > > Or do you have alternative solution for this? > Hi Viresk I notice the DT patch has been applied to -next but no cpufreq patch. I'm confused how to further proceed and what changes are needed. Any hint?
On 18-12-24, 08:41, Christian Marangi wrote: > On Fri, Dec 13, 2024 at 11:35:25PM +0100, Christian Marangi wrote: > > On Fri, Dec 13, 2024 at 09:30:01AM +0530, Viresh Kumar wrote: > > > On 12-12-24, 13:01, Ulf Hansson wrote: > > > > On Fri, 6 Dec 2024 at 22:16, Christian Marangi <ansuelsmth@gmail.com> wrote: > > > > Hmm, it looks like this needs to be moved and possibly split up. > > > > > > > > The provider part (for the clock and power-domain) belongs in > > > > /drivers/pmdomain/*, along with the other power-domain providers. > > > > > > > > Other than that, I was really expecting the cpufreq-dt to take care of the rest. > > > > > > > > To me, the above code belongs in a power-domain provider driver. While > > > > the below should be taken care of in cpufreq-dt, except for the device > > > > registration of the cpufreq-dt device, I guess. > > > > > > > > Viresh, what's your view on this? > > > > > > Sure, no issues.. These are all cpufreq related, but don't necessarily belong in > > > the cpufreq directory. > > > > > > > Problem is really DT schema... I wonder if it's acceptable to push a > > name-only driver in pmdomain just do detach from cpufreq. The cpufreq > > driver would manually probe the pmdomain. Is it acceptable? > > > > Or do you have alternative solution for this? > > > > Hi Viresk I notice the DT patch has been applied to -next but no > cpufreq patch. I'm confused how to further proceed and what changes are > needed. Any hint? The DT patch was fine and so I applied. I was waiting for Ulf to reply to your above query.
On Fri, 13 Dec 2024 at 23:35, Christian Marangi <ansuelsmth@gmail.com> wrote: > > On Fri, Dec 13, 2024 at 09:30:01AM +0530, Viresh Kumar wrote: > > On 12-12-24, 13:01, Ulf Hansson wrote: > > > On Fri, 6 Dec 2024 at 22:16, Christian Marangi <ansuelsmth@gmail.com> wrote: > > > Hmm, it looks like this needs to be moved and possibly split up. > > > > > > The provider part (for the clock and power-domain) belongs in > > > /drivers/pmdomain/*, along with the other power-domain providers. > > > > > > Other than that, I was really expecting the cpufreq-dt to take care of the rest. > > > > > > To me, the above code belongs in a power-domain provider driver. While > > > the below should be taken care of in cpufreq-dt, except for the device > > > registration of the cpufreq-dt device, I guess. > > > > > > Viresh, what's your view on this? > > > > Sure, no issues.. These are all cpufreq related, but don't necessarily belong in > > the cpufreq directory. > > > > Problem is really DT schema... I wonder if it's acceptable to push a > name-only driver in pmdomain just do detach from cpufreq. The cpufreq > driver would manually probe the pmdomain. Is it acceptable? > > Or do you have alternative solution for this? The power-domain provider driver should use the compatible "airoha,en7581-cpufreq". This driver should be responsible for registering the genpd and the clock. Potentially, the power-domain provider driver could also register the "cpufreq-dt" platform-device. To make this work, we also need to extend the cpufreq-dt driver (maybe extend its platform-data too?) to be capable of attaching the corresponding cpu-devices to their power(perf)-domains. For the moment, this isn't supported, but I think it would be nice if it could. Another option, would be to use an additional separate name-based cpufreq-driver, as in the qcom-cpufreq-nvmem.c, that then becomes responsible for registering the cpufreq-dt device. Viresh, do you have a better approach in mind? Kind regards Uffe
On 19-12-24, 16:23, Ulf Hansson wrote: > The power-domain provider driver should use the compatible > "airoha,en7581-cpufreq". This driver should be responsible for > registering the genpd and the clock. > > Potentially, the power-domain provider driver could also register the > "cpufreq-dt" platform-device. To make this work, we also need to > extend the cpufreq-dt driver (maybe extend its platform-data too?) to > be capable of attaching the corresponding cpu-devices to their > power(perf)-domains. For the moment, this isn't supported, but I think > it would be nice if it could. Another option, would be to use an > additional separate name-based cpufreq-driver, as in the > qcom-cpufreq-nvmem.c, that then becomes responsible for registering > the cpufreq-dt device. > > Viresh, do you have a better approach in mind? I am fine with any part of the kernel creating the cpufreq-dt device.. That doesn't need to be in the cpufreq directory.
On Thu, Dec 19, 2024 at 04:23:52PM +0100, Ulf Hansson wrote: > On Fri, 13 Dec 2024 at 23:35, Christian Marangi <ansuelsmth@gmail.com> wrote: > > > > On Fri, Dec 13, 2024 at 09:30:01AM +0530, Viresh Kumar wrote: > > > On 12-12-24, 13:01, Ulf Hansson wrote: > > > > On Fri, 6 Dec 2024 at 22:16, Christian Marangi <ansuelsmth@gmail.com> wrote: > > > > Hmm, it looks like this needs to be moved and possibly split up. > > > > > > > > The provider part (for the clock and power-domain) belongs in > > > > /drivers/pmdomain/*, along with the other power-domain providers. > > > > > > > > Other than that, I was really expecting the cpufreq-dt to take care of the rest. > > > > > > > > To me, the above code belongs in a power-domain provider driver. While > > > > the below should be taken care of in cpufreq-dt, except for the device > > > > registration of the cpufreq-dt device, I guess. > > > > > > > > Viresh, what's your view on this? > > > > > > Sure, no issues.. These are all cpufreq related, but don't necessarily belong in > > > the cpufreq directory. > > > > > > > Problem is really DT schema... I wonder if it's acceptable to push a > > name-only driver in pmdomain just do detach from cpufreq. The cpufreq > > driver would manually probe the pmdomain. Is it acceptable? > > > > Or do you have alternative solution for this? > > The power-domain provider driver should use the compatible > "airoha,en7581-cpufreq". This driver should be responsible for > registering the genpd and the clock. Is it ok to have clk provider in power-domain driver? > > Potentially, the power-domain provider driver could also register the > "cpufreq-dt" platform-device. To make this work, we also need to > extend the cpufreq-dt driver (maybe extend its platform-data too?) to > be capable of attaching the corresponding cpu-devices to their > power(perf)-domains. For the moment, this isn't supported, but I think > it would be nice if it could. Another option, would be to use an > additional separate name-based cpufreq-driver, as in the > qcom-cpufreq-nvmem.c, that then becomes responsible for registering > the cpufreq-dt device. Well a simple init/exit driver should be ok, we still need to have the custom function for opp so a specific driver in cpufreq is needed anyway. > > Viresh, do you have a better approach in mind? > If both are ok with this approach I will: - move pm domain and clock to pmdomain driver directory - rework the cpufreq driver to an init/exit implementation (no compatible) and just register cpufreq-dt with the custom opp OPs. This should work and make everything well organized.
On Fri, Dec 06, 2024 at 10:11:25PM +0100, Christian Marangi wrote: > Add simple CPU Freq driver for Airoha EN7581 SoC that control CPU > frequency scaling with SMC APIs and register a generic "cpufreq-dt" > device. > > CPUFreq driver registers a get-only clock to get the current global CPU > frequency from SMC and a Power Domain to configure the performance state > for each OPP to apply the requested frequency from cpufreq-dt. This is > needed as SMC use index instead of raw frequency. > > All CPU share the same frequency and can't be controlled independently. > Current shared CPU frequency is returned by the related SMC command. > > Add SoC compatible to cpufreq-dt-plat block list as a dedicated cpufreq > driver is needed with OPP v2 nodes declared in DTS. > > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> [...] > diff --git a/drivers/cpufreq/airoha-cpufreq.c b/drivers/cpufreq/airoha-cpufreq.c > new file mode 100644 > index 000000000000..29738f61f401 > --- /dev/null > +++ b/drivers/cpufreq/airoha-cpufreq.c > @@ -0,0 +1,222 @@ > +// SPDX-License-Identifier: GPL-2.0 > + > +#include <linux/arm-smccc.h> > +#include <linux/bitfield.h> > +#include <linux/cpufreq.h> > +#include <linux/clk-provider.h> > +#include <linux/module.h> > +#include <linux/platform_device.h> > +#include <linux/pm_domain.h> > +#include <linux/pm_runtime.h> > +#include <linux/slab.h> > + > +#include "cpufreq-dt.h" > + [...] > + > +static unsigned long airoha_cpufreq_clk_get(struct clk_hw *hw, > + unsigned long parent_rate) > +{ > + const struct arm_smccc_1_2_regs args = { > + .a0 = AIROHA_SIP_AVS_HANDLE, > + .a1 = AIROHA_AVS_OP_GET_FREQ, > + }; > + struct arm_smccc_1_2_regs res; > + > + arm_smccc_1_2_smc(&args, &res); See below comment. Same applies here. > + > + /* SMCCC returns freq in MHz */ > + return res.a0 * 1000 * 1000; > +} > + > +/* Airoha CPU clk SMCC is always enabled */ > +static int airoha_cpufreq_clk_is_enabled(struct clk_hw *hw) > +{ > + return true; > +} > + > +static const struct clk_ops airoha_cpufreq_clk_ops = { > + .recalc_rate = airoha_cpufreq_clk_get, > + .is_enabled = airoha_cpufreq_clk_is_enabled, > + .round_rate = airoha_cpufreq_clk_round, > +}; > + > +static const char * const airoha_cpufreq_clk_names[] = { "cpu", NULL }; > + > +/* NOP function to disable OPP from setting clock */ > +static int airoha_cpufreq_config_clks_nop(struct device *dev, > + struct opp_table *opp_table, > + struct dev_pm_opp *opp, > + void *data, bool scaling_down) > +{ > + return 0; > +} > + > +static const char * const airoha_cpufreq_pd_names[] = { "perf" }; > + > +static int airoha_cpufreq_set_performance_state(struct generic_pm_domain *domain, > + unsigned int state) > +{ > + const struct arm_smccc_1_2_regs args = { > + .a0 = AIROHA_SIP_AVS_HANDLE, > + .a1 = AIROHA_AVS_OP_FREQ_DYN_ADJ, > + .a3 = state, > + }; > + struct arm_smccc_1_2_regs res; > + > + arm_smccc_1_2_smc(&args, &res); > + I assume the compatible suggests SMCCCv1.2+ is implemented, but it is good to check arm_smccc_get_version() and add build config dependency on HAVE_ARM_SMCCC_DISCOVERY. Also use the SMCCC conduit and don't assume SMC.
diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm index 5f7e13e60c80..8494faac58ae 100644 --- a/drivers/cpufreq/Kconfig.arm +++ b/drivers/cpufreq/Kconfig.arm @@ -15,6 +15,16 @@ config ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM To compile this driver as a module, choose M here: the module will be called sun50i-cpufreq-nvmem. +config ARM_AIROHA_SOC_CPUFREQ + tristate "Airoha EN7581 SoC CPUFreq support" + depends on ARM64 && (ARCH_AIROHA || COMPILE_TEST) + select PM + select PM_OPP + select PM_GENERIC_DOMAINS + default ARCH_AIROHA + help + This adds the CPUFreq driver for Airoha EN7581 SoCs. + config ARM_APPLE_SOC_CPUFREQ tristate "Apple Silicon SoC CPUFreq support" depends on ARCH_APPLE || (COMPILE_TEST && 64BIT) diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile index d35a28dd9463..890fff99f37d 100644 --- a/drivers/cpufreq/Makefile +++ b/drivers/cpufreq/Makefile @@ -53,6 +53,7 @@ obj-$(CONFIG_X86_AMD_FREQ_SENSITIVITY) += amd_freq_sensitivity.o ################################################################################## # ARM SoC drivers +obj-$(CONFIG_ARM_AIROHA_SOC_CPUFREQ) += airoha-cpufreq.o obj-$(CONFIG_ARM_APPLE_SOC_CPUFREQ) += apple-soc-cpufreq.o obj-$(CONFIG_ARM_ARMADA_37XX_CPUFREQ) += armada-37xx-cpufreq.o obj-$(CONFIG_ARM_ARMADA_8K_CPUFREQ) += armada-8k-cpufreq.o diff --git a/drivers/cpufreq/airoha-cpufreq.c b/drivers/cpufreq/airoha-cpufreq.c new file mode 100644 index 000000000000..29738f61f401 --- /dev/null +++ b/drivers/cpufreq/airoha-cpufreq.c @@ -0,0 +1,222 @@ +// SPDX-License-Identifier: GPL-2.0 + +#include <linux/arm-smccc.h> +#include <linux/bitfield.h> +#include <linux/cpufreq.h> +#include <linux/clk-provider.h> +#include <linux/module.h> +#include <linux/platform_device.h> +#include <linux/pm_domain.h> +#include <linux/pm_runtime.h> +#include <linux/slab.h> + +#include "cpufreq-dt.h" + +#define AIROHA_SIP_AVS_HANDLE 0x82000301 +#define AIROHA_AVS_OP_BASE 0xddddddd0 +#define AIROHA_AVS_OP_MASK GENMASK(1, 0) +#define AIROHA_AVS_OP_FREQ_DYN_ADJ (AIROHA_AVS_OP_BASE | \ + FIELD_PREP(AIROHA_AVS_OP_MASK, 0x1)) +#define AIROHA_AVS_OP_GET_FREQ (AIROHA_AVS_OP_BASE | \ + FIELD_PREP(AIROHA_AVS_OP_MASK, 0x2)) + +struct airoha_cpufreq_priv { + struct clk_hw hw; + struct generic_pm_domain pd; + + int opp_token; + struct dev_pm_domain_list *pd_list; + struct platform_device *cpufreq_dt; +}; + +static long airoha_cpufreq_clk_round(struct clk_hw *hw, unsigned long rate, + unsigned long *parent_rate) +{ + return rate; +} + +static unsigned long airoha_cpufreq_clk_get(struct clk_hw *hw, + unsigned long parent_rate) +{ + const struct arm_smccc_1_2_regs args = { + .a0 = AIROHA_SIP_AVS_HANDLE, + .a1 = AIROHA_AVS_OP_GET_FREQ, + }; + struct arm_smccc_1_2_regs res; + + arm_smccc_1_2_smc(&args, &res); + + /* SMCCC returns freq in MHz */ + return res.a0 * 1000 * 1000; +} + +/* Airoha CPU clk SMCC is always enabled */ +static int airoha_cpufreq_clk_is_enabled(struct clk_hw *hw) +{ + return true; +} + +static const struct clk_ops airoha_cpufreq_clk_ops = { + .recalc_rate = airoha_cpufreq_clk_get, + .is_enabled = airoha_cpufreq_clk_is_enabled, + .round_rate = airoha_cpufreq_clk_round, +}; + +static const char * const airoha_cpufreq_clk_names[] = { "cpu", NULL }; + +/* NOP function to disable OPP from setting clock */ +static int airoha_cpufreq_config_clks_nop(struct device *dev, + struct opp_table *opp_table, + struct dev_pm_opp *opp, + void *data, bool scaling_down) +{ + return 0; +} + +static const char * const airoha_cpufreq_pd_names[] = { "perf" }; + +static int airoha_cpufreq_set_performance_state(struct generic_pm_domain *domain, + unsigned int state) +{ + const struct arm_smccc_1_2_regs args = { + .a0 = AIROHA_SIP_AVS_HANDLE, + .a1 = AIROHA_AVS_OP_FREQ_DYN_ADJ, + .a3 = state, + }; + struct arm_smccc_1_2_regs res; + + arm_smccc_1_2_smc(&args, &res); + + /* SMC signal correct apply by unsetting BIT 0 */ + return res.a0 & BIT(0) ? -EINVAL : 0; +} + +static int airoha_cpufreq_probe(struct platform_device *pdev) +{ + const struct dev_pm_domain_attach_data attach_data = { + .pd_names = airoha_cpufreq_pd_names, + .num_pd_names = ARRAY_SIZE(airoha_cpufreq_pd_names), + .pd_flags = PD_FLAG_DEV_LINK_ON | PD_FLAG_REQUIRED_OPP, + }; + struct dev_pm_opp_config config = { + .clk_names = airoha_cpufreq_clk_names, + .config_clks = airoha_cpufreq_config_clks_nop, + }; + struct platform_device *cpufreq_dt; + struct airoha_cpufreq_priv *priv; + struct device *dev = &pdev->dev; + const struct clk_init_data init = { + .name = "cpu", + .ops = &airoha_cpufreq_clk_ops, + /* Clock with no set_rate, can't cache */ + .flags = CLK_GET_RATE_NOCACHE, + }; + struct generic_pm_domain *pd; + struct device *cpu_dev; + int ret; + + /* CPUs refer to the same OPP table */ + cpu_dev = get_cpu_device(0); + if (!cpu_dev) + return -ENODEV; + + priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL); + if (!priv) + return -ENOMEM; + + /* Init and register a get-only clk for Cpufreq */ + priv->hw.init = &init; + ret = devm_clk_hw_register(dev, &priv->hw); + if (ret) + return ret; + + ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_simple_get, + &priv->hw); + if (ret) + return ret; + + /* Init and register a PD for Cpufreq */ + pd = &priv->pd; + pd->name = "cpu_pd"; + pd->flags = GENPD_FLAG_ALWAYS_ON; + pd->set_performance_state = airoha_cpufreq_set_performance_state; + + ret = pm_genpd_init(pd, NULL, false); + if (ret) + return ret; + + ret = of_genpd_add_provider_simple(dev->of_node, pd); + if (ret) + goto err_add_provider; + + /* Set OPP table conf with NOP config_clks */ + priv->opp_token = dev_pm_opp_set_config(cpu_dev, &config); + if (priv->opp_token < 0) { + ret = priv->opp_token; + dev_err(dev, "Failed to set OPP config\n"); + goto err_set_config; + } + + /* Attach PM for OPP */ + ret = dev_pm_domain_attach_list(cpu_dev, &attach_data, + &priv->pd_list); + if (ret) + goto err_attach_pm; + + cpufreq_dt = platform_device_register_simple("cpufreq-dt", -1, NULL, 0); + ret = PTR_ERR_OR_ZERO(cpufreq_dt); + if (ret) { + dev_err(dev, "failed to create cpufreq-dt device: %d\n", ret); + goto err_register_cpufreq; + } + + priv->cpufreq_dt = cpufreq_dt; + platform_set_drvdata(pdev, priv); + + return 0; + +err_register_cpufreq: + dev_pm_domain_detach_list(priv->pd_list); +err_attach_pm: + dev_pm_opp_clear_config(priv->opp_token); +err_set_config: + of_genpd_del_provider(dev->of_node); +err_add_provider: + pm_genpd_remove(pd); + + return ret; +} + +static void airoha_cpufreq_remove(struct platform_device *pdev) +{ + struct airoha_cpufreq_priv *priv = platform_get_drvdata(pdev); + + platform_device_unregister(priv->cpufreq_dt); + + dev_pm_domain_detach_list(priv->pd_list); + + dev_pm_opp_clear_config(priv->opp_token); + + of_genpd_del_provider(pdev->dev.of_node); + pm_genpd_remove(&priv->pd); +} + +static const struct of_device_id airoha_cpufreq_of_match[] = { + { .compatible = "airoha,en7581-cpufreq" }, + { }, +}; +MODULE_DEVICE_TABLE(of, airoha_cpufreq_of_match); + +static struct platform_driver airoha_cpufreq_driver = { + .probe = airoha_cpufreq_probe, + .remove = airoha_cpufreq_remove, + .driver = { + .name = "airoha-cpufreq", + .of_match_table = airoha_cpufreq_of_match, + }, +}; +module_platform_driver(airoha_cpufreq_driver); + +MODULE_AUTHOR("Christian Marangi <ansuelsmth@gmail.com>"); +MODULE_DESCRIPTION("CPUfreq driver for Airoha SoCs"); +MODULE_LICENSE("GPL"); diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c index 9c198bd4f7e9..2aa00769cf09 100644 --- a/drivers/cpufreq/cpufreq-dt-platdev.c +++ b/drivers/cpufreq/cpufreq-dt-platdev.c @@ -103,6 +103,8 @@ static const struct of_device_id allowlist[] __initconst = { * platforms using "operating-points-v2" property. */ static const struct of_device_id blocklist[] __initconst = { + { .compatible = "airoha,en7581", }, + { .compatible = "allwinner,sun50i-a100" }, { .compatible = "allwinner,sun50i-h6", }, { .compatible = "allwinner,sun50i-h616", },
Add simple CPU Freq driver for Airoha EN7581 SoC that control CPU frequency scaling with SMC APIs and register a generic "cpufreq-dt" device. CPUFreq driver registers a get-only clock to get the current global CPU frequency from SMC and a Power Domain to configure the performance state for each OPP to apply the requested frequency from cpufreq-dt. This is needed as SMC use index instead of raw frequency. All CPU share the same frequency and can't be controlled independently. Current shared CPU frequency is returned by the related SMC command. Add SoC compatible to cpufreq-dt-plat block list as a dedicated cpufreq driver is needed with OPP v2 nodes declared in DTS. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> --- Changes v7: - No changes Changes v6: - Improve Kconfig depends logic - Select PM (PM_GENERIC_DOMAINS depends on it) - Drop (int) cast for Changes v5: - Rename cpu_pd to perf for power domain name - Use remove instead of remove_new Changes v4: - Rework to clk-only + PM set_performance_state implementation Changes v3: - Adapt to new cpufreq-dt APIs - Register cpufreq-dt instead of custom freq driver Changes v2: - Fix kernel bot error with missing slab.h and bitfield.h header - Limit COMPILE_TEST to ARM64 due to smcc 1.2 drivers/cpufreq/Kconfig.arm | 10 ++ drivers/cpufreq/Makefile | 1 + drivers/cpufreq/airoha-cpufreq.c | 222 +++++++++++++++++++++++++++ drivers/cpufreq/cpufreq-dt-platdev.c | 2 + 4 files changed, 235 insertions(+) create mode 100644 drivers/cpufreq/airoha-cpufreq.c