From: "Clément Péron" <peron.clem@gmail.com>
To: Shuosheng Huang <huangshuosheng@allwinnertech.com>,
Rob Herring <robh+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Yangtao Li <tiny.windzz@gmail.com>
Cc: devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"open list:ALLWINNER CPUFREQ DRIVER" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 1/2] cpufreq: sun50i: add a100 cpufreq support
Date: Sun, 6 Dec 2020 21:59:01 +0100 [thread overview]
Message-ID: <CAJiuCcf3r_ThavkXtHaRujZOthvRK2_+Esa_5BG-fk5xBN6fxQ@mail.gmail.com> (raw)
In-Reply-To: <388512ba-9e2b-acad-8487-5c26a6eb101b@gmail.com>
Hi Shuosheng,
On Sun, 6 Dec 2020 at 21:49, Clément Péron <peron.clem@gmail.com> wrote:
>
> Hi Shuosheng,
>
> On 04/12/2020 08:09, Shuosheng Huang wrote:
> > Let's add cpufreq nvmem based for allwinner a100 soc. It's similar to h6,
> > let us use efuse_xlate to extract the differentiated part.
>
> So you introduce 2 modifications here.
> In this case it's better to have 2 patches.
> One to introduce the efuse_xlate
> And one to introduce the A100 support.
>
> Regards,
> Clement
>
> >
> > Signed-off-by: Shuosheng Huang <huangshuosheng@allwinnertech.com>
> > ---
> > drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> > drivers/cpufreq/sun50i-cpufreq-nvmem.c | 81 ++++++++++++++++++++------
> > 2 files changed, 64 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> > index 3776d960f405..2ebf5d9cb616 100644
> > --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> > @@ -102,6 +102,7 @@ static const struct of_device_id whitelist[] __initconst = {
> > */
> > static const struct of_device_id blacklist[] __initconst = {
> > { .compatible = "allwinner,sun50i-h6", },
> > + { .compatible = "allwinner,sun50i-a100", },
> >
> > { .compatible = "calxeda,highbank", },
> > { .compatible = "calxeda,ecx-2000", },
> > diff --git a/drivers/cpufreq/sun50i-cpufreq-nvmem.c b/drivers/cpufreq/sun50i-cpufreq-nvmem.c
> > index 9907a165135b..044e44a763f5 100644
> > --- a/drivers/cpufreq/sun50i-cpufreq-nvmem.c
> > +++ b/drivers/cpufreq/sun50i-cpufreq-nvmem.c
> > @@ -21,21 +21,63 @@
> >
> > #define NVMEM_MASK 0x7
> > #define NVMEM_SHIFT 5
> > +#define SUN50I_A100_NVMEM_MASK 0xf
> > +#define SUN50I_A100_NVMEM_SHIFT 12
> > +
> > +#define SUN50I_H6_NVMEM_MASK 0x7
> > +#define SUN50I_H6_NVMEM_SHIFT 5
> > +
> > +struct sunxi_cpufreq_soc_data {
> > + u32 (*efuse_xlate)(void *efuse);
Maybe it's better to pass the speedbin_nvmem.
And call nvmem_cell_read_u16 or nvmem_cell_read_u32 regarding the SoC.
But I'm not a Maintainer.
Clement
> > +};
> >
> > static struct platform_device *cpufreq_dt_pdev, *sun50i_cpufreq_pdev;
> >
> > +static u32 sun50i_a100_efuse_xlate(void *efuse)
> > +{
> > + u32 efuse_value = (*(u16 *)efuse >> SUN50I_A100_NVMEM_SHIFT) &
> > + SUN50I_A100_NVMEM_MASK;
> > +
> > + switch (efuse_value) {
> > + case 0b100:
> > + return 2;
> > + case 0b010:
> > + return 1;
> > + default:
> > + return 0;
> > + }
> > +}
> > +
> > +static u32 sun50i_h6_efuse_xlate(void *efuse)
> > +{
> > + u32 efuse_value = (*(u32 *)efuse >> SUN50I_H6_NVMEM_SHIFT) &
> > + SUN50I_H6_NVMEM_MASK;
> > +
> > + /*
> > + * We treat unexpected efuse values as if the SoC was from
> > + * the slowest bin. Expected efuse values are 1-3, slowest
> > + * to fastest.
> > + */
> > + if (efuse_value >= 1 && efuse_value <= 3)
> > + return efuse_value - 1;
> > + else
> > + return 0;
> > +}
> > +
> > /**
> > * sun50i_cpufreq_get_efuse() - Determine speed grade from efuse value
> > + * @soc_data: pointer to sunxi_cpufreq_soc_data context
> > * @versions: Set to the value parsed from efuse
> > *
> > * Returns 0 if success.
> > */
> > -static int sun50i_cpufreq_get_efuse(u32 *versions)
> > +static int sun50i_cpufreq_get_efuse(const struct sunxi_cpufreq_soc_data *soc_data,
> > + u32 *versions)
> > {
> > struct nvmem_cell *speedbin_nvmem;
> > struct device_node *np;
> > struct device *cpu_dev;
> > - u32 *speedbin, efuse_value;
> > + u32 *speedbin;
> > size_t len;
> > int ret;
> >
> > @@ -68,17 +110,7 @@ static int sun50i_cpufreq_get_efuse(u32 *versions)
> > if (IS_ERR(speedbin))
> > return PTR_ERR(speedbin);
> >
> > - efuse_value = (*speedbin >> NVMEM_SHIFT) & NVMEM_MASK;
> > -
> > - /*
> > - * We treat unexpected efuse values as if the SoC was from
> > - * the slowest bin. Expected efuse values are 1-3, slowest
> > - * to fastest.
> > - */
> > - if (efuse_value >= 1 && efuse_value <= 3)
> > - *versions = efuse_value - 1;
> > - else
> > - *versions = 0;
> > + *versions = soc_data->efuse_xlate(speedbin);
> >
> > kfree(speedbin);
> > return 0;
> > @@ -86,18 +118,23 @@ static int sun50i_cpufreq_get_efuse(u32 *versions)
> >
> > static int sun50i_cpufreq_nvmem_probe(struct platform_device *pdev)
> > {
> > + const struct of_device_id *match;
> > struct opp_table **opp_tables;
> > char name[MAX_NAME_LEN];
> > unsigned int cpu;
> > u32 speed = 0;
> > int ret;
> >
> > + match = dev_get_platdata(&pdev->dev);
> > + if (!match)
> > + return -EINVAL;
> > +
> > opp_tables = kcalloc(num_possible_cpus(), sizeof(*opp_tables),
> > GFP_KERNEL);
> > if (!opp_tables)
> > return -ENOMEM;
> >
> > - ret = sun50i_cpufreq_get_efuse(&speed);
> > + ret = sun50i_cpufreq_get_efuse(match->data, &speed);
> > if (ret)
> > return ret;
> >
> > @@ -163,8 +200,17 @@ static struct platform_driver sun50i_cpufreq_driver = {
> > },
> > };
> >
> > +static const struct sunxi_cpufreq_soc_data sun50i_a100_data = {
> > + .efuse_xlate = sun50i_a100_efuse_xlate,
> > +};
> > +
> > +static const struct sunxi_cpufreq_soc_data sun50i_h6_data = {
> > + .efuse_xlate = sun50i_h6_efuse_xlate,
> > +};
> > +
> > static const struct of_device_id sun50i_cpufreq_match_list[] = {
> > - { .compatible = "allwinner,sun50i-h6" },
> > + { .compatible = "allwinner,sun50i-h6", .data = &sun50i_h6_data },
> > + { .compatible = "allwinner,sun50i-a100", .data = &sun50i_a100_data > {}
> > };
> >
> > @@ -198,9 +244,8 @@ static int __init sun50i_cpufreq_init(void)
> > if (unlikely(ret < 0))
> > return ret;
> >
> > - sun50i_cpufreq_pdev =
> > - platform_device_register_simple("sun50i-cpufreq-nvmem",
> > - -1, NULL, 0);
> > + sun50i_cpufreq_pdev = platform_device_register_data(NULL,
> > + "sun50i-cpufreq-nvmem", -1, match, sizeof(*match));
> > ret = PTR_ERR_OR_ZERO(sun50i_cpufreq_pdev);
> > if (ret == 0)
> > return 0;
> >
prev parent reply other threads:[~2020-12-06 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 7:09 [PATCH 1/2] cpufreq: sun50i: add a100 cpufreq support Shuosheng Huang
2020-12-05 14:50 ` Frank Lee
2020-12-06 20:49 ` Clément Péron
2020-12-06 20:59 ` Clément Péron [this message]
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=CAJiuCcf3r_ThavkXtHaRujZOthvRK2_+Esa_5BG-fk5xBN6fxQ@mail.gmail.com \
--to=peron.clem@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=huangshuosheng@allwinnertech.com \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=tiny.windzz@gmail.com \
--cc=viresh.kumar@linaro.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).