[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220322055012.oewlqykxb4dlkhbr@vireshk-i7>
Date: Tue, 22 Mar 2022 11:20:12 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Sumit Gupta <sumitg@...dia.com>
Cc: rafael@...nel.org, robh+dt@...nel.org, krzk+dt@...nel.org,
treding@...dia.com, jonathanh@...dia.com, linux-pm@...r.kernel.org,
linux-tegra@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, ksitaraman@...dia.com,
sanjayc@...dia.com, bbasu@...dia.com
Subject: Re: [Patch v1 3/3] cpufreq: tegra194: Add support for Tegra234
On 16-03-22, 19:28, Sumit Gupta wrote:
> @@ -442,6 +538,13 @@ static int tegra194_cpufreq_probe(struct platform_device *pdev)
> if (!data->tables)
> return -ENOMEM;
>
> + if (of_device_is_compatible(pdev->dev.of_node, "nvidia,tegra234-ccplex-cluster")) {
Since you have soc specific data, that should be used here to know if you need
to map registers or not. You shouldn't use device-compatible here again.
> + /* mmio registers are used for frequency request and re-construction */
> + data->regs = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(data->regs))
> + return PTR_ERR(data->regs);
> + }
> +
> platform_set_drvdata(pdev, data);
>
> bpmp = tegra_bpmp_get(&pdev->dev);
> @@ -486,6 +589,7 @@ static int tegra194_cpufreq_remove(struct platform_device *pdev)
>
> static const struct of_device_id tegra194_cpufreq_of_match[] = {
> { .compatible = "nvidia,tegra194-ccplex", .data = &tegra194_cpufreq_soc },
> + { .compatible = "nvidia,tegra234-ccplex-cluster", .data = &tegra234_cpufreq_soc },
> { /* sentinel */ }
> };
>
> --
> 2.17.1
--
viresh
Powered by blists - more mailing lists