lkml.org 
[lkml]   [2019]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/4] cpufreq: ti-cpufreq: add support for omap34xx and omap36xx
* H. Nikolaus Schaller <hns@goldelico.com> [190907 07:38]:
> > Am 07.09.2019 um 08:56 schrieb H. Nikolaus Schaller <hns@goldelico.com>:
> > @@ -190,6 +272,11 @@ static const struct of_device_id ti_cpufreq_of_match[] = {
> > { .compatible = "ti,am33xx", .data = &am3x_soc_data, },
> > { .compatible = "ti,am43", .data = &am4x_soc_data, },
> > { .compatible = "ti,dra7", .data = &dra7_soc_data },
> > + { .compatible = "ti,omap34xx", .data = &omap34xx_soc_data, },
> > + { .compatible = "ti,omap36xx", .data = &omap36xx_soc_data, },
> > + /* legacy */
> > + { .compatible = "ti,omap3430", .data = &omap34xx_soc_data, },
> > + { .compatible = "ti,omap3630", .data = &omap36xx_soc_data, },
>
> Well, I just realized that with the latest DTS changes,
>
> ti,omap34xx and ti,omap36xx are legacy and
> ti,omap3430 and ti,omap3630 are now official.

Heh :) Anyways, with that changed, this looks good to me:

Reviewed-by: Tony Lindgren <tony@atomide.com>

\
 
 \ /
  Last update: 2019-09-07 19:09    [W:0.123 / U:0.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site