From: Lucas Stach <l.stach@pengutronix.de>
To: Leonard Crestez <leonard.crestez@nxp.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
Abel Vesa <abel.vesa@nxp.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] cpufreq: Add imx-cpufreq-dt driver
Date: Fri, 26 Apr 2019 11:47:09 +0200 [thread overview]
Message-ID: <1556272029.2584.31.camel@pengutronix.de> (raw)
In-Reply-To: <83a3ade389239bd492ee646aa4868c5e37e65434.1556187603.git.leonard.crestez@nxp.com>
Hi Leonard,
Am Donnerstag, den 25.04.2019, 10:29 +0000 schrieb Leonard Crestez:
> Right now in upstream imx8m cpufreq support just lists a common subset
> of OPPs because the higher ones should only be attempted after checking
> speed grading in fuses.
>
> This is not a reasonable limitation and means we must still carry a
> separate cpufreq driver in NXP tree.
>
> This is a small driver which checks speed grading from nvmem before
> registering cpufreq-dt. Unlike imx6q-cpufreq and various other rejected
> imx7/8 cpufreq drivers it contains no actual frequency switching code,
> just fuse reading through nvmem API.
>
> Code is inspired by similar cpufreq wrappers from a dozen different
> vendors. Currently for imx8mm but same issue applies to imx8mq and
> others.
>
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
>
> ---
> drivers/cpufreq/Kconfig.arm | 5 ++
> drivers/cpufreq/Makefile | 1 +
> drivers/cpufreq/cpufreq-dt-platdev.c | 2 +
> drivers/cpufreq/imx-cpufreq-dt.c | 101 +++++++++++++++++++++++++++
> 4 files changed, 109 insertions(+)
> create mode 100644 drivers/cpufreq/imx-cpufreq-dt.c
>
> Since nvmem is a module this driver also needs to be turned into a
> proper module, right now it will simply fail if nvmem is unavailable at
> init time. Let me know if you agree with this approach before I turn it
> into a module.
>
> In vendor tree this is done in soc driver but many other vendors do it
> in drivers/cpufreq so this is where it belongs.
>
> This is select by default in Kconfig, if anything fails then regular
> cpufreq-dt is not available. This is intentional because higher OPPs are
> potentially unstable.
>
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index 179a1d302f48..4a098a6befb2 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -90,10 +90,15 @@ config ARM_IMX6Q_CPUFREQ
> > help
> > This adds cpufreq driver support for Freescale i.MX6 series SoCs.
>
> > If in doubt, say N.
>
> +config ARM_IMX_CPUFREQ_DT
> > + bool "Freescale i.MX8MM cpufreq support"
> > + depends on CPUFREQ_DT && ARCH_MXC
> > + default y
> +
> config ARM_KIRKWOOD_CPUFREQ
> > def_bool MACH_KIRKWOOD
> > help
> > This adds the CPUFreq driver for Marvell Kirkwood
> > SoCs.
> diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile
> index 689b26c6f949..7bcda2273d0c 100644
> --- a/drivers/cpufreq/Makefile
> +++ b/drivers/cpufreq/Makefile
> > @@ -54,10 +54,11 @@ obj-$(CONFIG_ARM_ARMADA_8K_CPUFREQ) += armada-8k-cpufreq.o
> > obj-$(CONFIG_ARM_BRCMSTB_AVS_CPUFREQ) += brcmstb-avs-cpufreq.o
> > obj-$(CONFIG_ACPI_CPPC_CPUFREQ) += cppc_cpufreq.o
> > obj-$(CONFIG_ARCH_DAVINCI) += davinci-cpufreq.o
> > obj-$(CONFIG_ARM_HIGHBANK_CPUFREQ) += highbank-cpufreq.o
> > obj-$(CONFIG_ARM_IMX6Q_CPUFREQ) += imx6q-cpufreq.o
> > +obj-$(CONFIG_ARM_IMX_CPUFREQ_DT) += imx-cpufreq-dt.o
> > obj-$(CONFIG_ARM_KIRKWOOD_CPUFREQ) += kirkwood-cpufreq.o
> > obj-$(CONFIG_ARM_MEDIATEK_CPUFREQ) += mediatek-cpufreq.o
> > obj-$(CONFIG_MACH_MVEBU_V7) += mvebu-cpufreq.o
> > obj-$(CONFIG_ARM_OMAP2PLUS_CPUFREQ) += omap-cpufreq.o
> > obj-$(CONFIG_ARM_PXA2xx_CPUFREQ) += pxa2xx-cpufreq.o
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 47729a22c159..b84baeb1bf1b 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -106,10 +106,12 @@ static const struct of_device_id whitelist[] __initconst = {
> */
> static const struct of_device_id blacklist[] __initconst = {
> > { .compatible = "calxeda,highbank", },
> > { .compatible = "calxeda,ecx-2000", },
>
> > + { .compatible = "fsl,imx8mm", },
> +
> > { .compatible = "marvell,armadaxp", },
>
> > { .compatible = "mediatek,mt2701", },
> > { .compatible = "mediatek,mt2712", },
> > { .compatible = "mediatek,mt7622", },
> diff --git a/drivers/cpufreq/imx-cpufreq-dt.c b/drivers/cpufreq/imx-cpufreq-dt.c
> new file mode 100644
> index 000000000000..c341308a8142
> --- /dev/null
> +++ b/drivers/cpufreq/imx-cpufreq-dt.c
> @@ -0,0 +1,101 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright 2019 NXP
> + */
> +
> +#include <linux/cpu.h>
> +#include <linux/err.h>
> +#include <linux/init.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/nvmem-consumer.h>
> +#include <linux/of.h>
> +#include <linux/platform_device.h>
> +#include <linux/pm_opp.h>
> +#include <linux/slab.h>
> +
> > +#define OCOTP_CFG3_SPEED_GRADE_SHIFT 8
> > +#define OCOTP_CFG3_SPEED_GRADE_MASK (0x3 << 8)
> +
> > +#define OCOTP_CFG3_MKT_SEGMENT_SHIFT 6
> > +#define OCOTP_CFG3_MKT_SEGMENT_MASK (0x3 << 6)
> +
> > +#define OCOTP_CFG3_CONSUMER 0
> > +#define OCOTP_CFG3_EXT_CONSUMER 1
> > +#define OCOTP_CFG3_INDUSTRIAL 2
> > +#define OCOTP_CFG3_AUTO 3
> +
> > +#define OCOTP_CFG3_8MM_SPEED_0P8GHZ 0
> > +#define OCOTP_CFG3_8MM_SPEED_1P2GHZ 1
> > +#define OCOTP_CFG3_8MM_SPEED_1P6GHZ 2
> > +#define OCOTP_CFG3_8MM_SPEED_1P8GHZ 3
> +
> +static int imx8mm_opp_check_speed_grading(struct device *cpu_dev)
> +{
> > + u32 val, speed_grade, mkt_segment;
> > + int ret = 0;
> +
> > + ret = nvmem_cell_read_u32(cpu_dev, "speed_grade", &val);
> > + if (ret)
> > + return ret;
> +
> > + speed_grade = (val & OCOTP_CFG3_SPEED_GRADE_MASK) >> OCOTP_CFG3_SPEED_GRADE_SHIFT;
> > + mkt_segment = (val & OCOTP_CFG3_MKT_SEGMENT_MASK) >> OCOTP_CFG3_MKT_SEGMENT_SHIFT;
> +
> > + dev_info(cpu_dev, "imx8mm cpu speed grade %d segment %d\n",
> > + speed_grade, mkt_segment);
> +
> > + switch (mkt_segment) {
> > + case OCOTP_CFG3_CONSUMER:
> > + if (speed_grade < OCOTP_CFG3_8MM_SPEED_1P8GHZ)
> > + if (dev_pm_opp_disable(cpu_dev, 1800000000))
> > + pr_warn("failed to disable 1.8GHz OPP!\n");
> > + if (speed_grade < OCOTP_CFG3_8MM_SPEED_1P6GHZ)
> > + if (dev_pm_opp_disable(cpu_dev, 1600000000))
> > + pr_warn("failed to disable 1.6GHz OPP!\n");
> > + break;
> > + case OCOTP_CFG3_INDUSTRIAL:
> > + if (dev_pm_opp_disable(cpu_dev, 1800000000))
> > + pr_warn("failed to disable 1.8GHz OPP!\n");
> > + if (val < OCOTP_CFG3_8MM_SPEED_1P6GHZ)
> > + if (dev_pm_opp_disable(cpu_dev, 1600000000))
> > + pr_warn("failed to disable 1.6GHz OPP!\n");
> > + break;
> > + default:
> > + break;
> + }
Do we need to take the market segment classification into account here?
I would have expected that the speed grade would be fused correctly for
all parts, so a industrial part would never get a speed grade of
1.8GHz. Is this assumption wrong?
Also I don't see any code to disable the 1.2GHz OPP for parts with a
speed grade of 0.
Regards,
Lucas
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Lucas Stach <l.stach@pengutronix.de>
To: Leonard Crestez <leonard.crestez@nxp.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Abel Vesa <abel.vesa@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
Aisheng Dong <aisheng.dong@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [RFC] cpufreq: Add imx-cpufreq-dt driver
Date: Fri, 26 Apr 2019 11:47:09 +0200 [thread overview]
Message-ID: <1556272029.2584.31.camel@pengutronix.de> (raw)
Message-ID: <20190426094709.aHhE2uamKD1cLwJZhj4FGSumEolSsD4oNUSIi84LmO8@z> (raw)
In-Reply-To: <83a3ade389239bd492ee646aa4868c5e37e65434.1556187603.git.leonard.crestez@nxp.com>
Hi Leonard,
Am Donnerstag, den 25.04.2019, 10:29 +0000 schrieb Leonard Crestez:
> Right now in upstream imx8m cpufreq support just lists a common subset
> of OPPs because the higher ones should only be attempted after checking
> speed grading in fuses.
>
> This is not a reasonable limitation and means we must still carry a
> separate cpufreq driver in NXP tree.
>
> This is a small driver which checks speed grading from nvmem before
> registering cpufreq-dt. Unlike imx6q-cpufreq and various other rejected
> imx7/8 cpufreq drivers it contains no actual frequency switching code,
> just fuse reading through nvmem API.
>
> Code is inspired by similar cpufreq wrappers from a dozen different
> vendors. Currently for imx8mm but same issue applies to imx8mq and
> others.
>
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
>
> ---
> drivers/cpufreq/Kconfig.arm | 5 ++
> drivers/cpufreq/Makefile | 1 +
> drivers/cpufreq/cpufreq-dt-platdev.c | 2 +
> drivers/cpufreq/imx-cpufreq-dt.c | 101 +++++++++++++++++++++++++++
> 4 files changed, 109 insertions(+)
> create mode 100644 drivers/cpufreq/imx-cpufreq-dt.c
>
> Since nvmem is a module this driver also needs to be turned into a
> proper module, right now it will simply fail if nvmem is unavailable at
> init time. Let me know if you agree with this approach before I turn it
> into a module.
>
> In vendor tree this is done in soc driver but many other vendors do it
> in drivers/cpufreq so this is where it belongs.
>
> This is select by default in Kconfig, if anything fails then regular
> cpufreq-dt is not available. This is intentional because higher OPPs are
> potentially unstable.
>
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index 179a1d302f48..4a098a6befb2 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -90,10 +90,15 @@ config ARM_IMX6Q_CPUFREQ
> > help
> > This adds cpufreq driver support for Freescale i.MX6 series SoCs.
>
> > If in doubt, say N.
>
> +config ARM_IMX_CPUFREQ_DT
> > + bool "Freescale i.MX8MM cpufreq support"
> > + depends on CPUFREQ_DT && ARCH_MXC
> > + default y
> +
> config ARM_KIRKWOOD_CPUFREQ
> > def_bool MACH_KIRKWOOD
> > help
> > This adds the CPUFreq driver for Marvell Kirkwood
> > SoCs.
> diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile
> index 689b26c6f949..7bcda2273d0c 100644
> --- a/drivers/cpufreq/Makefile
> +++ b/drivers/cpufreq/Makefile
> > @@ -54,10 +54,11 @@ obj-$(CONFIG_ARM_ARMADA_8K_CPUFREQ) += armada-8k-cpufreq.o
> > obj-$(CONFIG_ARM_BRCMSTB_AVS_CPUFREQ) += brcmstb-avs-cpufreq.o
> > obj-$(CONFIG_ACPI_CPPC_CPUFREQ) += cppc_cpufreq.o
> > obj-$(CONFIG_ARCH_DAVINCI) += davinci-cpufreq.o
> > obj-$(CONFIG_ARM_HIGHBANK_CPUFREQ) += highbank-cpufreq.o
> > obj-$(CONFIG_ARM_IMX6Q_CPUFREQ) += imx6q-cpufreq.o
> > +obj-$(CONFIG_ARM_IMX_CPUFREQ_DT) += imx-cpufreq-dt.o
> > obj-$(CONFIG_ARM_KIRKWOOD_CPUFREQ) += kirkwood-cpufreq.o
> > obj-$(CONFIG_ARM_MEDIATEK_CPUFREQ) += mediatek-cpufreq.o
> > obj-$(CONFIG_MACH_MVEBU_V7) += mvebu-cpufreq.o
> > obj-$(CONFIG_ARM_OMAP2PLUS_CPUFREQ) += omap-cpufreq.o
> > obj-$(CONFIG_ARM_PXA2xx_CPUFREQ) += pxa2xx-cpufreq.o
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 47729a22c159..b84baeb1bf1b 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -106,10 +106,12 @@ static const struct of_device_id whitelist[] __initconst = {
> */
> static const struct of_device_id blacklist[] __initconst = {
> > { .compatible = "calxeda,highbank", },
> > { .compatible = "calxeda,ecx-2000", },
>
> > + { .compatible = "fsl,imx8mm", },
> +
> > { .compatible = "marvell,armadaxp", },
>
> > { .compatible = "mediatek,mt2701", },
> > { .compatible = "mediatek,mt2712", },
> > { .compatible = "mediatek,mt7622", },
> diff --git a/drivers/cpufreq/imx-cpufreq-dt.c b/drivers/cpufreq/imx-cpufreq-dt.c
> new file mode 100644
> index 000000000000..c341308a8142
> --- /dev/null
> +++ b/drivers/cpufreq/imx-cpufreq-dt.c
> @@ -0,0 +1,101 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright 2019 NXP
> + */
> +
> +#include <linux/cpu.h>
> +#include <linux/err.h>
> +#include <linux/init.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/nvmem-consumer.h>
> +#include <linux/of.h>
> +#include <linux/platform_device.h>
> +#include <linux/pm_opp.h>
> +#include <linux/slab.h>
> +
> > +#define OCOTP_CFG3_SPEED_GRADE_SHIFT 8
> > +#define OCOTP_CFG3_SPEED_GRADE_MASK (0x3 << 8)
> +
> > +#define OCOTP_CFG3_MKT_SEGMENT_SHIFT 6
> > +#define OCOTP_CFG3_MKT_SEGMENT_MASK (0x3 << 6)
> +
> > +#define OCOTP_CFG3_CONSUMER 0
> > +#define OCOTP_CFG3_EXT_CONSUMER 1
> > +#define OCOTP_CFG3_INDUSTRIAL 2
> > +#define OCOTP_CFG3_AUTO 3
> +
> > +#define OCOTP_CFG3_8MM_SPEED_0P8GHZ 0
> > +#define OCOTP_CFG3_8MM_SPEED_1P2GHZ 1
> > +#define OCOTP_CFG3_8MM_SPEED_1P6GHZ 2
> > +#define OCOTP_CFG3_8MM_SPEED_1P8GHZ 3
> +
> +static int imx8mm_opp_check_speed_grading(struct device *cpu_dev)
> +{
> > + u32 val, speed_grade, mkt_segment;
> > + int ret = 0;
> +
> > + ret = nvmem_cell_read_u32(cpu_dev, "speed_grade", &val);
> > + if (ret)
> > + return ret;
> +
> > + speed_grade = (val & OCOTP_CFG3_SPEED_GRADE_MASK) >> OCOTP_CFG3_SPEED_GRADE_SHIFT;
> > + mkt_segment = (val & OCOTP_CFG3_MKT_SEGMENT_MASK) >> OCOTP_CFG3_MKT_SEGMENT_SHIFT;
> +
> > + dev_info(cpu_dev, "imx8mm cpu speed grade %d segment %d\n",
> > + speed_grade, mkt_segment);
> +
> > + switch (mkt_segment) {
> > + case OCOTP_CFG3_CONSUMER:
> > + if (speed_grade < OCOTP_CFG3_8MM_SPEED_1P8GHZ)
> > + if (dev_pm_opp_disable(cpu_dev, 1800000000))
> > + pr_warn("failed to disable 1.8GHz OPP!\n");
> > + if (speed_grade < OCOTP_CFG3_8MM_SPEED_1P6GHZ)
> > + if (dev_pm_opp_disable(cpu_dev, 1600000000))
> > + pr_warn("failed to disable 1.6GHz OPP!\n");
> > + break;
> > + case OCOTP_CFG3_INDUSTRIAL:
> > + if (dev_pm_opp_disable(cpu_dev, 1800000000))
> > + pr_warn("failed to disable 1.8GHz OPP!\n");
> > + if (val < OCOTP_CFG3_8MM_SPEED_1P6GHZ)
> > + if (dev_pm_opp_disable(cpu_dev, 1600000000))
> > + pr_warn("failed to disable 1.6GHz OPP!\n");
> > + break;
> > + default:
> > + break;
> + }
Do we need to take the market segment classification into account here?
I would have expected that the speed grade would be fused correctly for
all parts, so a industrial part would never get a speed grade of
1.8GHz. Is this assumption wrong?
Also I don't see any code to disable the 1.2GHz OPP for parts with a
speed grade of 0.
Regards,
Lucas
next prev parent reply other threads:[~2019-04-26 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 10:29 [RFC] cpufreq: Add imx-cpufreq-dt driver Leonard Crestez
2019-04-25 10:29 ` Leonard Crestez
2019-04-25 10:32 ` Viresh Kumar
2019-04-25 10:32 ` Viresh Kumar
2019-04-25 11:38 ` Daniel Baluta
2019-04-25 11:38 ` Daniel Baluta
2019-04-26 9:47 ` Lucas Stach [this message]
2019-04-26 9:47 ` Lucas Stach
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=1556272029.2584.31.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@linaro.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