This function is only called once at boot by device_initcall(), so mark
it as __init.
Signed-off-by: Daniel Kurtz <[email protected]>
---
drivers/cpufreq/mt8173-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/mt8173-cpufreq.c b/drivers/cpufreq/mt8173-cpufreq.c
index ab25b1235a5e..72bc1192bd30 100644
--- a/drivers/cpufreq/mt8173-cpufreq.c
+++ b/drivers/cpufreq/mt8173-cpufreq.c
@@ -573,7 +573,7 @@ static struct platform_driver mt8173_cpufreq_platdrv = {
.probe = mt8173_cpufreq_probe,
};
-static int mt8173_cpufreq_driver_init(void)
+static int __init mt8173_cpufreq_driver_init(void)
{
struct platform_device *pdev;
int err;
--
2.12.0.rc1.440.g5b76565f74-goog
On 02-03-17, 19:03, Daniel Kurtz wrote:
> The Mediatek MT8173 is just one of several SOCs from the same MT817x family,
> including the 6-core (4-little/2-big) MT8176.
>
> The mt8173-cpufreq driver supports all of these SOCs, however, machines
> using them may use a different machine compatible.
>
> Since this driver checks explicitly for the machine compatible string, add
> support for the whole family.
>
> Signed-off-by: Daniel Kurtz <[email protected]>
> ---
> This patch is based on the compatibles added by the MT8176 series:
>
> https://patchwork.kernel.org/patch/9573209/
> https://patchwork.kernel.org/patch/9573213/
>
> v2:
> - use of_match_node (Thanks, Viresh!)
>
> drivers/cpufreq/mt8173-cpufreq.c | 21 ++++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
Acked-by: Viresh Kumar <[email protected]>
--
viresh
On 02-03-17, 19:03, Daniel Kurtz wrote:
> This function is only called once at boot by device_initcall(), so mark
> it as __init.
>
> Signed-off-by: Daniel Kurtz <[email protected]>
> ---
> drivers/cpufreq/mt8173-cpufreq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Viresh Kumar <[email protected]>
--
viresh
The Mediatek MT8173 is just one of several SOCs from the same MT817x family,
including the 6-core (4-little/2-big) MT8176.
The mt8173-cpufreq driver supports all of these SOCs, however, machines
using them may use a different machine compatible.
Since this driver checks explicitly for the machine compatible string, add
support for the whole family.
Signed-off-by: Daniel Kurtz <[email protected]>
---
This patch is based on the compatibles added by the MT8176 series:
https://patchwork.kernel.org/patch/9573209/
https://patchwork.kernel.org/patch/9573213/
v2:
- use of_match_node (Thanks, Viresh!)
drivers/cpufreq/mt8173-cpufreq.c | 21 ++++++++++++++++++++-
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq/mt8173-cpufreq.c b/drivers/cpufreq/mt8173-cpufreq.c
index 72bc1192bd30..fd1886faf33a 100644
--- a/drivers/cpufreq/mt8173-cpufreq.c
+++ b/drivers/cpufreq/mt8173-cpufreq.c
@@ -573,14 +573,33 @@ static struct platform_driver mt8173_cpufreq_platdrv = {
.probe = mt8173_cpufreq_probe,
};
+/* List of machines supported by this driver */
+static const struct of_device_id mt8173_cpufreq_machines[] __initconst = {
+ { .compatible = "mediatek,mt817x", },
+ { .compatible = "mediatek,mt8173", },
+ { .compatible = "mediatek,mt8176", },
+
+ { }
+};
+
static int __init mt8173_cpufreq_driver_init(void)
{
+ struct device_node *np;
+ const struct of_device_id *match;
struct platform_device *pdev;
int err;
- if (!of_machine_is_compatible("mediatek,mt8173"))
+ np = of_find_node_by_path("/");
+ if (!np)
return -ENODEV;
+ match = of_match_node(mt8173_cpufreq_machines, np);
+ of_node_put(np);
+ if (!match) {
+ pr_warn("Machine is not compatible with mt8173-cpufreq\n");
+ return -ENODEV;
+ }
+
err = platform_driver_register(&mt8173_cpufreq_platdrv);
if (err)
return err;
--
2.12.0.rc1.440.g5b76565f74-goog
On Thu, Mar 2, 2017 at 7:06 PM, Viresh Kumar <[email protected]> wrote:
>
> On 02-03-17, 19:03, Daniel Kurtz wrote:
> > This function is only called once at boot by device_initcall(), so mark
> > it as __init.
> >
> > Signed-off-by: Daniel Kurtz <[email protected]>
> > ---
> > drivers/cpufreq/mt8173-cpufreq.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Acked-by: Viresh Kumar <[email protected]>
Its very strange. The patch itself does not appear to have made it to the list.
But, I do see your Ack:
https://www.spinics.net/lists/kernel/msg2455271.html
>
> --
> viresh